linux-kernel - Re: Mounting NFS root FS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0701250121410.10972@yvahk01.tjqt.qr>
Date:	Sat, 27 Jan 2007 15:47:36 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Trond Myklebust <trond.myklebust@....uio.no>
cc:	Janne Karhunen <Janne.Karhunen@...il.com>, MrUmunhum@...dial.com,
	linux-kernel@...r.kernel.org
Subject: Re: Mounting NFS root FS


On Dec 5 2006 15:12, Trond Myklebust wrote:
>On Tue, 2006-12-05 at 20:59 +0100, Jan Engelhardt wrote:
JE>>>> Since we're on the topic locking, is it because I am not running
JE>>>> statd on the client that my NFS client hangs during boot phase?
TM>>>
TM>>>If you have applications that try to set locks before rpc.statd is up
TM>>>and running, then that would explain it.
JE>> 
JE>>Even if the nfs mount is mounted using -o ro,nolock?
TM>
TM>No. The 'nolock' option means that the NFS client will use the VFS posix
TM>locks only, which will not depend on rpc.statd.
TM>

By trying a little I found out that it is unionfs which has problems 
with locking.
So on the NFS side (nfs-only, no unionfs above it) all is fine.


	-`J'
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/