xfs
[Top] [All Lists]

Re: XFS problems

To: Wolfgang Henselmann-Weiss <Wolfgang_Henselmann@xxxxxxxxxxxxxxx>
Subject: Re: XFS problems
From: Nathan Scott <nathans@xxxxxxx>
Date: Thu, 19 Jul 2001 21:33:48 +1000
Cc: Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <3B568903.7376AC2B@xxxxxxxxxxxxxxx>; from Wolfgang_Henselmann@xxxxxxxxxxxxxxx on Thu, Jul 19, 2001 at 09:15:15AM +0200
References: <200107182244.IAA21596@xxxxxxxxxxxxxxxxxxxxxxx> <3B568903.7376AC2B@xxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Thu, Jul 19, 2001 at 09:15:15AM +0200, Wolfgang Henselmann-Weiss wrote:
> 
> syslog output is ...
> |Jul 19 09:08:48 wolfi kernel:  XFS: SB sanity check 2 failed
> |Jul 19 09:08:48 wolfi kernel:  XFS: SB validate failed
> 

Hmmm ... that looks grim - the error comes from here, in the
XFS kernel code (xfs_mount.c):

        if (sbp->sb_dblocks == 0 ||
            sbp->sb_dblocks >
             (xfs_drfsbno_t)sbp->sb_agcount * sbp->sb_agblocks ||
            sbp->sb_dblocks < (xfs_drfsbno_t)(sbp->sb_agcount - 1) * 
                              sbp->sb_agblocks + XFS_MIN_AG_BLOCKS) {
                cmn_err(CE_WARN, "XFS: SB sanity check 2 failed");
                return XFS_ERROR(EFSCORRUPTED);
        }

So, it seems mkfs might be coming up with bad data.. haven't ever
seen that before.  Could you run xfs_db on the device, and print
the superblock & send us that?  Something like:

        # xfs_db -c sb -c p /dev/foo

and we should be able to narrow it down to one of those 3 condition.

thanks.

-- 
Nathan


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