Your message dated Mon, 6 Mar 2006 14:52:23 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#355481: Mount version too old for NFSv4
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: loop-aes-utils
Version: 2.12r-5
Severity: normal
Hi !
After an upgrade I was not able to mount my nfs v4 exports anymore. After one
hour and an half of investigation, I found that this package diverted the
original mount. I spent a hour and a half, but I never said I was smart.
With "mount" I got a "bad mount version", with mount.orig, it is working.
Cheers,
Romain
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Versions of packages loop-aes-utils depends on:
ii gnupg 1.4.2-2 GNU privacy guard - a free PGP rep
ii libblkid1 1.38+1.39-WIP-2005.12.31-1 block device id library
ii libc6 2.3.6-3 GNU C Library: Shared libraries an
ii libuuid1 1.38+1.39-WIP-2005.12.31-1 universally unique id library
ii mount 2.12.nfsv4-11 Tools for mounting and manipulatin
ii sharutils 1:4.2.1-15 shar, unshar, uuencode, uudecode
loop-aes-utils recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Mar 06, 2006 at 12:06:49AM +0100, Romain Chantereau wrote:
> Hi !
Hello Romain,
> After an upgrade I was not able to mount my nfs v4 exports anymore. After one
> hour and an half of investigation, I found that this package diverted the
> original mount. I spent a hour and a half, but I never said I was smart.
>
> With "mount" I got a "bad mount version", with mount.orig, it is working.
> ii mount 2.12.nfsv4-11 Tools for mounting and manipulati
^^^^^^^^^^^^^^
It looks like you are using a non-Debian version of the mount
package that was patched for nfsv4?
The packages mount (2.12r-7) and loop-aes-utils (2.12r-4) in Debian
included an nfsv4 patch for a short time. It turned out this patch
causes problems for older NFS setups (#354075) so it was dropped
shortly after. The situation is currently that loop-aes-utils follows
the mount package closely and will not support nfsv4 until the patch
gets (re-)applied to the Debian mount package.
Here is an idea: If the patch in 2.12r-4 worked for you, what you could
do is fetch the loop-aes-utils source package and do a local rebuild
with the nfsv4 patch applied - it is still included in the source
package. Just edit debian/patches/00list, un-comment 30nfs4 and rebuild.
Does this work for you?
cheers,
Max
--- End Message ---
