public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-progs: New utility to swap subvolumes
Date: Wed, 6 Jan 2010 08:56:17 +0100	[thread overview]
Message-ID: <201001060856.17940.kreijack@libero.it> (raw)
In-Reply-To: <4B43D4C9.2000705@jp.fujitsu.com>

On Wednesday 06 January 2010, TARUISI Hiroaki wrote:
> 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.

I wrote a little script which handle the snapshot creation/deleting/listing 
and grub config file update.

This script supposing the layout which I discussed

- under /var/btrfs is mounter the real root btrfs filesystem
- under the real root file-system there are the snapshots and the root of the 
system (rootfs)
- in /var/btrfs/snaplist.txt there is the list of snaphsot
- in /boot/grub/menu.lst there is the grub configuration

In you are interested, I can send you.

BR 
Goffredo

> 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
> > 
> 
> 
> 


-- 
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E  C054 BF04 F161 3DC5 0512

  reply	other threads:[~2010-01-06  7:56 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
2010-01-06  7:56           ` Goffredo Baroncelli [this message]
     [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=201001060856.17940.kreijack@libero.it \
    --to=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