From: David Ford <david+cert@blue-labs.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: nfs@lists.sourceforge.net, James Pearson <james-p@moving-picture.com>
Subject: Re: NFS problems across reboot
Date: Sun, 07 Apr 2002 01:48:52 -0500 [thread overview]
Message-ID: <3CAFEBD4.9030708@blue-labs.org> (raw)
In-Reply-To: 15535.56536.237108.198660@notabene.cse.unsw.edu.au
I'm not using XFS, I'm using NFS. Originating filesystems are reiserfs
and ext2, doesn't make a difference.
-d
Neil Brown wrote:
>On Sunday April 7, neilb@cse.unsw.edu.au wrote:
>
>>13 == EACCES. Looks like the filesystem isn't exported.
>>
>>Show us the relevent /etc/init.d file.
>>My guess is that "exportfs -a" is being run *After* rpc.nfsd.
>>It must must run *before* for correct operation.
>>
>
>Actually, that would cause ESTALE, not EACCES.
>
>EACCES seems to suggest an XFS problem.
>Can you duplicate this without using XFS????
>
>NeilBrown
>
>>NeilBrown
>>
>>_______________________________________________
>>NFS maillist - NFS@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/nfs
>>
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-04-07 6:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 19:27 NFS problems across reboot David Ford
2002-04-05 9:12 ` James Pearson
2002-04-07 4:43 ` David Ford
2002-04-07 5:23 ` Neil Brown
2002-04-07 5:44 ` Neil Brown
2002-04-07 6:48 ` David Ford [this message]
2002-04-08 13:42 ` James Pearson
2002-04-08 15:23 ` James Pearson
2002-04-08 23:10 ` Neil Brown
2002-04-07 6:39 ` Daniel Freedman
2002-04-08 2:50 ` Neil Brown
2002-04-07 6:59 ` David Ford
2002-04-08 2:48 ` Neil Brown
2002-04-08 12:15 ` Andreas Unterluggauer
2002-04-08 22:58 ` Neil Brown
[not found] <E16uI1v-00067H-00@usw-sf-list1.sourceforge.net>
2002-04-08 0:43 ` Al Borchers
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=3CAFEBD4.9030708@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=james-p@moving-picture.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.