Unable to mount / (ext error 22) [plug]

Dean Holland speedster at westnet.com.au
Wed Jun 18 07:04:05 WST 2003


> Are you using a relatively recent version of e2fsprogs? (e2fsck -V
> will tell you). From memory, you'll want something at least version
> 1.28? (it's what a lot of things seem to recommend).

1.32 :o)

> In other words, infinite loops should never happen :)

Hehe, they shouldn't, but one other user has reported it with version 1.32 -
exactly the same symptoms I am getting.

http://sourceforge.net/tracker/index.php?func=detail&aid=729708&group_id=2406&atid=102406


Regards

Dean

----- Original Message ----- 
From: "Bernard Blackham" <bernard at blackham.com.au>
To: <plug at plug.linux.org.au>
Sent: Wednesday, June 18, 2003 12:53 AM
Subject: Re: Unable to mount / (ext error 22) [plug]


> On Wed, Jun 18, 2003 at 12:31:54AM +0800, Dean Holland wrote:
> > back into rescue mode, i noticed that when fsck was spamming the
console, it
> > was the same group of dup/bad inodes, and wasn't deleting/cloning them.
> >
> > tune2fs (re)creating the journal allowed me to mount the partition as
ext3,
> > but I am still getting kernel panics on boot, and fsck still loops on
the
> > same files when scanning for dup blocks.
>
> Are you using a relatively recent version of e2fsprogs? (e2fsck -V
> will tell you). From memory, you'll want something at least version
> 1.28? (it's what a lot of things seem to recommend).
>
> > I can actually get to the partition in rescue mode now, so I'll probably
> > just recover what I can and format :)
>
> The e2fsck man page says "If you manage to find a filesystem which
> causes e2fsck to crash, or which e2fsck is unable to repair, please
> report it to the author."
>
> In other words, infinite loops should never happen :)
>
> Regards,
>
> Bernard.
>
> -- 
>  Bernard Blackham
>  bernard at blackham dot com dot au
>



More information about the plug mailing list