From: David Sterba <dsterba@suse.cz>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/3] btrfs-progs: random fixes of btrfs-filesystem documentation
Date: Wed, 20 Aug 2014 15:22:42 +0200 [thread overview]
Message-ID: <20140820132242.GE1553@suse.cz> (raw)
In-Reply-To: <53F36E58.1090108@redhat.com>
On Tue, Aug 19, 2014 at 10:33:44AM -0500, Eric Sandeen wrote:
> Seems like using /proc/partitions would make more sense in that case
> than a recursive scan of every file under /dev, wouldn't it?
> Any details on those reports?
It does make sense.
> I'm just wondering when you might possibly have success looking deep
> into the /dev tree if you didn't have success in /proc/partitions.
I haven't figured out any advantage of /dev.
> It just seems a bit bizarre to have so many ways to get the same info.
I think keeping blkid as default and /proc/filesystems as fallback
should cover the usecases. This meanas that the option -d stays, and the
scanning method can be changed to BTRFS_SCAN_PROC (fi show and dev scan).
prev parent reply other threads:[~2014-08-20 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 9:11 [PATCH 1/3] btrfs-progs: random fixes of btrfs-filesystem documentation Satoru Takeuchi
2014-08-11 17:05 ` Eric Sandeen
2014-08-11 17:14 ` Eric Sandeen
2014-08-11 23:55 ` Satoru Takeuchi
2014-08-11 23:51 ` Satoru Takeuchi
2014-08-12 0:07 ` Eric Sandeen
2014-08-12 7:25 ` [PATCH 1/3 v2] " Satoru Takeuchi
2014-08-12 7:45 ` [PATCH 1/3 v3] " Satoru Takeuchi
2014-08-12 8:06 ` [PATCH 1/3 v4] " Satoru Takeuchi
2014-08-19 15:07 ` David Sterba
2014-08-19 15:10 ` [PATCH 1/3] " David Sterba
2014-08-19 15:33 ` Eric Sandeen
2014-08-20 13:22 ` David Sterba [this message]
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=20140820132242.GE1553@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=takeuchi_satoru@jp.fujitsu.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).