public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
To: kreijack@gmail.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-progs: New utility to swap subvolumes
Date: Wed, 06 Jan 2010 09:09:45 +0900	[thread overview]
Message-ID: <4B43D4C9.2000705@jp.fujitsu.com> (raw)
In-Reply-To: <201001041820.03591.kreijack@libero.it>

Thanks for your greetings.

I read your article, and could follow your idea, which looks
very practical rule to me.
But we may need some application which support to create or maintain
these rules because the relation mount point and subvolumes and
snapshots gets complicated as number of subvolumes increases.

Regards,
taruisi

(2010/01/05 2:20), Goffredo Baroncelli wrote:
> On Monday 04 January 2010, TARUISI Hiroaki wrote:
>> Buon anno, Goffredo.
> あけまして おめでとう Taruisi,
> 
> (I hope that happy new year is correctly written)
>>
>> Taking snapshot in btrfs is very easy, but handling snapshots is
>> very confusing. So, we must make a rule of snapshotting such as
>> your proposal, which seems to me very good and useful.
>> If rules like this are forced regardless of operator's preference,
>> this utility may become a deadwood.
> 
> I detailed this idea in this article
> 
> http://kreijack.blogspot.com/2010/01/linux-btrfs-example-of-layout.html
> 
> BR
> G.Baroncelli
> 


-- 
taruisi


  reply	other threads:[~2010-01-06  0:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24  2:17 btrfs-progs: New utility to swap subvolumes TARUISI Hiroaki
2009-12-24  2:18 ` [PATCH] " TARUISI Hiroaki
2009-12-27 20:23 ` Goffredo Baroncelli
2009-12-28  1:38   ` TARUISI Hiroaki
2009-12-28 19:08     ` Goffredo Baroncelli
2010-01-04  0:49     ` TARUISI Hiroaki
2010-01-04 17:20       ` Goffredo Baroncelli
2010-01-06  0:09         ` TARUISI Hiroaki [this message]
2010-01-06  7:56           ` Goffredo Baroncelli
     [not found]             ` <4B4450C0.3050607@cs.bgu.ac.il>
2010-01-06 20:21               ` Goffredo Baroncelli

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=4B43D4C9.2000705@jp.fujitsu.com \
    --to=taruishi.hiroak@jp.fujitsu.com \
    --cc=kreijack@gmail.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