From: Nuno Silva <nuno.silva@vgertech.com>
To: Paulo da Silva <psdasilva@esoterica.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: K 2.6.9 - NFS: lstat causes "permission errors"
Date: Sat, 30 Oct 2004 05:58:53 +0100 [thread overview]
Message-ID: <41831F8D.5000606@vgertech.com> (raw)
In-Reply-To: <4182FED2.8010000@esoterica.pt>
Olá Paulo,
Paulo da Silva wrote:
> Paulo da Silva wrote:
>
>> I am getting several "permission errors" when using
>> "lstat". So far I only found this on Directories.
>> I changed a program to retry the "lstat" whenever
>> a "permission error" occurs and it works successfully.
>>
> I'm also getting "Stale NFS file handle" error when "lstat" and
> "read" a file. This seems to happen only on a VFAT filesystem
> but I am not sure.
Are you exporting a FAT fs with NFS? It's expected to break in some
situations. Read http://nfs.sourceforge.net/nfs-howto/server.html
Regards,
Nuno Silva
prev parent reply other threads:[~2004-10-30 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 19:06 K 2.6.9 - NFS: lstat causes "permission errors" Paulo da Silva
2004-10-30 2:39 ` Paulo da Silva
2004-10-30 2:44 ` Paulo da Silva
2004-10-30 4:58 ` Nuno Silva [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=41831F8D.5000606@vgertech.com \
--to=nuno.silva@vgertech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=psdasilva@esoterica.pt \
/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