On Mon, Mar 03, 2008 at 12:46:38PM +1100, Lachlan McIlroy wrote:
>> After mount, the file in question is heavily fragmented (around 1600
>> segments). I'm not sure if this file caused the corruption, but I'm
>> almost certain, as no other traffic should have been at that time.
> The file being written to (that caused the panic) has unwritten extents
> and we were trying to convert the extents from unwritten to real after
> writing to them. These XFS_WANT_CORRUPTED_GOTO bugs often occur with
> extent tree corruption so this is not surprising. Could we get output
> from xfs_bmap -v on this file?
http://www.k1024.org/iusty/plains.bmap
>> I also have a metadump (run before recovery) and a full copy of the
>> filesystem if it's useful.
> Can we get a copy of that metadump? I don't hold high hopes for it
> though - the filesystem can be inconsistent until the log is replayed
> but after the log was replayed the problem was gone. I don't suppose
> you have a copy of the log?
The metadump is here http://www.k1024.org/iusty/plains.metadump.bz2
(~80MB), done with default options. Warning, the server is somewhat slow
:)
The copy of the log, done with xfs_logprint -t, is here
http://www.k1024.org/iusty/plains.logprint
The inode of the file in question is 96424401.
Let me know if I can give more information.
thanks,
iustin
|