** Description changed:
When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the
client ends up using version 4.2 instead. This option seems to be
ignored.
This happens with pam_mount and manual mount. We have been using
pam_mount for years with the option vers=4.0, but now
Public bug reported:
When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the
client ends up using version 4.2 instead. This option seems to be
ignored.
This happens with pam_mount and manual mount. We have been using
pam_mount for years with the option vers=4.0, but now it appears to
*** This bug is a duplicate of bug 1362884 ***
https://bugs.launchpad.net/bugs/1362884
Here is the dmesg output at the time of the error message:
[8.515396] BTRFS: device fsid e91f611f-524a-43f5-bde5-8ebb9672f146 devid 2
transid 100593 /dev/dm-0
[8.525319] BTRFS info (device dm-0): e
** Package changed: ubuntu => upstart (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1426782
Title:
Boot fails with encyprted BTRFS RAID1 array - open ctree faile
4 matches
Mail list logo