Hello mubasicusr,

Which Isilon system do you have and what is your current onefs version?

Hi Sam, thanks for your reply

OneFS Version: 9.1.0.4

We have F600, H500, and A2000 isilon system at environment.

We defined access zone into from host to F600 and H500.

Is it set to local locally or remote? When does it occur? After a reboot or every time a client makes a connection?

Execute ls command by every linux host if it mounted the path.

type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=6,sec=sys,mountaddr=xxxxxxxxx,mountvers=3,mountport=300,mountproto=tcp,local_lock=none,addr=xxxxxxxxxx)

Anytime is occurring, even we reboot the Linux host, we still get this error.

#time ls

ls: cannot access xxxxxxxxxxxxxxxxxxxxxxxxx: No such file or directory

ls: cannot access xxxxxxxxxxxxxxxxxxxxxxxxx: No such file or directory

ls: cannot access xxxxxxxxxxxxxxxxxxxxxxxxx: No such file or directory

real 2m29.831s
user 0m0.047s
sys 0m0.223s

Thanks a lot! 

Hello mubasicusr,

How did you migrate your files from your netapp to your Isilon? Did you use emcopy, robocopy or isi_vol_copy?

Hi Sam,

We are using Linux XCP to execute data copy.

Thanks!

Those 2m30 or 150s look suspicious to me, like a network timeout at the TCP layer.

You can check the network condition using the relevant sections from these troubleshootung guides:

https://dl.dell.com/content/docu80766 

https://dl.dell.com/content/docu60944 

hth

-- Peter

Hi Peter,

Thanks for your reply.

But if it is a network timeout issue at TCP layer.

I have 2 folders that is using data uploading, one of folder normal, but other is bad.

I don't have idea for this different.

Does it work locally on the Isilon cluster, from all nodes?

If so, what happens on the Linus client when you create a full copy of the 'bad' folder?

Have you run a cluster health check? - see https://www.dell.com/support/kbdoc/en-us/000130893/dell-emc-isilon-healthcheck-isilon-info-hub 

(What has Dell support advised so far?)