lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 28 Mar 2013 07:55:54 -0400
From:	Theodore Ts'o <>
To:	Eric Sandeen <>
Cc:	John Jolly <>,
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
More majordomo info at

Powered by blists - more mailing lists