All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim <jim@webstarts.com>
To: linux-btrfs@vger.kernel.org
Subject: snapshots changed behavior
Date: Fri, 21 Oct 2011 12:31:34 -0400	[thread overview]
Message-ID: <4EA19E66.2020102@webstarts.com> (raw)

Good afternoon btrfs list,
about a month ago, when testing btrfs, I could create a snapshot with 
btrfs snap create and be able to drill down in the snapshot to find 
subvols and files below the snapshot level.  I currently need to use 
btrfsctl -s to create snapshots and can no longer drill down through 
subvols in them.  An example would be a file tree of /btrfs (subvol)
/data (subvol) /sites (subvol) /0000 (directory) /files-in-dir.  If I 
snapshot /btrfs/data I can open data and see /sites but can see nothing 
below /sites.  However, if I snap /btrfs/data/sites I can drill down 
through all lower directories and files.  In my past tests I was able to 
drill all the way down from the /btrfs/data snap.  Also, in the past, a 
snap was definitely a sparse file and was able to easily be moved, moved 
back, remounted and used.  Currently, the useful file /btrfs/data/sites 
contains 5GB of data and both shows and moves as 5GB of data, not like a 
sparse file.  Am I misusing the filesystem, or improperly using the 
commands?  Or have changes been made to the functionality which I 
missed?  Sorry to take your time on such a simple matter, but I need to 
understand how to best use the filesystem.  Thanks very much for your 
advice.
Jim Maloney

             reply	other threads:[~2011-10-21 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 16:31 Jim [this message]
2011-10-21 17:53 ` snapshots changed behavior Goffredo Baroncelli
2011-10-21 18:29   ` Jim
2011-10-21 18:43     ` Goffredo Baroncelli
2011-10-21 18:50       ` Jim

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=4EA19E66.2020102@webstarts.com \
    --to=jim@webstarts.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.