xfs
[Top] [All Lists]

Re: filesize after H/W fault

To: Eric Sandeen <sandeen@xxxxxxx>, ASANO Masahiro <masano@xxxxxxxxxxxxxx>
Subject: Re: filesize after H/W fault
From: Seth Mos <knuffie@xxxxxxxxx>
Date: Mon, 15 Jul 2002 08:39:20 +0200
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.44.0207150022050.6433-100000@xxxxxxxxxxxxxxxxxx .com>
References: <20020715135555H.masano@xxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
At 00:26 15-7-2002 -0500, Eric Sandeen wrote:
Hi Masano -

You say "linux-2.4.7 and xfs cvs based" - does that mean that it is
recent XFS code, ported back to 2.4.7?  Or is the xfs code from many
months ago?

I believe this to be CVS from that time.

There have been MANY changes in the area of syncing & logging since
2.4.7, so if you are running xfs code from the 2.4.7 days, I would
strongly suggest an upgrade.  I don't have any specific suggestions
on what may have gone wrong, but an upgrade would be a good idea.

It's not unthinkable that a process already got wedged which caused disk processes to get stuck. I have had similar behaviour with hardware failures and XFS. Thinks like memory and such which is silent corruption untill it's too late.

He also didn't mention what hardware part was faulty.

Cheers


-Eric

On Mon, 15 Jul 2002, ASANO Masahiro wrote:

> Hi,
>
> I have run old xfs on my server machine. The kernel is linux-2.4.7 and
> xfs cvs based. This system was working fine for several months without
> any xfs related troubles. But a problem happened at last.
>
> After a hardware fault, some files on xfs were truncated to size
> zero. The files were created via nfs v3 several hours before the
> hardware fault, and were not overwritten after created. When the
> filesystem was mounted at reboot, log recovery was done automatically,
> and there was no error.
>
> I thought file data would be sync'd to disk within minutes after it is
> written. What happened?
> Any ideas or patches?
>
> --
> Masano
>

--
Seth
It might just be your lucky day, if you only knew.


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