All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim <jim@webstarts.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: snapshot issues
Date: Fri, 14 Oct 2011 13:13:31 -0400	[thread overview]
Message-ID: <4E986DBB.4080100@webstarts.com> (raw)

Good afternoon btrfs,
I have been having issues with snapshots not reading the whole file tree 
below them.  I have installed new btrfs-progs from

git://git.darksatanic.net/repo/btrfs-progs-unstable.git

made and installed them.  My tree is:  /Btrfs |
                                               |__ nfs1 |
                                                        |__ data |
                                                                 |__ sites |
                                                                           |__ 00xx |
                                                                                    |__ email@address

If I use btrfsctl -s (btrfs sub snapshot isn't working) snappath-name /btrfs/nfs1  I get a mountable snapshot of nfs1
but data is all that I can see below it.  If I btrfsctl -s snappath-name /btrfs/nfs1/data/sites/0000 I can mount /0000 and
get a full list of email@address accounts but none of the files below them.  I should have stated earlier, everything down
to and including /email@address are subvolumes.  Below /email@address directories and files were rsync'd into the subvol from
an nfs mount.  Finally if I snapshot /email@address I have access to all directories and files below them.  Because of this I
believe that the issue is with snapshots of subvolumes.  I thought I just couldn't see subvols above the snapshot level and was able to see subvols below.  Am I confused or is this a real problem.  I am using kernel 3.1.0-rc4 and will be happy to trace anything you need if you can tell me how to get what you need.  Thanks for your help.
Jim


             reply	other threads:[~2011-10-14 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14 17:13 Jim [this message]
2011-10-14 18:17 ` snapshot issues C Anthony Risinger
2011-10-14 18:33   ` 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=4E986DBB.4080100@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.