xfs
[Top] [All Lists]

Re: xfs_repair unable to repair a corrupt filesystem

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: xfs_repair unable to repair a corrupt filesystem
From: "Russell G. Howe" <rhowe@xxxxxxxxxx>
Date: Mon, 24 Feb 2003 14:08:06 +0000
Cc: "Russell G. Howe" <rhowe@xxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <20030224071237.GF798@frodo>
References: <20030223081255.GA14077@lithium.sta.man.ac.uk> <20030223215931.GA798@frodo> <20030224033309.GA20260@lithium.sta.man.ac.uk> <20030224034815.GC798@frodo> <20030224043829.GA20677@lithium.sta.man.ac.uk> <20030224052759.GD798@frodo> <20030224055532.GA21046@lithium.sta.man.ac.uk> <20030224071237.GF798@frodo>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4i
On Mon, Feb 24, 2003 at 06:12:37PM +1100, Nathan Scott wrote:
> be able to blow these files away by writing zeroes into the
> nextents and size fields (in a similar way to the way you did
> nblocks overwrite earlier with xfs_db).

Hm, OK. I'll try that then. I also have another problem with /home (log
corruption causing mount failure), but the emails I sent to the list
about that seem to have been caught in limbo for no good reason (I just
got a Mailer-Daemon message saying there was an SMTP timeout talking to
oss's mail server, yet it's odd that these messages don't get stuck).

Eric Sandeen had a brief look at it on IRC before he went to bed, but
not long enough to draw a conclusion. At least I have a rough idea of
what data I can collect now, and I'll be posting a message about it
shortly :)

-- 
Russell Howe     | Why be just another cog in the machine,
rhowe@xxxxxxxxxx | when you can be the spanner in the works?


<Prev in Thread] Current Thread [Next in Thread>