Re: Filesystem module autoprobe?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2013-12-24 at 16:31 -0500, Phillip Susi wrote:
> On 12/24/2013 03:22 PM, James Bottomley wrote:
> > 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).
> 
> 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.

> > If
> > 
> > mount -t ext2 /dev/sda1 /mnt
> > 
> > isn'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


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




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux