diff options
author | Brian Behlendorf <[email protected]> | 2017-06-07 10:59:44 -0700 |
---|---|---|
committer | Tony Hutter <[email protected]> | 2017-06-09 14:05:15 -0700 |
commit | 590509b75e899a769a47744cba2ab41fda5f85ce (patch) | |
tree | c49a606aef4b0680a1583bfa89d7fb027ecc3074 /rpm/generic/zfs.spec.in | |
parent | d07a8deac85e9ef2af5c158dfcd0d8b9e3743cc0 (diff) |
Add MS_MANDLOCK mount failure message
Commit torvalds/linux@9e8925b6 allowed for kernels to be built
without support for mandatory locking (MS_MANDLOCK). This will
result in 'zfs mount' failing when the nbmand=on property is set
if the kernel is built without CONFIG_MANDATORY_FILE_LOCKING.
Unfortunately we can not reliably detect prior to the mount(2) system
call if the kernel was built with this support. The best we can do
is check if the mount failed with EPERM and if we passed 'mand'
as a mount option and then print a more useful error message. e.g.
filesystem 'tank/fs' has the 'nbmand=on' property set, this mount
option may be disabled in your kernel. Use 'zfs set nbmand=off'
to disable this option and try to mount the filesystem again.
Additionally, switch the default error message case to use
strerror() to produce a more human readable message.
Reviewed-by: George Melikov <[email protected]>
Reviewed-by: Giuseppe Di Natale <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #4729
Closes #6199
Diffstat (limited to 'rpm/generic/zfs.spec.in')
0 files changed, 0 insertions, 0 deletions