Re: [arch-general] [aur-general] systemd 207 and btrfs
On Wed, Sep 18, 2013 at 9:50 PM, Curtis Shimamoto <sugar.and.scruffy@gmail.com> wrote:
On 09/18/13 at 08:31pm, Jameson wrote:
I upgraded to systemd 207 today, and upon reboot received several messages that say, "failed to open /dev/btrfs-control skipping device registration: No such file or directory."
I think you probably meant to send this to [arch-general], not [aur-general]. So I am going to send this to both… we'll see where it goes.
Right you are. It turns out if I type arch- instead of arch, my Google contact list knows what I mean. :)
Your btrfs filesystem must span more than one device, yes?
Yep. After running into different problems with both hardware RAID and mdadm for different reasons, I thought I'd give a btrfs RAID 1 volume a shot for root on my home server.
It was definitely the lack of /dev/btrfs-control that was causing the failure though, as I was getting that error message. I recall checking immediately after getting the message and seeing that /dev/btrfs-control was indeed there. So maybe this is some kind of a race condition?
It looks that way because when it gets to an emergency shell a btrfs device scan works fine.
This is just a shot in the dark, but what if you were to put the necessary modules for btrfs in mkinitcpio.conf's MODULES list to have it loaded explicitly and early?
That did it. I added btrfs, zlib_deflate, and libcrc32a. I think I had previously needed to add crc32a for a different problem I was having with multi-device btrfs volumes. Thanks so much for your help, Curtis. =-Jameson
On Thu, Sep 19, 2013 at 11:10 AM, Jameson <imntreal@gmail.com> wrote:
On Wed, Sep 18, 2013 at 9:50 PM, Curtis Shimamoto <sugar.and.scruffy@gmail.com> wrote:
This is just a shot in the dark, but what if you were to put the necessary modules for btrfs in mkinitcpio.conf's MODULES list to have it loaded explicitly and early?
That did it. I added btrfs, zlib_deflate, and libcrc32a. I think I had previously needed to add crc32a for a different problem I was having with multi-device btrfs volumes.
For what it is worth, the cause of this bug was that the creation of static device nodes (including /dev/btrfs-control) moved from systemd-udevd to systemd-tmpfiles, but we forgot to add a call to tmpfiles in the udev hook. This has now been fixed and the systemd in testing should work with btrfs without the need for adding any modules manually. Cheers, Tom
Hi On Thu, Sep 19, 2013 at 11:23 AM, Tom Gundersen <teg@jklm.no> wrote:
On Thu, Sep 19, 2013 at 11:10 AM, Jameson <imntreal@gmail.com> wrote:
On Wed, Sep 18, 2013 at 9:50 PM, Curtis Shimamoto <sugar.and.scruffy@gmail.com> wrote:
This is just a shot in the dark, but what if you were to put the necessary modules for btrfs in mkinitcpio.conf's MODULES list to have it loaded explicitly and early?
That did it. I added btrfs, zlib_deflate, and libcrc32a. I think I had previously needed to add crc32a for a different problem I was having with multi-device btrfs volumes.
For what it is worth, the cause of this bug was that the creation of static device nodes (including /dev/btrfs-control) moved from systemd-udevd to systemd-tmpfiles, but we forgot to add a call to tmpfiles in the udev hook. This has now been fixed and the systemd in testing should work with btrfs without the need for adding any modules manually.
I consider it as a severe bug. Those who use btrfs on root filesystem (like me) ended up with unbootable machine after this upgrade. Please fix it in [core] as soon as possible.
participants (3)
-
Anatol Pomozov
-
Jameson
-
Tom Gundersen