On Sun, 2007-02-18 at 19:40 -0600, Eric Sandeen wrote:
> Andrew Morton wrote:
> > I thought Eric fixed that. Maybe he broke it instead ;)
>
> Eeek... I'll reserve judgment on who broke what until I see that
> corrupted image... ;) is it available? How huge?
2G, but bzip'ed e2image -r is 54M:
Andrew Morton wrote:
On Mon, 19 Feb 2007 10:52:42 +1100 Rusty Russell <[EMAIL PROTECTED]> wrote:
Hi all,
This happened on 2.6.20-rc6-mm3, so I upgraded to 2.6.20-git14, and
same thing happened. Doing a forced fsck on the (corrupted by
double-mounting I think) filesystem fixed it, but
On Mon, 19 Feb 2007 10:52:42 +1100 Rusty Russell <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> This happened on 2.6.20-rc6-mm3, so I upgraded to 2.6.20-git14, and
> same thing happened. Doing a forced fsck on the (corrupted by
> double-mounting I think) filesystem fixed it, but I took a copy be
