Your message dated Mon, 27 Jan 2014 12:47:24 +0100 with message-id <[email protected]> and subject line USe newer linux kernel fixes this bug has caused the Debian Bug report #676883, regarding fai-nfsroot: fai nfsclient fails to mount nfsv4 volumes properly to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 676883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676883 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: fai-nfsroot Version: 4.0.1 Severity: important A FAI nfsclient does not mount NFSv4 volumes properly. Most of the files/directories belonging to root belong to 'nobody' instead. 'most' is important. Some files are properly mapped belonging to root, so it is not a simple idmap-mismatch issue. Confirmed for: Debian Wheezy and Sid Impact: Installation via FAI is not possible. If aufs is used, then the install client kernel-panics. If a simple rw-mount is used, then one is at least able to see which files belong to nobody and which files belong to root. Workaround/Wheezy: Set 'nfsvers=3' option in the clients pxelinux cfg file. Workaround/Sid: None known to me. Sid nfsclient/kernel is not able to mount v3 Reason: Unknown. Solution: Unknown. # dpkg -l dracut-network linux-image-3.2.0-2-amd64 nfs-common Name Version ii dracut-network 019+1+gd77540c-1 ii linux-image-3.2.0-2-amd64 3.2.19-1 ii nfs-common 1:1.2.6-2
--- End Message ---
--- Begin Message ---Closing this bug, as it is fixed when using a newer linux kernel version, for e.g. inux-image-3.12-0.bpo.1-amd64. -- regards Thomas
--- End Message ---
