On 5 December 2014 at 15:32, Chris Mason <c...@fb.com> wrote:
> On Sun, Nov 30, 2014 at 5:57 PM, Dimitri John Ledkov <x...@debian.org>
> wrote:
>>
>> On 30 November 2014 at 22:31, cwillu <cwi...@cwillu.com> wrote:
>>>
>>>
>>>  In ubuntu, the initfs runs a btrfs dev scan, which should catch
>>>  anything that would be missed there.
>>>
>>
>> I'm sorry, udev rule(s) is not sufficient in the initramfs-less case,
>> as outlined.
>>
>> In case of booting with initramfs, indeed, both Debian & Ubuntu
>> include snippets there to run btrfs scan.
>
>
> In an initramfs-less system, the root filesystem mount is done by the
> kernel, without calling any mount.btrfs.  The mount helper has all the same
> problems that calling btrfs dev scan does, it's just being run by mount.
>

Sure. in my initramfs-less system case the root filesystem was not
btrfs. Simply there was a btrfs filesystem defined in /etc/fstab.

> I definitely agree that assembling the filesystem from userland is somewhat
> awkward, and people that don't want initrds end up needing to jump through
> hoops to get things done.
>
> But, the tools we have to avoid the hoops are initrds and udev, and I'd much
> rather spend time fixing filesystem bugs than recreating those tools.  If
> people are having trouble with udev, or having trouble with tools in the
> initrd, lets contribute fixes to those projects instead.
>
> For people that really really don't want initrds, pass the devices on the
> command line.  If that isn't working, we'll fix it, but if you really want a
> scan, please try an initrd.  You can even make one without any kernel
> modules, and then you don't have to recreate it until you want to update the
> userland in your initrd.
>

The other suggestion I received is to ship a systemd unit that does
unconditional btrfs scan pre local filesystem target... =)

kernel-module-less initrd sounds cool, i'll experiment with that.

-- 
Regards,

Dimitri.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to