archive mirror
 help / color / mirror / Atom feed
From: "" <>
To: <>
Cc: <>
Subject: R: default subvolume abilities/restrictions
Date: Wed, 19 May 2010 13:56:32 +0200 (CEST)	[thread overview]
Message-ID: <29213501.290601274270192630.JavaMail.defaultUser@defaultHost> (raw)

Hi Anthony,

I think that for you may be interested to read this thread

and to read a my blog about this argument


>----Messaggio originale----
>Data: 19/05/2010 8.50
>A: <>
>Ogg: default subvolume abilities/restrictions
>i'm working on an initrd hook
>[] to support
>non-volatile system rollbacks (promoting a temporary rollback snapshot
>to the new active/default).  when the system is installed to the
>default/"." subvolume (as many users probably initially do), it is
>more difficult/messier to manage system state; there are empty folders
>in each "child" snapshot where a subvolume used to exist (this seems
>like BUG to me, dir should not exist?) in the default subvolume. these
>grow/vary with time.  to work around this and for cleaner
>implementation, i'll intend to permanently boot a named subvolume
>[__active] (though its contents may be swapped out).  ultimately, i
>have to tell the user to manually remove the old junk (/usr, /etc,
>/var, etc...) from the default subvolume (since its really in the
>/__active subvolume)
>moving along to a question... can the default subvolume be
>what would have been useful, would be the ability to generate an
>empty, parent subvolume to _contain_ the current one, and rename it to
>__active.  btrfs gives rise to a "subroot" structure; the structure
>beneath the root.
>is something like this possible or can be added?
>an alternative idea i had was "promoting" a subvolume to be the new
>root, and anything "above" the new root is lost/forgotten.  then i
>could create the subroot structure in a subvol, snapshot the default
>subvol to where i want it, and promote the subvol to be the new root.
>like a permanent pivot_root/chroot.
>great stuff,
>C Anthony
>To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>the body of a message to
>More majordomo info at

             reply	other threads:[~2010-05-19 11:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 11:56 kreijack [this message]
2010-05-19 14:01 ` default subvolume abilities/restrictions C Anthony Risinger
2010-05-19 17:58   ` Goffredo Baroncelli
2010-06-12  5:24   ` C Anthony Risinger
2010-06-12 23:06     ` C Anthony Risinger
2010-06-13  0:22       ` David Brown
2010-06-13  1:06         ` C Anthony Risinger
2010-06-13 17:47           ` C Anthony Risinger
2010-06-18 21:01             ` C Anthony Risinger
2010-06-29 13:20               ` Hubert Kario
2010-06-29 15:23                 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29213501.290601274270192630.JavaMail.defaultUser@defaultHost \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).