[Top] [All Lists]

Re: XFS filesystem corruption on the arm(el) architecture

To: Martin Michlmayr <tbm@xxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>, Tobias Frost <tobi@xxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, debian-arm@xxxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
Subject: Re: XFS filesystem corruption on the arm(el) architecture
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Sat, 18 Oct 2008 22:06:45 -0500
In-reply-to: <20081019014830.GI31761@disturbed>
References: <1222893502.5020.40.camel@moria> <20081002004556.GB30001@disturbed> <48E4213E.9090508@xxxxxxxxxxx> <20081016212500.GA27228@xxxxxxxxxxxxxxxxxxxxxx> <48F7BC9F.4080909@xxxxxxxxxxx> <20081017070109.GA30726@xxxxxxxxxxxxxxxxxxxxxx> <48F89E0F.6030307@xxxxxxxxxxx> <20081018085752.GS25834@xxxxxxxxxxxxxxxxxxxxxx> <20081019014830.GI31761@disturbed>
User-agent: Thunderbird (Macintosh/20080914)
Dave Chinner wrote:
> On Sat, Oct 18, 2008 at 10:57:56AM +0200, Martin Michlmayr wrote:
>> * Eric Sandeen <sandeen@xxxxxxxxxxx> [2008-10-17 09:15]:
>>> If you unmount & remount, does the ls work then?
>> I cannot even mount it:
>> debian:~# mkfs.xfs -f /dev/sda5
>> meta-data=/dev/sda5              isize=256    agcount=4, agsize=94380 blks
>>          =                       sectsz=512   attr=2
>> data     =                       bsize=4096   blocks=377519, imaxpct=25
>>          =                       sunit=0      swidth=0 blks
>> naming   =version 2              bsize=4096
>> log      =internal log           bsize=4096   blocks=2560, version=2
>>          =                       sectsz=512   sunit=0 blks, lazy-count=0
>> realtime =none                   extsz=4096   blocks=0, rtextents=0
>> debian:~# mount /dev/sda5 /mnt
>> [42949596.920000] XFS mounting filesystem sda5
>> debian:~# cp /usr/bin/* /mnt/
>> debian:~# umount /mnt
>> debian:~# mount -t xfs /dev/sda5 /mnt
>> [42949612.290000] XFS mounting filesystem sda5
>> [42949612.460000] Starting XFS recovery on filesystem: sda5 (logdev: 
>> internal)
>> [42949612.480000] XFS: xlog_recover_process_data: bad flag
>> [42949612.500000] XFS: log mount/recovery failed: error 5
>> [42949612.500000] XFS: log mount failed
>> mount: /dev/sda5: can't read superblock
>> debian:~#
> That's the log replay indicating that there's a bad transaction
> header in the log. Very strange - it shoul dbe a clean log. What
> does xfs_logprint -t /dev/sda5 tell you about the transactions
> in the log?

This is probably the vmap cache aliasing problem that we paid a bit of
attention to a few months ago, no?


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