All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim <jim@webstarts.com>
To: C Anthony Risinger <anthony@xtfx.me>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: snapshot issues
Date: Fri, 14 Oct 2011 14:33:48 -0400	[thread overview]
Message-ID: <4E98808C.7020502@webstarts.com> (raw)
In-Reply-To: <4E987CAB.2000007@xtfx.me>

Thank you for that info Anthony, I just wanted to know the expected 
behavior.  In that same vein, when I use btrfs sub list it lists all 
subvols regardless of whether or not it is given a path argument.  Is 
this current behavior as well.  Thanks again.
Jim

On 10/14/2011 02:17 PM, C Anthony Risinger wrote:
> On 10/14/2011 12:13 PM, Jim wrote:
>> 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
>>
>> -- 
>> 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
>
> yaarg -- resend w/list included -- changed clients recently (tbird) 
> and cant figure out how to default to replay-all ...
>
> i believe this is expected behavior as of now -- there are a couple 
> threads mentioning `recursive snapshotting`, check those out.  AFAIK a 
> snapshot will not traverse beyond it's own boundaries.
>

      reply	other threads:[~2011-10-14 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14 17:13 snapshot issues Jim
2011-10-14 18:17 ` C Anthony Risinger
2011-10-14 18:33   ` Jim [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=4E98808C.7020502@webstarts.com \
    --to=jim@webstarts.com \
    --cc=anthony@xtfx.me \
    --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.