[Top] [All Lists]

Re: in memory corruption?

To: Arkadiusz Miskiewicz <arekm@xxxxxxxx>
Subject: Re: in memory corruption?
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 31 Oct 2008 10:00:49 -0500
Cc: xfs@xxxxxxxxxxx
In-reply-to: <200810310858.07632.arekm@xxxxxxxx>
References: <200810310858.07632.arekm@xxxxxxxx>
User-agent: Thunderbird (X11/20080723)
Arkadiusz Miskiewicz wrote:
> Hi,
> I'm trying to find out  a reason (and a solution) for in memory corruption 
> with xfs involved.
> Sometimes files are corrupted in such way as pasted below. This is in memory
> corruption since the file is correct after reboot. File size is unchanged as 
> original,
> mtime not modified (compared to what I have in backup) according to ls -l.
> There is no oops, just contents of some files (it happens like 1 file per 
> week, well I notice
> one file per week) are partially trashed.
> This is 230GB partition on lvm2, mounted with 
> rw,nosuid,nodev,noatime,nodiratime,usrquota,grpquota
> options. Hardware is intel rack server (don't remember which one exactly) 1U 
> with 2 x quad xeon,
> adaptec 3405, 4 SAS disks in raid5.
> Any ideas what that could be?
> /**
> * A class for reading Microsoft Excel Spreadsheets.
> *
> * Originally 
> d4040\134040\134040\134040//"#,##0.00",^M\134012\134040\134040\134040\134040\134040\134040\134040\1340400x5\134040=>\134040"%1.0f",\134040\134040\134040\134040\134040/*"$#,##0;

Ow, my eyes ;)


# hexdump -C $FILENAME

to see if it's obvious where the corruption boundaries are, or any
patterns that might be more readable than
"\134012\134040\134040\134040\134040\"  :)


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