linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] online resize
Date: Sun, 26 Mar 2006 14:35:11 +0200	[thread overview]
Message-ID: <20060326123511.GS31387@lug-owl.de> (raw)
In-Reply-To: <200603260537.00242.krakrjak@volumehost.net>

[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]

On Sun, 2006-03-26 05:36:59 -0600, Zac Slade <krakrjak@volumehost.net> wrote:
> On Sunday 26 March 2006 04:26, Luca Berra wrote:
> > if you have any horror story, please share it, it will surely help other
> > users out there.
> Distribution: Gentoo
> Data: /home
> Target: Resize from 1GiB to 800MiB (plenty of free space)
> Filesystem: ext3
> Method: ext2resize with kernel patches and latest e2fsprogs
> 
> Unmount /home in single user mode.  Resize using ext resizing utilities and 
> spend the next 12 hours recovering inodes with fsck only to find a few 
> hundred megs of data in /home/lost+found (with nonsensical names) and 
> swearing off ext3 for mission critical data.

Nice story, but as a bug report, this is mostly useless:

  * After umount, did you run an e2fsck -f?

  * Do you have a script(1) log of the whole session? (You'd probably
    have this started as a last resort log then you started the
    fsck'ing after the resize.)

  * What exactly is "ext resizing utilities"? Did you save a copy of
    it (incl. sources to find out about additionally applied patches?)

  * These nonsensical names you refer to are the file's inode numbers,
    in decimal. For mission-critical systems, it's wise to regularly
    get inode listings with filenames. Did you compare those inode
    numbers with your backups?

  * Did you prepare an image-backup of your 1GB container beforehand?
    Helps for easy recovery as well as error reproduction (esp.
    because 1GB isn't all that hard to store on one CD when there's
    plenty of free space, which can be made to compress very well.)

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

  reply	other threads:[~2006-03-26 12:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 14:27 [linux-lvm] online resize Michael Schulz
2006-03-15 14:35 ` [linux-lvm] XFS Decreasing Size James Hammett
2006-03-15 14:53   ` Kevin P. Fleming
2006-03-16  9:02 ` [linux-lvm] online resize Gunther Clasen
2006-03-16 13:08   ` Roger Lucas
2006-03-16 18:12     ` Nate Carlson
2006-03-16 18:28       ` David Brown
2006-03-26  7:21     ` Urs Thuermann
2006-03-26  8:46     ` Zac Slade
2006-03-26  9:29       ` Luca Berra
2006-03-26 10:07         ` Zac Slade
2006-03-26 10:26           ` Luca Berra
2006-03-26 11:36             ` Zac Slade
2006-03-26 12:35               ` Jan-Benedict Glaw [this message]
2006-03-27  5:50                 ` Zac Slade
2006-03-27  7:28                   ` Jan-Benedict Glaw

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=20060326123511.GS31387@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).