public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
To: piavka@cs.bgu.ac.il
Cc: linux-btrfs@vger.kernel.org
Subject: Re: snapshot/subvolume removal
Date: Tue, 12 Jan 2010 17:04:02 +0900	[thread overview]
Message-ID: <4B4C2CF2.5070402@jp.fujitsu.com> (raw)
In-Reply-To: <4B4C1FEA.70109@cs.bgu.ac.il>

Yes, it's not enough reliable for all users, and it may be
possible, but disk format may be the last point to change.

If we want to change it, we need to discuss its necessity
carefully and implement it [almost] without incompatibility.

Regards,
taruisi

(2010/01/12 16:08), Piavlo wrote:
> TARUISI Hiroaki wrote:
>> Thanks for your comment.
>>
>> I think your request is reasonable but because there's
>> no information about a hierachy of snapshots in filesystem,
>> we cannot know it for now.
>>
>> In future, these information may be supplied by application
>> programs which manage all snapshots or backups.
>>   
> 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.
> 
> Thanks
> Alex
> 


  reply	other threads:[~2010-01-12  8:04 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 [this message]
2010-01-12  9:12             ` Adrian von Bidder
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=4B4C2CF2.5070402@jp.fujitsu.com \
    --to=taruishi.hiroak@jp.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=piavka@cs.bgu.ac.il \
    /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