On Mon, Jun 20, 2011 at 10:20:02AM -0400, John Lindgren wrote:
> On 06/20/2011 10:04 AM, Karel Zak wrote:
> > On Mon, Jun 20, 2011 at 09:05:36AM -0400, John Lindgren wrote:
> >> I did try that; however, blkid checks *all* filesystems, even after it
> >> finds a match, just in case two probes turn up positive. Even passing
> >> "-n nozfs" doesn't actually prevent it from checking for ZFS.
> > The name of the FS in libblkid is zfs_member :-)
> >
> > blkid -p -o udev -n nozfs_member
> >
> > Yeah, crazy name, see our TODO file:
> >
> > - add something like "blkid --list-known" to list all supported
> > filesystems/raids
Implemented,
blkid -k
lists all known filesystems/RAIDs now.
> Perhaps a "-q/--quick" option could be added to blkid to allow an early
> exit once the first positive match is found?
That's dangerous, and many times rejected by udev upstream. The
mainstream distributions rely on the automatic FS detection on many
places. We are not able to control mkfs and partitioning tools, so we
are not sure that the device has been properly wiped and there is
really only one valid superblock. We already have bad experience with
FAT, linux swap, luks, ... some people already lost data.
> Then more difficult checks
> such as ZFS could be moved to the end of the list, as you suggest, with
> a performance benefit.
What about to set to blkid (during boot) greater I/O priority than to
read-ahead?
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
