Bug 5184

Summary: When halting umounting LVM (encrypted?) is broken
Product: Mageia Reporter: Kamil Rytarowski <n54>
Component: RPM PackagesAssignee: Colin Guthrie <mageia>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: mageia
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: systemd CVE:
Status comment:
Bug Depends on: 5159    
Bug Blocks: 2120    
Attachments: dm errors

Description Kamil Rytarowski 2012-04-01 22:34:01 CEST 
+++ This bug was initially created as a clone of Bug #5159 +++

Description of problem:
Hi!

I'm doing minimal installation (without X Window), and I got when halting error that are visible on the attachement

My partitions
sda1 /boot
sda2 encrypted LVM
* /
* swap
* /home


Steps to Reproduce:
1. network installation (nonfree iso)
2. see errors at halt time
Comment 1 Kamil Rytarowski 2012-04-01 22:34:29 CEST 
Created attachment 1893 [details]
dm errors
Comment 2 Colin Guthrie 2012-04-09 13:44:33 CEST 
Reproduced here in my VM.

Passing acpi=off on the command line makes the messages vaguely readable too :D

Status: NEW => ASSIGNED

Colin Guthrie 2012-04-09 13:44:39 CEST

Assignee: bugsquad => mageia

Comment 3 Colin Guthrie 2012-04-09 14:54:14 CEST 
Should be fixed in latest dracut. Systemd will still output these messages, but it is impossible for systemd to do more here anyway (it could in theory be a little cleverer about how to tear down DM's such that it won't even try to tear down the DM if the rootfs is somewhere within it, but that's a mostly cosmetic issue really).

The difference now is that dracut will take over again, and do it's own tidy up of stuff.

Sadly after all this, it still seems that dracut doesn't actually shutdown the LVM or crypt anyway (I cannot see any shutdown hooks to call vgchange -an) but this is an upstream problem. We can't realistically do much more than this (other than by patching dracut, but I'm sure this is on the roadmap anyway and this is already better than we were able to do before with sysvinit and mkinitrd so I thing that's an improvement.

Therefore, closing.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Comment 4 Kamil Rytarowski 2012-04-09 21:22:35 CEST 
(In reply to comment #3)
> Should be fixed in latest dracut. Systemd will still output these messages, but
> it is impossible for systemd to do more here anyway (it could in theory be a
> little cleverer about how to tear down DM's such that it won't even try to tear
> down the DM if the rootfs is somewhere within it, but that's a mostly cosmetic
> issue really).
> 
> The difference now is that dracut will take over again, and do it's own tidy up
> of stuff.
> 
> Sadly after all this, it still seems that dracut doesn't actually shutdown the
> LVM or crypt anyway (I cannot see any shutdown hooks to call vgchange -an) but
> this is an upstream problem. We can't realistically do much more than this
> (other than by patching dracut, but I'm sure this is on the roadmap anyway and
> this is already better than we were able to do before with sysvinit and
> mkinitrd so I thing that's an improvement.
> 
> Therefore, closing.

Thank you for fixing it. Please report it upstream.