From: Axel Burri <axel@tty0.ch>
To: kreijack@inwind.it
Cc: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/4] btrfs-progs: change -t option for subvolume list to print a simple space-separated table (making it machine-readable)
Date: Mon, 5 Oct 2015 18:58:39 +0200 [thread overview]
Message-ID: <5612AC3F.30401@tty0.ch> (raw)
In-Reply-To: <56129A7C.8060701@inwind.it>
On 2015-10-05 17:42, Goffredo Baroncelli wrote:
> Hi Axel,
>
> On 2015-10-05 17:04, Axel Burri wrote:
> [...]
>> I still don't think it is wise to bloat things further just for printing
>> nice tables. My impression is that "btrfs subvolume list" is
>> human-readable enough without the '-t' flag, while the output with '-t'
>> flag is much more machine-readable-friendly, and thus should have the
>> highest possible performance. e.g.:
>
> I disagree, the "-t" mode is for the human; the non '-t' mode would be for machine (if you take the space as separator and the first word as key, with the exception of the path which starts from the "path " word and ends to the end of line); unfortunately "top level" is an exception. Anyway btrfs is not very machine-friendly (sic).
That's what my patches are all about in the first place, to make it more
machine-friendly :)
> Compare the two output below:
>
> $ sudo btrfs sub list -a /
> ID 257 gen 44309 top level 5 path <FS_TREE>/debian
> ID 289 gen 17415 top level 257 path debian/var/lib/machines
> ID 298 gen 35434 top level 5 path <FS_TREE>/debian-i32
> ID 299 gen 43961 top level 5 path <FS_TREE>/boot
> ID 300 gen 39452 top level 5 path <FS_TREE>/debian-jessie
"grep-friendly"
>
> $ sudo btrfs sub list -at /
> ID gen top level path
> -- --- --------- ----
> 257 44310 5 <FS_TREE>/debian
> 289 17415 257 debian/var/lib/machines
> 298 35434 5 <FS_TREE>/debian-i32
> 299 43961 5 <FS_TREE>/boot
> 300 39452 5 <FS_TREE>/debian-jessie
>
>
> I think that is easy to declare the latter more "human" friendly.
Well yes, but in some ways the latter is also more machine-friendly, as
there is less data to pipe and a whitespace-separated list is much
easier to parse (of course the same applies to your table implementation
below).
Problems here are:
- "top level" (whitespace, addressed in [PATCH 4/4])
- timestamp (-s) "YYYY-MM-DD HH:MM:SS" (whitspace and no timezone,
addressed in [PATCH 3/4])
- path can contain whitespace (not _that_ important as it's always
printed last).
>
> BTW with the use of the table_* function the output become:
>
> $ sudo ./btrfs sub list -at /
> ID gen top level path
> === ===== ========= =======================
> 257 44311 5 <FS_TREE>/debian
> 289 17415 257 debian/var/lib/machines
> 298 35434 5 <FS_TREE>/debian-i32
> 299 43961 5 <FS_TREE>/boot
> 300 39452 5 <FS_TREE>/debian-jessie
>
> $ sudo ./btrfs sub list -aptcguqR /
> ID gen cgen parent top level parent_uuid received_uuid uuid path
> === ===== ===== ====== ========= =========== ============= ==================================== =======================
> 257 44313 7 5 5 - - 840c86cf-e78b-d54a-ab38-66662858812d <FS_TREE>/debian
> 289 17415 17415 257 257 - - 8b857250-3a3e-754d-810e-57342bbb2f56 debian/var/lib/machines
> 298 35434 35399 5 5 - - 1f38049b-b153-d741-b903-d2de6fd7b3fd <FS_TREE>/debian-i32
> 299 43961 35512 5 5 - - f9d52b6b-a6d1-8c45-a6cd-ddb68cf58062 <FS_TREE>/boot
> 300 39452 37744 5 5 - - 026e44bd-66d4-e341-9a14-0124acf79793 <FS_TREE>/debian-jessie
>
> I right aligned each field with the exception of the path (which is left aligned).
> I already prepared the patch which convert "btrfs sub list -t" to use the table_* function. If you want I can send it to you to extend/replace your patch #4.
Looks promising, although I'd still not recommend it because of the
increased memory/cpu requirements.
next prev parent reply other threads:[~2015-10-05 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 16:41 [PATCH 0/4] btrfs-progs: improve output of btrfs subvolume list command axel
2015-10-02 16:41 ` [PATCH 1/4] btrfs-progs: add -A option for subvolume list (print all available information) axel
2015-10-02 16:41 ` [PATCH 2/4] btrfs-progs: add "flags" column for subvolume list (shows "readonly" flag with -A) axel
2015-10-02 16:41 ` [PATCH 3/4] btrfs-progs: add option "--time-format=short|iso|unix|locale" to subvolume list axel
2015-10-02 16:41 ` [PATCH 4/4] btrfs-progs: change -t option for subvolume list to print a simple space-separated table (making it machine-readable) axel
2015-10-03 9:56 ` Goffredo Baroncelli
2015-10-03 10:06 ` Goffredo Baroncelli
2015-10-03 10:17 ` Axel Burri
[not found] ` <560FA944.3050606@digint.ch>
2015-10-03 17:41 ` Goffredo Baroncelli
2015-10-04 3:37 ` Duncan
2015-10-04 14:34 ` Goffredo Baroncelli
2015-10-05 15:08 ` Axel Burri
[not found] ` <56129171.4040200@digint.ch>
2015-10-05 15:42 ` Goffredo Baroncelli
2015-10-05 16:58 ` Axel Burri [this message]
[not found] ` <5612B30A.9030308@tty0.ch>
2015-10-05 20:09 ` btrfs machine readable output [was Re: btrfs patches] 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=5612AC3F.30401@tty0.ch \
--to=axel@tty0.ch \
--cc=1i5t5.duncan@cox.net \
--cc=kreijack@inwind.it \
--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;
as well as URLs for NNTP newsgroup(s).