xfs
[Top] [All Lists]

Re: XFS (vdb): Corruption detected. Unmount and run xfs_repair

To: Fengguang Wu <fengguang.wu@xxxxxxxxx>
Subject: Re: XFS (vdb): Corruption detected. Unmount and run xfs_repair
From: Ben Myers <bpm@xxxxxxx>
Date: Mon, 17 Jun 2013 13:37:50 -0500
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, Jan Kara <jack@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, Dave Chinner <david@xxxxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20130615030928.GC29338@dastard>
References: <20130615023620.GA23586@localhost> <20130615030928.GC29338@dastard>
User-agent: Mutt/1.5.20 (2009-06-14)
Hey Fengguang,

On Sat, Jun 15, 2013 at 01:09:28PM +1000, Dave Chinner wrote:
> [cc xfs@xxxxxxxxxxx, where XFS bug reports should go]
> 
> On Sat, Jun 15, 2013 at 10:36:20AM +0800, Fengguang Wu wrote:
> > [   74.570969] XFS (vdb): bad magic number
> > [   74.573837] ffff8800170ed000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> > 00 00  ................
                                     X  F  S  B

That's the magic it's looking for...

> > [   74.579266] ffff8800170ed010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> > 00 00  ................
> > [   74.584581] ffff8800170ed020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> > 00 00  ................
> > [   74.590036] ffff8800170ed030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> > 00 00  ................
> > [   74.595386] XFS (vdb): Internal error xfs_sb_read_verify at line 730 of 
> > file /c/kernel-tests/src/stable/fs/xfs/xfs_mount.c.  Caller 
> > 0xffffffff81309514
> .....
> > [   74.692206] XFS (vdb): Corruption detected. Unmount and run xfs_repair
> > [   74.696000] XFS (vdb): SB validate failed with error 22.
> 
> It's obviously not an XFS filesystem you are asking the kernel to
> mount, so it's perfectly valid to throw a corruption error at you.
> What it has actually thrown is EWRONGFS, but because you've asked
> the kernel specifically to mount the device as an XFS filesystem,
> the kernel is explicitly telling you that it's a corrupt
> filesystem... :)

We did have an issue in this area in 3.7 which fixed in commit aeb4f20a that
made 3.8.  We were returning EFSCORRUPTED instead of EWRONGFS.  Maybe that's
not your kernel.

Regards,
        Ben

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