[systemd-bugs] [Bug 51220] New: systemd fails to unmount an atypical block-device setup

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=51220

             Bug #: 51220
           Summary: systemd fails to unmount an atypical block-device
                    setup
    Classification: Unclassified
           Product: systemd
           Version: unspecified
          Platform: All
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
        AssignedTo: systemd-bugs at lists.freedesktop.org
        ReportedBy: anonymous at dodgeit.com
         QAContact: systemd-bugs at lists.freedesktop.org


lsblk:
NAME        MAJ:MIN RM   SIZE RO TYPE   MOUNTPOINT
sda           8:0    0 698,7G  0 disk   
├─sda1        8:1    0    65M  0 part   /boot
├─sda2        8:2    0     4M  0 part   
├─sda3        8:3    0    80M  0 part   
│ └─md0       9:0    0    84M  0 linear 
│   └─md0p1 259:0    0    80M  0 md     
├─sda4        8:4    0   4,1G  0 part   [SWAP]
├─sda5        8:5    0    13G  0 part   /
└─sda6        8:6    0   678G  0 part   /home
sr0          11:0    1  1024M  0 rom    
loop0         7:0    0     4M  0 loop   
└─md0         9:0    0    84M  0 linear 
  └─md0p1   259:0    0    80M  0 md     

This setup is to enable me to access /dev/sda3 from within QEMU. loop0 points
to an image file containing MBR, on the /home partition. Sometimes when I
shutdown I forget to disassemble the md0 device, and systemd fails to do so
automatically; on next boot, some file systems need to recover from their
journals. A bit annoying.

Apparently block-device dependency information like this is available to lsblk,
and losetup -a will reveal which file a loop device points to. systemd could
probably also make use of that.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.