All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Alex <alex@bpmit.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: REQ: btrfs list <subvols only> option
Date: Thu, 09 Jan 2014 20:20:05 +0800	[thread overview]
Message-ID: <52CE93F5.5050109@cn.fujitsu.com> (raw)
In-Reply-To: <loom.20140109T045506-475@post.gmane.org>

On 01/09/2014 12:06 PM, Alex wrote:
> Chris Murphy <lists <at> colorremedies.com> writes:
>
>> Specify the mount point for the Btrfs file system and it will list all
> subvols on that file system.
>> Chris Murphy--
> Thank you Chris.
>
> When I do that on my version of the 3.12 userland:
> # btrfs  sub list / -o
There is a bug for 'btrfs sub list -o path', i will send a patch for this

Thanks,
Wang
> returns nothing (with no error), which I wasn't quite expecting because
> there *are* other snapshots and subvols below '/'
>
> AND
>
> # btrfs  sub list / -s
> correctly lists the snapshots only.
>
> I don't understand, what or if, I'm doing something wrong.
> Thank you in advance.
>
>
>
> --
> 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
>


      parent reply	other threads:[~2014-01-09 12:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09  1:31 REQ: btrfs list <subvols only> option Alex
2014-01-09  1:42 ` Chris Murphy
2014-01-09  4:06   ` Alex
2014-01-09  6:27     ` Chris Murphy
2014-01-09  6:44       ` Chris Murphy
2014-01-09  6:46         ` Chris Murphy
2014-01-09  9:25           ` Alex
2014-01-09 12:20     ` Wang Shilong [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=52CE93F5.5050109@cn.fujitsu.com \
    --to=wangsl.fnst@cn.fujitsu.com \
    --cc=alex@bpmit.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 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.