** Changed in: zfs-linux (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2014784
Title:
Missing zfs-list.cache folder causes zfs list cacher to fail
To manage n
** Also affects: zfs-linux (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075941
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2014784
I reported upstream
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075941
Yours
lopiuh
** Bug watch added: Debian Bug tracker #1075941
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075941
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
The touch command would fail in that case, because the zfs-list.cache
directory does not exist and touch will not automatically create the
parent directory. So even if it's empty the folder should at least
exist, even that manpage assumes it already exists.
--
You received this bug notification b
To be more clear:
https://manpages.debian.org/testing/zfsutils-linux/zfs-mount-generator.8.en.html
states: "To begin, enable tracking for the pool:
# touch /etc/zfs/zfs-list.cache/poolname "
So I am right. The missing directory in a default state is a feature, no
bug.
Yours lopiuh
--
You recei
Hi,
isn't that by design (intended) Because zfs-zed package is installed (e
.g. default installation) but zfs-mount-generator should not be active
in every case. So if I want to finally use zfs-mount-generator I have to
manually create the /etc/zfs/zfs-list.cache folder? If it gets
"corrected" man
