From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Ali AlipourR <alipoor90@gmail.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: "btrfs subvolume list" feature request
Date: Tue, 16 Dec 2014 14:36:58 +0900 [thread overview]
Message-ID: <548FC4FA.6030009@jp.fujitsu.com> (raw)
In-Reply-To: <CABvhJLhSTfm711Hdp6_=7xEv44ejYmbSRPgqKT6a5jNHvxEWTA@mail.gmail.com>
Hi Ali,
(2014/12/16 11:01), Ali AlipourR wrote:
> Hi
>
> I think it will be to add option to "btrfs subvolume list" command to
> also show the property of sub volumes (ro, compression,...)? do this
> is possible?
Of course it's possible by writing some code :-D
Is "btrfs property get <subvol>" (and some one liner) insufficient for
your purpose? If you want to just list properties of each subvolumes
instead of listing properties with existing fields, it can be
accomplished as follows.
===============================================================================
# btrfs sub list /btrfstest
# btrfs sub cre /btrfstest/sub1
Create subvolume '/btrfstest/sub1'
# btrfs sub cre /btrfstest/sub2
Create subvolume '/btrfstest/sub2'
# btrfs sub list /btrfstest/
ID 382 gen 39625 top level 5 path sub1
ID 383 gen 39626 top level 5 path sub2
# for i in $(btrfs sub list /btrfstest | cut -d ' ' -f 9) ; do echo -n $i': ' ; btrfs prop get /btrfstest/$i ; done
sub1 ro=false
sub2 ro=false
===============================================================================
Thanks,
Satoru
>
> Thanks,
> Ali
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-12-16 5:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 2:01 "btrfs subvolume list" feature request Ali AlipourR
2014-12-16 5:36 ` Satoru Takeuchi [this message]
2014-12-16 7:52 ` Chris Murphy
2014-12-16 9:25 ` Satoru Takeuchi
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=548FC4FA.6030009@jp.fujitsu.com \
--to=takeuchi_satoru@jp.fujitsu.com \
--cc=alipoor90@gmail.com \
--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).