Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Aaron Straus <aaron@merfinllc.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] start work on delete snapshot code
Date: Mon, 9 Feb 2009 17:42:37 -0800	[thread overview]
Message-ID: <20090210014237.GA31158@merfinllc.com> (raw)
In-Reply-To: <1234228148.17365.34.camel@think.oraclecorp.com>

On Feb 09 08:09 PM, Chris Mason wrote:
> Sorry to say that I won't have time to read through this in the morning,
> but this is a pretty hefty task for a first patch.  Thanks for taking it
> on and posting this work!

No worries... I just wanted to learn more about btrfs... so it seemed
like a good project, especially if nobody else is working on it.

I don't think my patch actually works correctly, but I'm hoping someone
who understands both the VFS and btrfs can fix it up or at least use it
as a starting point.

--

Quick question about the root_refs for you or anyone else on the list.

Let's say we have:

  base/s1

where base is a subvolume and s1 is a snapshot.  So base has a root_ref
to s1 and s1 has a back_ref to base in the tree root.

Now let's say we make a snapshot of base so we have:

  base/s1
  base.snap/s1

So we have s1, the same tree root referenced in two separate snapshots.

Now should s1 should now have two back_refs, one to base and one to
base.snap?  Also base.snap show have a root_ref to s1?

That doesn't seem to happen with the current snapshotting code, unless
I'm missing something...  I'm happy to try to add a patch if that is
indeed what should happen...


				Regards,
				=a=



-- 
===================
Aaron Straus
aaron@merfinllc.com

  reply	other threads:[~2009-02-10  1:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  0:07 [PATCH] start work on delete snapshot code Aaron Straus
2009-02-10  1:09 ` Chris Mason
2009-02-10  1:42   ` Aaron Straus [this message]
2009-02-10 19:44 ` Michele Petrazzo
2009-02-10 19:57   ` Aaron Straus
2009-02-10 20:27     ` Aaron Straus

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=20090210014237.GA31158@merfinllc.com \
    --to=aaron@merfinllc.com \
    --cc=chris.mason@oracle.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