Skip to contentSkip to conversation

Files not visible across NFS

DISCUSSION Sai Bhushan 2 participants 2 messages Mar 15, 2007

lore
Share & tools
lore
#0 lore raw

Hi,

I am facing a problem where-in some files are not visible across NFS and hence, not able to read those files. However, after sometime, the files become visible and the data is accessible. I have tried to do an 'ls -l' operation on the directory and repeat it till the directory gets mounted and visible. This works in some cases but sometimes fails as well.

Is there any reliable way of ensuring that the directory gets mounted and all files in it are visible before accessing the data ??

Any help/pointers in this regard would be really great.

-Thanks & Regards
Sai

#1 lore raw
Quoted 8 lines · Sai Bhushan

Hi,

I am facing a problem where-in some files are not visible across NFS and hence, not able to read those files. However, after sometime, the files become visible and the data is accessible. I have tried to do an 'ls -l' operation on the directory and repeat it till the directory gets mounted and visible. This works in some cases but sometimes fails as well.

Quoted 4 lines

Is there any reliable way of ensuring that the directory gets mounted and all files in it are visible before accessing the data ??

Any help/pointers in this regard would be really great.

Hi,

Many Ubuntu users seem to be experiencing such problems on ubuntu-2.6.17 kernels:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/62308

In my experience, everything works fine as long as all directory-elements in
the path on the nfs mount are set executable for user _and_others_. If that
is not the case, files are available for about five seconds after the first
access, after which they disappear. If I try to access the file again I get
a "permission denied" message. No messages get logged.

For me, adding the "no_subtree_check" option in /etc/exports 'fixed' the problem. I'm on ubuntu-2.6.17-11-generic on amd64. This works for me:

/home 192.168.22.0/255.255.255.0(rw,sync,no_subtree_check,mp=/home,fsid=12120) /scratch 192.168.22.0/255.255.255.0(rw,sync,no_subtree_check,mp=/scratch,fsid=12121)

Anyhow, you did not give any information about your distro/kernel/hardware?

Greetings,
Alexander

Quoted 11 lines

-Thanks & Regards
Sai

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 5 lines
  Alexander van Heukelum
  [email protected]

-- 
http://www.fastmail.fm - Does exactly what it says on the tin