On Sun, Apr 26, 2015 at 03:32:26PM +0000, Hugo Mills wrote:
> The usual reason for this is that btrfs dev scan isn't being run
> properly. It's usually handled by udev -- most distributions will put
> the appropriate hooks in their udev configuration if you have the
> distribution's btrfs-progs package installed. If you have only a
> self-built btrfs-progs from git installed, then the udev hooks
> probably aren't there, and you'll need to configure it yourself (or
> arrange to have btrfs dev scan run after the cryptsetup open
> operation).
Ah, yes, that makes more sense.
I do have package and the rules:
gargamel:~# dpkg -L btrfs-tools
/.
/lib
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/80-btrfs-lvm.rules
/lib/udev/rules.d/70-btrfs.rules
But it's very possible that udev isn't working properly or timely on
this system.
I added "btrfs device scan" to /etc/init.d/cryptdisks
Thanks for the help.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
--
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
