From: John Lindgren <john.lindgren@tds.net>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org, Andreas Dilger <adilger@sun.com>
Subject: Re: blkid: excessive random reads probing for ZFS on NTFS filesystem
Date: Mon, 20 Jun 2011 10:20:02 -0400 [thread overview]
Message-ID: <4DFF5712.4070606@tds.net> (raw)
In-Reply-To: <20110620140457.GI17967@nb.net.home>
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
>
> Karel
My bad. "-n nozfs_member" does work, so I will add it to my udev rules
locally.
Perhaps a "-q/--quick" option could be added to blkid to allow an early
exit once the first positive match is found? Then more difficult checks
such as ZFS could be moved to the end of the list, as you suggest, with
a performance benefit.
-- John
next prev parent reply other threads:[~2011-06-20 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 19:02 blkid: excessive random reads probing for ZFS on NTFS filesystem John Lindgren
2011-06-20 11:16 ` Karel Zak
2011-06-20 11:59 ` John Lindgren
2011-06-20 12:46 ` Karel Zak
2011-06-20 13:05 ` John Lindgren
2011-06-20 14:04 ` Karel Zak
2011-06-20 14:20 ` John Lindgren [this message]
2011-06-20 14:57 ` Karel Zak
2011-06-20 12:02 ` John Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DFF5712.4070606@tds.net \
--to=john.lindgren@tds.net \
--cc=adilger@sun.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.