From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Desater Recovery <urgent>
Date: Thu Apr 25 04:00:02 2002 [thread overview]
Message-ID: <20020425105940.A16030@sistina.com> (raw)
In-Reply-To: <002c01c1ea92$c33db310$3b00a8c0@aplabwp0368359>; from weblists@gmx.net on Tue, Apr 23, 2002 at 08:47:40AM +0200
All,
I supported Ralf on the phone and we analyzed, that the ext2 filesystem was
already *very* messy before e2fsadm could be run.
Brief history was:
- fs run as ext3 (heavily) used for weeks
- try to shrink unmounted fs with e2fsadm (using resize2fs) made e2fsadm
end early because manual fsck was required; this was the point in time
where a readonly mount and a backup was needed (but didn't happen) in
order to save as much data as possible
- manual "fsck -fy" was run exposing piles of messages :-( which
convinces me, that the fs data was messy already afterwards
- e2fsadm was run "successfully" ending up with smaller fs and larger
LV size which is most likely caused by a resize2fs exit code != 0.
As already mentioned in other mails of this thread: no backups :-(
"Remind people of taking backup, remind people of taking backup, remind..."
Regards,
Heinz -- The LVM Guy --
On Tue, Apr 23, 2002 at 08:47:40AM +0200, Bas wrote:
> > On Apr 22, 2002 18:22 +0100, Joe Thornber wrote:
> > > On Mon, Apr 22, 2002 at 07:14:05PM +0200, Ralf Zerres wrote:
> > > > no, i guess not.
> > > > I was using e2fsadm which is serializing the steps. As far as I know
> ...
> > >
> > > Yes e2fsadm should have resized the filesystem itself, so that's not
> > > the problem.
> >
> > Unless e2fsadm doesn't work properly with "- 4,5G"...
> >
> > Out of curiosity, which resizer did e2fsadm use? resize2fs or
> > ext2resize? By default it would have picked resize2fs if it is
> > installed.
> >
> > I don't suppose you recall (or better, have saved) any of the output
> > >from e2fsadm, resize2fs, e2fsck, anything?
> >
> > Cheers, Andreas
> > --
> > Andreas Dilger
>
> Is it possible to extend the lv to the original size and run fsck on it ?
> Make a tarball of the available data in advance !
>
> Good luck,
> Bas.
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-04-25 4:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 10:14 [linux-lvm] Desater Recovery <urgent> Ralf Zerres
2002-04-22 12:05 ` Joe Thornber
2002-04-22 12:13 ` Ralf Zerres
2002-04-22 12:22 ` Joe Thornber
2002-04-22 12:32 ` Andreas Dilger
2002-04-23 1:43 ` Bas
2002-04-25 4:00 ` Heinz J . Mauelshagen [this message]
2002-04-22 12:25 ` Andreas Dilger
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=20020425105940.A16030@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.