From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Sumit Narayan <talk2sumit@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
ext3-users@redhat.com
Subject: Re: deleting partition does not effect superblock?
Date: Mon, 10 Apr 2006 18:00:52 +0200 [thread overview]
Message-ID: <20060410160052.GO13324@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0604101725130.922@yvahk01.tjqt.qr>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
On Mon, 2006-04-10 17:28:18 +0200, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
> >deleted) or otherwise modified. So it's perfectly okay to delete such
> >a container (eg. remove start and end from the partition table) and
> >recreate it at some time later (by adding those values back to the
> >partition table.) As long as the new container starts at the same
> >location, a filesystem driver will be able to find the old
> >information. If you start a block later, it won't find it's
> >superblocks.
> >
> If using a filesystem with replicated superblocks (ext*, xfs), then ...?
> [Includes expecting weird breakage.]
I'll possibly test if this works in another life...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-04-10 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 6:37 Sumit Narayan
2006-04-06 6:58 ` Jan-Benedict Glaw
2006-04-10 15:28 ` Jan Engelhardt
2006-04-10 16:00 ` Jan-Benedict Glaw [this message]
2006-04-06 7:31 ` Damian Menscher
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=20060410160052.GO13324@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=ext3-users@redhat.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=talk2sumit@gmail.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
Powered by JetHome