public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian von Bidder <avbidder@fortytwo.ch>
To: Piavlo <piavka@cs.bgu.ac.il>
Cc: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: snapshot/subvolume removal
Date: Tue, 12 Jan 2010 10:12:46 +0100	[thread overview]
Message-ID: <201001121012.52665@fortytwo.ch> (raw)
In-Reply-To: <4B4C1FEA.70109@cs.bgu.ac.il>

[-- Attachment #1: Type: Text/Plain, Size: 617 bytes --]

Hi,

On Tuesday 12 January 2010 08.08:26 Piavlo wrote:
> Maintaining snapshot hierarchy by  external application is not reliable
> and error prone
> compared to maintaining it withing the btrfs itself,
> probably by adding the parent treeid field for every  shapshot/subvolume.

What should, in your opinion, happen if the parent snapshot is deleted?  
Orphan? Re-parent to parent of parent?  I guess depending on application, 
there may be more than one "right" solution.

cheers
-- vbi

-- 
When Al sends me patches, I apply them.
I worry what would happen if I didn't.
        -- Linus Torvalds

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 389 bytes --]

  parent reply	other threads:[~2010-01-12  9:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 21:18 snapshot/subvolume removal Piavlo
2010-01-06  0:30 ` TARUISI Hiroaki
2010-01-06  6:54   ` Adrian von Bidder
2010-01-06  8:33   ` Piavlo
2010-01-08  8:28     ` TARUISI Hiroaki
2010-01-09 22:01       ` Piavlo
2010-01-12  0:48         ` TARUISI Hiroaki
2010-01-12  7:08           ` Piavlo
2010-01-12  8:04             ` TARUISI Hiroaki
2010-01-12  9:12             ` Adrian von Bidder [this message]
2010-01-12 11:03               ` Piavlo
2010-01-10 20:18       ` Chris Mason
2010-01-12  1:12         ` TARUISI Hiroaki

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=201001121012.52665@fortytwo.ch \
    --to=avbidder@fortytwo.ch \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=piavka@cs.bgu.ac.il \
    --cc=taruishi.hiroak@jp.fujitsu.com \
    /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