-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changed systemd unit ordering with 0.7.4 (zfs-mount/local-fs.target) #6953
Comments
what does |
not familiar with rpm packaging, but possibly systemd_svcs in https://github.com/zfsonlinux/zfs/blob/master/rpm/generic/zfs.spec.in#L225 is missing the newly introduced zfs-import.target (#6764), which is thus not enabled on upgrades? |
Note that there's some weird ordering here, Looking at a system that still runs 0.7.3 I cannot immediately figure out why From 0.7.4:
So |
|
Enabling |
duplicate: #6951 |
thanks for the heads-up (still using 6.5.11 here) |
@Fabian-Gruenbichler can we get a PR opened to update the packaging to include
|
So might be worth mentioning in the release notes also... I did the upgrade, wasn't aware of this change when I did - so naturally rebooted. System booted up into the dracut emergency shell; running a zfs root. It wasn't immediately obvious what was wrong due to me not being able to enter my root password, I think due to keyboard layouts over ipmi. So came across this issue and had to chroot into the system to enable the zfs-import target, rebooted still went into the emergency shell. chrooted back into the system, examined the previous boot journal and it transpired the file system was failing to mount due to the target directory not being empty. I believe this is because I (like many probably) am using a mixture of legacy and native zfs mounts for my root filesystem, before zfs-import was enabled I imagine the legacy ones succeeded where as the native mounts did not. So in summary a very simple problem, but not an obvious one. |
Add missing zfs-import.target to list of systemd services in zfs RPM spec file. Reviewed-by: Niklas Wagner <[email protected]> Reviewed-by: Giuseppe Di Natale <[email protected]> Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Ralf Ertzinger <[email protected]> Issue #6953 Closes #6955
Fix merged to master and a notice was added to the top of the zfs-0.7.4 release notes. |
FYI: The manual workaround here is to simply run the zfs mount command on your pool, |
Isn't this bug severe enough that a 0.7.4.1 hotfix should be released? |
I don't believe so, users have had to maintain systemd services in the past, such as 0.6.5.8 release. |
So "users get thrown into emergency mode" is not a severe bug in your eyes? Wow. |
For what it's worth, gentoo tells you to add the services to openrc after installation... I don't use systemd personally, but I imagine it does the same there. If your package manager doesn't tell you anything, I think that's more a problem of the package manager than the zfs packages themselves.
|
Something similar also appears to be happening with the Ubuntu ZFS PPA. |
systemd does the right thing here, the unit was not marked as to be started
automatically after installation, so it didn't.
Redhat based systems in general don't ask questions during packet
installation
A 0.7.4-2 RPM has been spun with this fixed, so this can be closed I believe.
December 16, 2017 11:49 AM, "bunder2015" <[email protected] (mailto:%22bunder2015%22%20<[email protected]>)> wrote:
For what it's worth, gentoo tells you to add the services to openrc after installation... I don't use systemd personally, but I imagine it does the same there. If your package manager doesn't tell you anything, I think that's more a problem of the package manager than the zfs packages themselves.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (#6953 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/AFfh5VBg-1_nz6CgjfkcUOYSwhkElcxQks5tA5_0gaJpZM4RAdeR).
|
Ubuntu ZFS PPA author has pushed a fix. |
This fix will be included in 0.7.5 which will be released this week. And as previously mentioned the needed fix has been picked up in the packaging for the at least the EPEL, Fedora, Ubuntu PPA and Debian repositories. |
Add missing zfs-import.target to list of systemd services in zfs RPM spec file. Reviewed-by: Niklas Wagner <[email protected]> Reviewed-by: Giuseppe Di Natale <[email protected]> Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Ralf Ertzinger <[email protected]> Issue #6953 Closes #6955
https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.5 is out and should have all the necessary fixes. |
FWIW, I upgraded 0.7.3 to 0.7.5 on CentOS 7, and I still had to enable zfs-import.target manually. |
Add missing zfs-import.target to list of systemd services in zfs RPM spec file. Reviewed-by: Niklas Wagner <[email protected]> Reviewed-by: Giuseppe Di Natale <[email protected]> Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Ralf Ertzinger <[email protected]> Issue openzfs#6953 Closes openzfs#6955
Add missing zfs-import.target to list of systemd services in zfs RPM spec file. Reviewed-by: Niklas Wagner <[email protected]> Reviewed-by: Giuseppe Di Natale <[email protected]> Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Ralf Ertzinger <[email protected]> Issue openzfs#6953 Closes openzfs#6955
Hi, FYI: -I. |
System information
Describe the problem you're observing
In 0.7.3 zfs-mount.service ran (and completed) before local-fs.target, meaning all file systems on the pool were available before most services on the system started.
With 0.7.4 this does no longer seem to be the case, local-fs.target is reached before zfs file systems are mounted. Also, many file systems remain completely unmounted.
I've seen comments in the release notes that there is now a zfs-import.target, but I'm unsure how this relates to this issue exactly.
Affected file systems which have the 'mountpoint' and 'canmount' property set, but are not legacy in the sense that they're mounted via fstab.
Describe how to reproduce the problem
Update to 0.7.4, reboot
The text was updated successfully, but these errors were encountered: