© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f399f05
demo site
(Get the code!)
juliank: unset right before and restore after the call. It would not screw up anything. The user does not know, what the script does (and IIRC it didn't call zfs.mount in pre-focal versions). So the script has to take care of what it does.
xnox: I do not think, that this fixed the problem. Just export POSIXLY_CORRECT=1 and run a zfs create command - it will fail to mount the new fs for the same reason.
IIRC linux mount (used by zfs mount last time I digged the code) requires arguments to be in a non-posix compatible order. So ZFS can't do anything about it, except to unset POSIXLY_CORRECT or to rewrite the mount code to avoids the linux-mount invocation ...