linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Christopher Thorjussen <joffer@onlinebackupcompany.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs subvolume list - with three subvolumes, the second is missing/not showing
Date: Thu, 31 Jan 2013 22:00:40 +0000	[thread overview]
Message-ID: <20130131220040.GP16285@carfax.org.uk> (raw)
In-Reply-To: <CAFKW2=ETvfXTyth9jHoc=6yZQDLj+5c8kRTZd4+79zVbs4LU-w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2369 bytes --]

On Thu, Jan 31, 2013 at 04:39:52PM +0100, Christopher Thorjussen wrote:
> I've created a large btrfs volume out of two large raid-60 devices. On
> there I've created three subvolumes. When I do a list of those the 2nd
> isn't displayed. If I however add a fouth subvol they all gets listed.

   This is (probably) a known bug in the userspace tools. It should be
fixed in David Sterba's integration branch:

  git://repo.or.cz/btrfs-progs-unstable/devel.git integration-20130130          
   Hugo.

> This is on a HP DL360 running RHEL6.3 with a P411 SAS Raid controller
> connected to a HP MD600 (70 x 2TB NL-SAS).
> I've installed kernel-ml v3.7.4 from elrepo and also installed
> btrfs-progs-0.19-12.el6.x86_64
> 
> root@data01:/opt/data# btrfs fi sh
> failed to read /dev/sr0
> Label: none  uuid: 786684d1-95fa-4809-8fca-e17e37a79999
>         Total devices 2 FS bytes used 816.00KB
>         devid    1 size 54.58TB used 2.03GB path /dev/sdb
>         devid    2 size 54.58TB used 2.01GB path /dev/sdc
> 
> Btrfs Btrfs v0.19
> 
> root@data01:/opt/data# ls -l
> total 0
> drwxr-xr-x 1 root root 0 Jan 31 15:55 buffer
> drwxr-xr-x 1 root root 0 Jan 31 15:55 consolidated
> drwxr-xr-x 1 root root 0 Jan 31 15:55 staging
> 
> root@data01:/opt/data# btrfs subvolume list .
> ID 265 top level 5 path consolidated
> ID 267 top level 5 path buffer
> 
> root@data01:/opt/data# btrfs subvolume create 4thsubvol
> Create subvolume './4thsubvol'
> 
> root@data01:/opt/data# btrfs subvolume list .
> ID 265 top level 5 path consolidated
> ID 266 top level 5 path staging
> ID 267 top level 5 path buffer
> ID 272 top level 5 path 4thsubvol
> 
> root@data01:/opt/data# rpm -qa | grep btrfs
> btrfs-progs-0.19-12.el6.x86_64
> 
> It surely is a bug, but has it been reported and/or fixed? I wasn't
> able to find out by googling just now.
> 
> 
> 
> Med vennlig hilsen / kind regards
> 
> Christopher Thorjussen
> System Administrator, VCP4/VCP5
> The Online Backup Company AS
> http://www.onlinebackupcompany.no
> 
> "Backup isn't the real concern. Restoring normal business is."

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
  --- What do you give the man who has everything? -- Penicillin is ---  
                             a good start...                             

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2013-01-31 22:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 15:39 btrfs subvolume list - with three subvolumes, the second is missing/not showing Christopher Thorjussen
2013-01-31 22:00 ` Hugo Mills [this message]
2013-01-31 22:59   ` Christopher Thorjussen

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=20130131220040.GP16285@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=joffer@onlinebackupcompany.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).