Re: [NFS] async vs. sync. corrupted fs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 19, 2008 at 4:54 PM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote:
> On Fri, May 16, 2008 at 12:55:59PM +0200, Chris Fanning wrote:
>> Hello all,
>>
>> Could someone help me out?
>>
>> I'm exporting a whole partition to a client.
>> Using (rw,no_root_squash,sync, no_subtree_check), when I shutdown the
>> server _before_ the client, the filesystem on the partion becomes
>> corrupted.
>
> How do you know it becomes corrupted?
>
when I boot the server it reports the partition as corrupted and I
need to perform an fsck.

>> When I user async, it doesn't happen.
>
> "async" the client-side mount option, or "async" the server-side export
> option?
server export.
(rw,no_root_squash,sync, no_subtree_check)

client mount (fstab)
nfs_home_server:/home  /home  nfs  tcp,rw  0  0

>
>> Is this normal?
>
> No.
I didn't think so ;)

Perhaps I can shed some more light on this. The client is diskless.
The problems I'm reporting are with it's /home mount. It's root
filessystem is also a nfs mount (but that is exported form a
_different_ nfs server).
I modify the nfsroot using chroot on the server.

I *think* this might be because of /proc mounted in the chroot get
exported to the client? Any insight?

I've been trying all sorts of combinations yesterday (/proc mounted
and not mounted in the chroot) and I haven't been able to reproduce
the error. Strange becuase it definitely happened when was shutting
down the nfs_home_server while everything else was up and running.

Perahps it is also worth noting that I'm booting the client with
live-initramfs. /home gets mounted after the real
filesystem(aufs,nfs+ram) comes up.
Once the client has booted I can use /home. But it doesn't show up
using 'df', and it is not present in /etc/mtab
However it does show up in /proc/mounts
nfs_home_server:/home /home nfs
rw,vers=3,rsize=32768,wsize=23768,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=192.168.2.2
0 0

Sorry for the convulated reply.
Thanks.
Chris.

>
>> The exports manpage suggests that 'sync' is the better option.
>
> Yes.
>
> --b.
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@xxxxxxxxxxxxxxxxxxxxx is being discontinued.
Please subscribe to linux-nfs@xxxxxxxxxxxxxxx instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux