[Top] [All Lists]

Re: File system corruption

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: File system corruption
From: Wayne Walker <wwalker@xxxxxxxxxxxxxx>
Date: Wed, 24 Oct 2012 16:19:28 -0500
Cc: <xfs@xxxxxxxxxxx>
In-reply-to: <20121013001425.GN2739@dastard>
References: <5077077A.3040608@xxxxxxxxxxxxxx> <20121011210741.GC2739@dastard> <50789076.7040402@xxxxxxxxxxxxxx> <20121013001425.GN2739@dastard>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121009 Thunderbird/16.0
On 10/12/2012 07:14 PM, Dave Chinner wrote:
And SB/AGF 3 and 4 are ok, too. So, the filesystem headers just beyond the 2TB offset are zero. That tends to point to a block device problem, as an offset of 2TB is where a 32 bit sector count will overflow (i.e. 2^32). Next step is to run blktrace/blkparse on the cp workload that generates the error to see if anything actually writes to the 2TB offset region, and if so, where it comes from. Probably best to compress the resultant blkparse output file - it might be quite large but the text will compress well. Cheers, Dave.


Thank you for your help.

10 MB .gz file at http://rx-7.bybent.com/blktrace.sde1.out.gz

What I can see seems to have most of the writes are around 2^31.


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