NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

ONTAP Discussions

CP type "s" in the 2nd character.

motohisa_nozaki
7,124 Views

Hello,

 

I am not good at English. So, I apologise if you feel difficult to understand  following.

 

I have VMware environment that includes NetApp FAS as NFS datastore.

Sometime this FAS not responding in CP ty #s, and occures APD in ESXi.

 

I read man page and understood that "CP ty s" is "Proccesing Special Files", but I cannot understand what is "Special Files".

 

Please let me know If anyone knows "what is Special Files".

(inode? metafile? or other?) 

 

regards,

1 ACCEPTED SOLUTION

D_BEREZENKO
6,992 Views

Examples of "special files" in ONTAP are:

  • Directories
  • Hard Links
  • LUNs

 

If you have # or : symbols fallowing with B in next CP, it might mean that you have high sequential throughput or high overwrite throughput, both cases indicate to a small number of drives which is not enough to handle the workload.

Also as far as I remember in 8.1.2 there was a bug BURT 393877 (Inefficient pre-fetching of metadata blocks delays WAFL consistency point) which might be indicated by CP ty :s but it should be resolved in 8.1.4P1, so double check on it.

View solution in original post

4 REPLIES 4

D_BEREZENKO
7,071 Views

What ONTAP version & FAS system do you have?

Do you have 7-mode?

What protocol(s) are you using in your environment?

motohisa_nozaki
7,006 Views

Hi, 

 

Thank you for reply.

 

I have FAS2240-2. DOT814P1 7-mode installed.

Protocols are NFS and iSCSI.

D_BEREZENKO
6,993 Views

Examples of "special files" in ONTAP are:

  • Directories
  • Hard Links
  • LUNs

 

If you have # or : symbols fallowing with B in next CP, it might mean that you have high sequential throughput or high overwrite throughput, both cases indicate to a small number of drives which is not enough to handle the workload.

Also as far as I remember in 8.1.2 there was a bug BURT 393877 (Inefficient pre-fetching of metadata blocks delays WAFL consistency point) which might be indicated by CP ty :s but it should be resolved in 8.1.4P1, so double check on it.

motohisa_nozaki
6,950 Views

Hi, D_BEREZENKO

 

Thank you for your assistance.

 

It was not include inode or metadata...

Your answer was very usefull.

 

and I'll check a BURT you suggested.

 

Thank you very much!

 

sincely yours.

Public