public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander van Heukelum" <heukelum@fastmail.fm>
To: sbhushan@cadence.com, linux-kernel@vger.kernel.org
Subject: Re: Files not visible across NFS
Date: Thu, 15 Mar 2007 15:25:59 +0100	[thread overview]
Message-ID: <1173968759.13755.1179613375@webmail.messagingengine.com> (raw)
In-Reply-To: <45F92C1E.2040604@cadence.com>

On Thu, 15 Mar 2007 16:51:02 +0530, "Sai Bhushan" <sbhushan@cadence.com>
said:
> 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.

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

> -Thanks & Regards
> Sai
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 
-- 
  Alexander van Heukelum
  heukelum@fastmail.fm

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


      reply	other threads:[~2007-03-15 14:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 11:21 Files not visible across NFS Sai Bhushan
2007-03-15 14:25 ` Alexander van Heukelum [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1173968759.13755.1179613375@webmail.messagingengine.com \
    --to=heukelum@fastmail.fm \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sbhushan@cadence.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox