From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] online resize
Date: Mon, 27 Mar 2006 09:28:26 +0200 [thread overview]
Message-ID: <20060327072826.GY31387@lug-owl.de> (raw)
In-Reply-To: <200603262350.53701.krakrjak@volumehost.net>
[-- Attachment #1: Type: text/plain, Size: 2294 bytes --]
On Sun, 2006-03-26 23:50:53 -0600, Zac Slade <krakrjak@volumehost.net> wrote:
> > * 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.)
> No. The session was not run through script(1).
That's something I learned the hard way, too. Though that was not a
Linux session.
> > * 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?
> I know they are inode numbers, but they don't help you much in that situation.
> You think people keep inode listings with backups? What a perfect world you
> live in. I think it's not superflous information, but it is not a part of
> your average backup. As a matter of fact I've not incountered a system that
> does this. Sure you can do this on your own and it sort of makes sense.
> This just seems like a strange suggestion to me.
inode/filename listings are rarely heared of, but I have them at my
hands for the backups I drive. Learned that the hard way, too...
Again, not on a Linux box.
> > * 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.)
> I did restore the data eventually. I apologize if that was not clear. I was
> frustrated that the tool did not perform as expected and it is something I
> should have followed up on with a bug report. I should go back and do some
> experimenting with the current e2fsprogs and see if they behave better now.
So at least you had no data loss. That's most important.
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 --]
prev parent reply other threads:[~2006-03-27 7:28 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
2006-03-27 5:50 ` Zac Slade
2006-03-27 7:28 ` Jan-Benedict Glaw [this message]
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=20060327072826.GY31387@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).