[Expired for zfs-linux (Ubuntu) because there has been no activity for
60 days.]
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
It might be also a result of the bogus mount.zfs, which requires POSIX
incorrect arguments but honors POSIXLY_CORRECT env var!
Had a similar zfs mount order problem with a rpool/local/home/{A,B,C}
tree (was created using -p option) ...
--
You received this bug notification because you are a memb
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694090
Title:
ZoL: wrong import order prevents boot
To manage notifications about th
The output only shows the results, not the order of mount attempts. It
may be the case that there is an ordering bug here. But we need to rule
out the other case first. It could easily be the case that the directory
is non-empty, so the /var/share mount failed even though it was properly
attempted
Please read carefully before answering: As already said (and the given
output clearly shows the problem beside being mentioned in the subject):
zfs screwed up the mount order and mounted rpool/VARSHARE/lxc _before_
rpool/VARSHARE. And when /var/share/lxc gets mounted, obviously
/var/share is not em
This is the problem:
'/var/share': directory is not empty
Figure out what is in there and deal with this appropriately.
I don't personally love that ZFS refuses to mount on non-empty
directories, but most of the time, the fact that the directory is non-
empty is the real problem.
** Changed in:
