[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ext3 + raid, is resize2fs neccessary?

On Fri, 2003-10-17 at 17:20, Andreas Dilger wrote:
> On Oct 17, 2003  16:26 -0400, Eric Wood wrote:
> > Does merely running e2fsck recover the journal? You lost me here.  How/why
> > do I "recover" a journal.  I didn't think I was going to loose it.
> Sorry, maybe "replay" the journal is better, done by running e2fsck <dev>

> I don't think either resize2fs or ext2resize will allow you to resize
> with a journal that needs replaying, so you are safe.

Okay sounds good.  Thanks for your assistance.  The HOWTO says in Step
11: "This will generate the same error about inconsistent sizes and
possibly corrupted superblock.Say N to 'Abort?'."  So you can see why I
started this thread!

So I will resize2fs the /dev/hdaX devices first to back off from the
last block, *then* do the mkraid, wait for the mirror to complete,
*then* run resize2fs on the /dev/mdX devices to max the filesystems back
to full capacity.  This sounds like this will get rid of the error
message Mark Price is talking about.

I'll try this out Monday.  Thanks again!
-eric wood 

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]