All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Chris Murphy <lists@colorremedies.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: RFE: btrfs subvolume list -t, include marker for snapshots, and whether they are ro
Date: Fri, 15 Apr 2016 07:18:59 -0400	[thread overview]
Message-ID: <5710CE23.3060107@gmail.com> (raw)
In-Reply-To: <CAJCQCtSUj0fcsH7AUREnm7KzdDZiL2pW9MpSkKiQBcV9-J9nXQ@mail.gmail.com>

On 2016-04-14 21:55, Chris Murphy wrote:
> Hi,
>
> I'm realizing instead of doing 'btrfs subvolume -t' and then 'btrfs
> subvolume -tr' and comparing, it would be better if -t just had a
> column for whether a subvolume is ro. And maybe it's useful to know if
> a subvolume is a snapshot or not (?). I'm not super picky about the
> last one. But being able to see if it's ro or not is a nice to have.
If you're just wanting info about one subvolume, just use 'subvol show'. 
  As far as 'subvol list', that was mentioned in discussion on github of 
future changes for btrfs-progs (although I don't think that's gone 
anywhere).

Checking if something is a snapshot is easy though, do 'btrfs subvolume 
show -qt', if the Parent UUID column is a -, it's a regular subvolume, 
if not, it was created as a snapshot.

      parent reply	other threads:[~2016-04-15 11:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15  1:55 RFE: btrfs subvolume list -t, include marker for snapshots, and whether they are ro Chris Murphy
2016-04-15  6:51 ` Satoru Takeuchi
2016-04-15  6:57   ` Chris Murphy
2016-04-15 11:18 ` Austin S. Hemmelgarn [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=5710CE23.3060107@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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 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.