Filesystem module autoprobe?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I thought that these days module autoprobe was pretty much taken care of and that in the case of filesystems, an attempt to mount a filesystem for which a module had not yet been loaded would result in the kernel forking a modprobe on fs-xxx, which would use the module aliases to match up an appropriate module and load it. So why is it that when I try to mount an ext2 filesystem mount complains that there's no such filesystem until I modprobe ext2?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCgAGBQJSuQDhAAoJEI5FoCIzSKrwzPEIAJwBewwaiEPa1w3OdC+kXYVV egHB1KS4pnPsgdmmBsz9bQLLwrvh+9YJMRUJX0jroEIQErEb7R+KWHab+0Cu6Lfd q84lx/x/2bbyncJxjxx/ayRiKHKeytEYajLEckbs7IWT8oJJN8goNDOIGCCd0Sjv THOkrZJjQz8Q50EXytv6aZ4jazKJRGpAiuQsHCFOnrwMNUMYrxb0MGmr2EqyCNiJ wI0Xpgn16jdvTaDsk0nDOVFs0NKg52oXDj9myGDL2ikowGSurmDb3ftnLmBZsGFL D8Vaq3qRtysbxzT6aJXprAY7utT2h00at61xEpehnSvrcnHIA8WDeq99nWFDgGk= =ALBh
-----END PGP SIGNATURE-----
Quoted 7 lines · Phillip Susi
I thought that these days module autoprobe was pretty much taken care of and that in the case of filesystems, an attempt to mount a filesystem for which a module had not yet been loaded would result in the kernel forking a modprobe on fs-xxx, which would use the module aliases to match up an appropriate module and load it. So why is it that when I try to mount an ext2 filesystem mount complains that there's no such filesystem until I modprobe ext2?
If you're expecting
mount /dev/sda1 /mnt
to insert all the available filesystem modules and discover that /dev/sda1 is ext2, this is a case of mismatched user expectations (because we won't).
If
mount -t ext2 /dev/sda1 /mnt
isn't autoprobing, that's either a bug or a distribution problem.
James
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Quoted 7 lines · James Bottomley
If you're expecting
mount
/dev/sda1/mntto insert all the available filesystem modules and discover that
/dev/sda1is ext2, this is a case of mismatched user expectations (because we won't).
mount uses libblkid to identify the correct filesystem and tells the kernel to use it.
Quoted 5 lines
If
mount -t ext2
/dev/sda1/mntisn't autoprobing, that's either a bug or a distribution problem.
So that *should* autoprobe? Any pointers to some docs on how that is supposed to work or where to start looking to figure out why it isn't?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCgAGBQJSuf0aAAoJEI5FoCIzSKrw7aUH/ir25B8lch2syfvPxY/k7x06 5j05rowEBpY6yhRtM7h2UmtzP6yJH8eVy2lBRnhHoURWFmNiCid9FAPOawn+bl1B QLno+VPZpIaxuQ6mv0dBtq7EVzzPnpl3MR5Im+P6UabEmqfMlp6HFGBXIHYhJFSj to2XXwxt4xrZo8GZxelVEGSjaYUx1FrRmPxoaH8KxBwY0kfDqaYDibC8flaWuFnT W9WZdcy9BgURLt6eBRDN9Vk2EW05S64NiGNyGkGKZwHoQoWjLhTkGghmW9le+aui bZxJl0cnjeNTfriNB5iVjMZOvJHO7Ui0AWwBGPUGI/XMx2DyDUEMi1wo+9TNQOQ= =ibM2
-----END PGP SIGNATURE-----
Quoted 11 lines · Phillip Susi
Quoted 7 lines · James Bottomley
If you're expecting
mount
/dev/sda1/mntto insert all the available filesystem modules and discover that
/dev/sda1is ext2, this is a case of mismatched user expectations (because we won't).mount uses libblkid to identify the correct filesystem and tells the kernel to use it.
No idea about that, but making it work is a distro specific problem, I'd look at the source code. However, if you pass a NULL fstype to sys_mount, it will try every fs it knows about until one says yes.
Quoted 8 lines
Quoted 5 lines
If
mount -t ext2
/dev/sda1/mntisn't autoprobing, that's either a bug or a distribution problem.
So that *should* autoprobe? Any pointers to some docs on how that is supposed to work or where to start looking to figure out why it isn't?
Yes, mount -t <fstype> should try to load a module with alias fs-<fstype> each filesystem module has a MODULE_ALIAS_FS which constructs this.
James