From: Goffredo Baroncelli <kreijack@inwind.it>
To: dsterba@suse.cz
Cc: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH RFC] btrfs: pick device with lowest devt for show_devname
Date: Wed, 6 Dec 2023 20:52:59 +0100 [thread overview]
Message-ID: <dc5b4031-588e-44ea-9bc6-e429a8195e47@inwind.it> (raw)
In-Reply-To: <20231205174443.GP2751@twin.jikos.cz>
On 05/12/2023 18.44, David Sterba wrote:
> On Wed, Nov 29, 2023 at 09:54:02PM +0100, Goffredo Baroncelli wrote:
[...]
>> I developed a little utility to build for each btrfs filesystem:
>> - all the devices involved
>> - all the mountpoint (if any) where the filesystem is mounted and the subvolume used as root.
>>
>> It was nice because it got all these information only using:
>> - libblkid
>> - parsing /proc/self/mountinfo
>
> I think if there's one consistent approach based on libblkid then all
> the related tools and projects can use that.
>
Just now I send some patches to evaluate. See
[PATCH 0/4] RFC: add the btrfs_info helper
BR
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2023-12-06 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 11:10 [PATCH RFC] btrfs: pick device with lowest devt for show_devname Anand Jain
2023-11-02 20:26 ` David Sterba
2023-11-02 22:55 ` Anand Jain
2023-11-20 14:42 ` David Sterba
2023-11-24 16:19 ` David Sterba
2023-11-25 1:09 ` Anand Jain
2023-11-27 11:48 ` Anand Jain
2023-11-28 8:00 ` Goffredo Baroncelli
2023-11-28 23:28 ` Anand Jain
2023-11-29 13:38 ` Andrei Borzenkov
2023-11-29 20:54 ` Goffredo Baroncelli
2023-12-05 17:44 ` David Sterba
2023-12-06 19:52 ` Goffredo Baroncelli [this message]
2023-12-05 17:43 ` David Sterba
2023-11-29 21:20 ` Goffredo Baroncelli
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=dc5b4031-588e-44ea-9bc6-e429a8195e47@inwind.it \
--to=kreijack@inwind.it \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox