On Sun, Nov 30, 2014 at 5:57 PM, Dimitri John Ledkov <xnox@xxxxxxxxxx>
wrote:
On 30 November 2014 at 22:31, cwillu <cwillu@xxxxxxxxxx> 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.
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.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
