Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/28/2015 08:40 PM, Andrei Borzenkov wrote: Try booting with udev.log-priority=debug rd.udev.log-priority=debug, this may give some hint what happens. Wow did that produce a lot of output! No. You can set nofail in which case boot will proceed and you can mount it manually later. I added the nofail flag to /home and mounts below it, along with the udev flags above. Booting at least got me to a login screen instead of the emergency shell. I was then able to login at a virtual console, checked /home was not mounted, and mount -a quite happily mounted it and the system works. I have attached the output of journalctl -b which has all the udev output as well as everything else. That is fulljournal.txt.gz. Separately my laptop has two drives, and I have 3 luks+dmcrypt partitions. One of them is for swap, and two of them are in RAID0 for a single btrfs filesystem that contains / and /home subvolumes. The initrd does the keysetup and decryption, long before systemd is involved. My boot time with systemd has become several minutes, but eventually succeeds. Looking in the log (attached as laptop.txt.gz), it too has messages about waiting for disk devices and eventually timing out, but the system eventually boots compared to the desktop emergency shell. It seems there is something very confused going on between the initrd, udev and systemd, especially noticeable if you have btrfs across multiple partitions and the same partitions are already mounted for root by initrd. Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlVoqb0ACgkQmOOfHg372QRi4QCgp1GNeKJ4UIPqAVtI7vkGzpwE u7cAn1aAiBolnDd4xBIlQETTR+0nmUji =0DRw -END PGP SIGNATURE- fulljournal.txt.gz Description: application/gzip laptop.txt.gz Description: application/gzip ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/28/2015 02:37 AM, Andrei Borzenkov wrote: I was wrong here, device is opened by btrfs driver so there should be no collision here. Still obviously scanning fails (and it fails actively, setting ID_BTRFS_READY). This needs some debugging on udev side. I just tried booting with fsck.mode=skip and that didn't make any difference, seemingly supporting your diagnosis (it being the device stage rather than fsck stage where the problem lies). Note that this problem is very silly. The systemd binary is running from the very devices it claims aren't ready! If it actually tried to mount /home then it would succeed every time. Prior to Ubuntu 15.04/systemd, I had my drives in a different configuration. My motherboard has two SATA controllers, each with 4 ports (one is Intel, one is ASMedia). I had the two drives making up / and /home on different controllers, and everything worked fine. My hypothesis is that the boot sequence looked like this: 1. Wait for all storage controllers and all devices on them to be enumerated 2. Run btrfs device scan 3. Mount root and pivot 4. Within new root, attempt to mount everything in /etc/fstab without any detection of availability etc With 15.04 (both upstart and systemd, hence blame likely lying with initrd+udev), things look concurrent: 1. Enumerate storage controllers and all devices on them 1. Simultaneously run btrfs device scan each time a new device is found 1. Simultaneously, the moment /dev/disk/by-uuid/ROOTUUID shows up, attempt to mount root filesystem With the two halves of the btrfs filesystem on different controllers, mounting of root failed. Doing so at the emergency root shell worked just fine. I had to rewire my drives so they were on the same controller which fixed this issue. Is there any more information I can gather to make progress on this issue? Does systemd support any flags in /etc/fstab where I can tell it just go ahead and mount instead of waiting for devices? Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlVnYVMACgkQmOOfHg372QTLMwCfRUnluXxvRsRvFTULJ0Y1ORZO 5SkAnR8rM6++4yePhel+nfPlUNh/iRfN =UF1T -END PGP SIGNATURE- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Thu, 28 May 2015 11:41:27 -0700 Roger Binns rog...@rogerbinns.com пишет: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/28/2015 02:37 AM, Andrei Borzenkov wrote: I was wrong here, device is opened by btrfs driver so there should be no collision here. Still obviously scanning fails (and it fails actively, setting ID_BTRFS_READY). This needs some debugging on udev side. I just tried booting with fsck.mode=skip and that didn't make any difference, seemingly supporting your diagnosis (it being the device stage rather than fsck stage where the problem lies). ... Is there any more information I can gather to make progress on this issue? Try booting with udev.log-priority=debug rd.udev.log-priority=debug, this may give some hint what happens. You can also try to enable debug logging after boot (udevadm control - -l debug) and trigger event by issuing echo add /sys/block/sda/sda1/uevent Does systemd support any flags in /etc/fstab where I can tell it just go ahead and mount instead of waiting for devices? No. You can set nofail in which case boot will proceed and you can mount it manually later. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlVn36QACgkQR6LMutpd94yO0QCfbuLIGqrGv0Bmv5diFwBMJCs9 phcAnivLXey85bM4XkuBbIHhS7k2lDO0 =+WoA -END PGP SIGNATURE- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
Am 28.05.2015 um 07:24 schrieb Martin Pitt: Reindl Harald [2015-05-28 1:00 +0200]: Am 27.05.2015 um 23:03 schrieb Roger Binns: My immediate problem is a boot failure with systemd on Ubuntu 15.04 because of fsck issues (systemd timing out fscking something it shouldn't) sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1217969 Out of interest, why does it sound the same? Roger's specific situation is that he has a btrfs device which is spread over multiple partitions, and all these partitions have the exact same UUID. Do you actually have that as well? The bug report doesn't mention that, or a blkid output etc.; I'd say that this kind of striped btrfs is a special case enough to at least be worth mentioning it sounds similar because something is running in a timeout and break boot instead wait for the fsck to finish, in my case it's a at that time slow host system a fsck should not timeout and lead in an emergency shell because when you imagine a really large volume with multible TB it may take a long time signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
On Thu, May 28, 2015 at 8:46 AM, Andrei Borzenkov arvidj...@gmail.com wrote: Apr 24 14:18:41 workstation systemd[1]: Job dev-disk-by\x2duuid-3ff68715\x2d0daa\x2d4e44\x2d8de2\x2d0997f36d8ab6.device/start timed out. systemd times out waiting for UUID alias. Neither sda1 nor sdb1 are present in list of active device units. Please show udevadm info -q all -n sda1 and udevadm info -q all -n sdb1 after boot. OK, found them in bug report. As expected P: /devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 E: ID_BTRFS_READY=0 E: SYSTEMD_READY=0 P: /devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb1 E: ID_BTRFS_READY=0 E: SYSTEMD_READY=0 Something is wrong with scanning for btrfs either in initrd or in running system. Hmm ... looking in kernel, btrfs_scan_one_device tries to open device exclusively. If device is already mounted, it will likely fail. I was wrong here, device is opened by btrfs driver so there should be no collision here. Still obviously scanning fails (and it fails actively, setting ID_BTRFS_READY). This needs some debugging on udev side. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 My immediate problem is a boot failure with systemd on Ubuntu 15.04 because of fsck issues (systemd timing out fscking something it shouldn't). Prior Ubuntu releases and upstart work just fine. Martin Pitt @ Ubuntu said I should bring the issue here in the Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879 I have 6 drives in my system. Two identical 960GB SSDs (model, firmware etc all the same, only serial number difference), another two identical 256GB SSDs (same story), and two spinning drives. Of note is that my root and /home are both btrfs subvolumes of a RAID0 btrfs using the two first SSDs. /etc/fstab has these two lines for them (wrapped by email client): UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 / btrfs defaults,autodefrag,compress=lzo,subvol=@ 0 1 UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home btrfs defaults,autodefrag,compress=lzo,subvol=@home 0 2 blkid output mentioning that UUID: /dev/sda1: LABEL=main UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 UUID_SUB=12243c27-9502-4a1e-b1d1-d1998107b9e4 TYPE=btrfs PARTUUID=011a8e03-01 /dev/sdb1: LABEL=main UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 UUID_SUB=abda2c4f-3346-44e5-b32e-7c1bba0ba728 TYPE=btrfs PARTUUID=1537012a-01 What happens is that / is mounted successfully, as are all the other filesystems that aren't /home or mounted below /home. There will be a message about waiting for fsck either including the UUID above, or CT960M500SSD1 (drive id), and after 1m30s it times out and dumps me in a root shell. The devices/partitions are already mounted as root, so no amount of further checking makes sense. If it just went ahead and mounted the @home subvolume it would be fine. Instead systemd is unhelpfully timing out, without any diagnostics as to why it is trying this and why it doesn't succeed. Note that /sbin/fsck.btrfs is a shell script (Suse/SGI copyright) that just prints out BTRFS file system if the device node exists - and doesn't do anything else. The Ubuntu bug report includes numerous attachments with various systemctl and similar outputs, full /etc/fstab etc. I'll happily capture whatever else can help diagnose and fix this problem. Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlVmMQoACgkQmOOfHg372QQ7xgCgy1K0bak/EEy+7YcNR2YZSFcD GxUAn293LNyeEYpQMIqKv5KNMLaEcv9G =Ms/5 -END PGP SIGNATURE- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Thu, 28 May 2015 08:27:30 +0300 Andrei Borzenkov arvidj...@gmail.com пишет: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Wed, 27 May 2015 14:03:10 -0700 Roger Binns rog...@rogerbinns.com пишет: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 My immediate problem is a boot failure with systemd on Ubuntu 15.04 because of fsck issues (systemd timing out fscking something it shouldn't). Prior Ubuntu releases and upstart work just fine. Martin Pitt @ Ubuntu said I should bring the issue here in the Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879 I have 6 drives in my system. Two identical 960GB SSDs (model, firmware etc all the same, only serial number difference), another two identical 256GB SSDs (same story), and two spinning drives. Of note is that my root and /home are both btrfs subvolumes of a RAID0 btrfs using the two first SSDs. /etc/fstab has these two lines for them (wrapped by email client): UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 / btrfs defaults,autodefrag,compress=lzo,subvol=@ 0 1 UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home btrfs defaults,autodefrag,compress=lzo,subvol=@home 0 2 blkid output mentioning that UUID: /dev/sda1: LABEL=main UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 UUID_SUB=12243c27-9502-4a1e-b1d1-d1998107b9e4 TYPE=btrfs PARTUUID=011a8e03-01 /dev/sdb1: LABEL=main UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 UUID_SUB=abda2c4f-3346-44e5-b32e-7c1bba0ba728 TYPE=btrfs PARTUUID=1537012a-01 Apr 24 14:18:41 workstation systemd[1]: Job dev-disk-by\x2duuid-3ff68715\x2d0daa\x2d4e44\x2d8de2\x2d0997f36d8ab6.device/start timed out. systemd times out waiting for UUID alias. Neither sda1 nor sdb1 are present in list of active device units. Please show udevadm info -q all -n sda1 and udevadm info -q all -n sdb1 after boot. OK, found them in bug report. As expected P: /devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 E: ID_BTRFS_READY=0 E: SYSTEMD_READY=0 P: /devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb1 E: ID_BTRFS_READY=0 E: SYSTEMD_READY=0 Something is wrong with scanning for btrfs either in initrd or in running system. What happens is that / is mounted successfully, as are all the other filesystems that aren't /home or mounted below /home. If your initrd does not properly enters information in udev database, this would explain the problem. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlVmp0IACgkQR6LMutpd94zQdgCeI0gZeEHLvobg0+BNCYO8BKzp nOAAn0W2E4aZC8qrzxeyEHERfYSVKqHR =4XiK -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlVmqM8ACgkQR6LMutpd94yrnQCfbHjRJnIrobWkmUUUsKk+LPZX IxoAmwcITeP9AWYY3PtLqGOGndSnnSJg =z+cT -END PGP SIGNATURE- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/27/2015 04:00 PM, Reindl Harald wrote: sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1217969 Thanks for the pointer. I think my situation is different but it does show that I should test with fsck.mode=skip and hopefully systemd will skip whatever is confusing it. I only have one non-btrfs filesystem (/boot ext4) so I don't need fsck that much anyway. Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlVmVG8ACgkQmOOfHg372QTxSACdFW+pZfRWBywf4/eoaM3TgTYR +skAoIIu8KbEuHroZeyW/jFLePCxH4Tv =Nfmt -END PGP SIGNATURE- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
Reindl Harald [2015-05-28 1:00 +0200]: Am 27.05.2015 um 23:03 schrieb Roger Binns: My immediate problem is a boot failure with systemd on Ubuntu 15.04 because of fsck issues (systemd timing out fscking something it shouldn't) sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1217969 Out of interest, why does it sound the same? Roger's specific situation is that he has a btrfs device which is spread over multiple partitions, and all these partitions have the exact same UUID. Do you actually have that as well? The bug report doesn't mention that, or a blkid output etc.; I'd say that this kind of striped btrfs is a special case enough to at least be worth mentioning. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Thu, 28 May 2015 08:34:07 +0300 Andrei Borzenkov arvidj...@gmail.com пишет: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Thu, 28 May 2015 08:27:30 +0300 Andrei Borzenkov arvidj...@gmail.com пишет: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Wed, 27 May 2015 14:03:10 -0700 Roger Binns rog...@rogerbinns.com пишет: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 My immediate problem is a boot failure with systemd on Ubuntu 15.04 because of fsck issues (systemd timing out fscking something it shouldn't). Prior Ubuntu releases and upstart work just fine. Martin Pitt @ Ubuntu said I should bring the issue here in the Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879 I have 6 drives in my system. Two identical 960GB SSDs (model, firmware etc all the same, only serial number difference), another two identical 256GB SSDs (same story), and two spinning drives. Of note is that my root and /home are both btrfs subvolumes of a RAID0 btrfs using the two first SSDs. /etc/fstab has these two lines for them (wrapped by email client): UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 / btrfs defaults,autodefrag,compress=lzo,subvol=@ 0 1 UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home btrfs defaults,autodefrag,compress=lzo,subvol=@home 0 2 blkid output mentioning that UUID: /dev/sda1: LABEL=main UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 UUID_SUB=12243c27-9502-4a1e-b1d1-d1998107b9e4 TYPE=btrfs PARTUUID=011a8e03-01 /dev/sdb1: LABEL=main UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 UUID_SUB=abda2c4f-3346-44e5-b32e-7c1bba0ba728 TYPE=btrfs PARTUUID=1537012a-01 Apr 24 14:18:41 workstation systemd[1]: Job dev-disk-by\x2duuid-3ff68715\x2d0daa\x2d4e44\x2d8de2\x2d0997f36d8ab6.device/start timed out. systemd times out waiting for UUID alias. Neither sda1 nor sdb1 are present in list of active device units. Please show udevadm info -q all -n sda1 and udevadm info -q all -n sdb1 after boot. OK, found them in bug report. As expected P: /devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 E: ID_BTRFS_READY=0 E: SYSTEMD_READY=0 P: /devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb1 E: ID_BTRFS_READY=0 E: SYSTEMD_READY=0 Something is wrong with scanning for btrfs either in initrd or in running system. Hmm ... looking in kernel, btrfs_scan_one_device tries to open device exclusively. If device is already mounted, it will likely fail. That explains ID_BTRFS_READY=0. I suppose, udev should first check whether device is part of mounted filesystem, at which point it obviously is present and active. Or should this logic better go into kernel handling of BTRFS_IOC_DEVICES_READY? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlVmq80ACgkQR6LMutpd94xWaACbBPiw4MViBo846fW38o83Wo5U XGQAnRH0HOlnGAbG+QatWHV3/T5T00Qn =A2z8 -END PGP SIGNATURE- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Wed, 27 May 2015 14:03:10 -0700 Roger Binns rog...@rogerbinns.com пишет: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 My immediate problem is a boot failure with systemd on Ubuntu 15.04 because of fsck issues (systemd timing out fscking something it shouldn't). Prior Ubuntu releases and upstart work just fine. Martin Pitt @ Ubuntu said I should bring the issue here in the Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879 I have 6 drives in my system. Two identical 960GB SSDs (model, firmware etc all the same, only serial number difference), another two identical 256GB SSDs (same story), and two spinning drives. Of note is that my root and /home are both btrfs subvolumes of a RAID0 btrfs using the two first SSDs. /etc/fstab has these two lines for them (wrapped by email client): UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 / btrfs defaults,autodefrag,compress=lzo,subvol=@ 0 1 UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home btrfs defaults,autodefrag,compress=lzo,subvol=@home 0 2 blkid output mentioning that UUID: /dev/sda1: LABEL=main UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 UUID_SUB=12243c27-9502-4a1e-b1d1-d1998107b9e4 TYPE=btrfs PARTUUID=011a8e03-01 /dev/sdb1: LABEL=main UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 UUID_SUB=abda2c4f-3346-44e5-b32e-7c1bba0ba728 TYPE=btrfs PARTUUID=1537012a-01 Apr 24 14:18:41 workstation systemd[1]: Job dev-disk-by\x2duuid-3ff68715\x2d0daa\x2d4e44\x2d8de2\x2d0997f36d8ab6.device/start timed out. systemd times out waiting for UUID alias. Neither sda1 nor sdb1 are present in list of active device units. Please show udevadm info -q all -n sda1 and udevadm info -q all -n sdb1 after boot. What happens is that / is mounted successfully, as are all the other filesystems that aren't /home or mounted below /home. If your initrd does not properly enters information in udev database, this would explain the problem. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlVmp0IACgkQR6LMutpd94zQdgCeI0gZeEHLvobg0+BNCYO8BKzp nOAAn0W2E4aZC8qrzxeyEHERfYSVKqHR =4XiK -END PGP SIGNATURE- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
Am 27.05.2015 um 23:03 schrieb Roger Binns: My immediate problem is a boot failure with systemd on Ubuntu 15.04 because of fsck issues (systemd timing out fscking something it shouldn't) sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1217969 signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
