[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130328115554.GA5737@thunk.org>
Date: Thu, 28 Mar 2013 07:55:54 -0400
From: Theodore Ts'o <tytso@....edu>
To: Eric Sandeen <sandeen@...hat.com>
Cc: John Jolly <john.jolly@...il.com>, linux-ext4@...r.kernel.org
Subject: Re: Failure of resize2fs past 4TB
On Wed, Mar 27, 2013 at 10:57:25PM -0500, Eric Sandeen wrote:
> > I know it is unusual to start so small and expand like this, but I
> > doubt I am the only one to have experienced this. How could I have
> > prepared my small 1GB file system so that it would be able to handle
> > an expansion past 2TB? Any help would be appreciated.
>
> not sure; you haven't done anything wrong, this simply looks like
> a resize bug, of which there have been a few lately I'm afraid.
Note that what might have corrupted your file system may be different
from the reproduction case which you've sent (which I've also
confirmed). There was a number of off-line resize bugs fixed between
1.42.6 and 1.42.7. In general, off-line resize has been a bit more
problematic recently than on-line resize. (Although if you're using
an older kernel, online resize didn't work when starting with a
super-small file system and then grow it to something large.)
Thanks for sending this bug report; we'll get right on it.
Can you say a bit more about the resize2fs failure you had with your
production file system? Was it a similar "start really small and grow
very big" pattern? Or something else?
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists