ran into rare bug: "unable to verify superblock, continuing..."

To:	"linux-xfs@xxxxxxxxxxx {unsecure}" <linux-xfs@xxxxxxxxxxx>
Subject:	ran into rare bug: "unable to verify superblock, continuing..."
From:	"Errikos Pitsos {secure}" <ep@xxxxxxxxxx>
Date:	Wed, 10 Mar 2004 14:58:48 +0100
Organization:	leogic
Sender:	linux-xfs-bounce@xxxxxxxxxxx
User-agent:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040126

Hi!

Seems like I ran into a known problem wrt to "unable to verify
superblock, continuing..."
http://oss.sgi.com/projects/xfs/faq.html#xfsmountfail

I can't mount the xfs fs.
I can't repair the xfs fs.
Yes, this is my root partition, this is a new system I was setting up.
I don't know what caused the trouble, but it seems that somehow the
system was not properly unmounted.
Using xfs_repai without "L" doesn't change anything.
So if I can help finding that bug tell me.
I am using Gentoo and had a 2.4.24-xfs-r3 on there, syslog says:
Mar 10 07:56:43 leonzwei SGI XFS snapshot-2.4.23-2003-12-01_00:33_UTC
with no debug enabled

For some reason it seems that the XFS was not cleanly unmounted, not
sure though. The system was cleanly shutdown, but I didn't find a:
 Mar 10 03:47:25 leonzwei Ending clean XFS mount for filesystem: ide1(22,3)

in there which I had before.


syslog shows these here when I try to mount the partition.
Mar 10 08:03:37 leonzwei XFS: bad magic number
Mar 10 08:03:37 leonzwei XFS: SB validate failed



here some console output:

leonzwei root # xfs_repair -nLv /dev/hdc3
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...

...........................................................................................................



.....................found candidate secondary superblock...
error reading superblock 54 -- seek to offset 57982058496 failed
unable to verify superblock, continuing...

...........................................................................................................



.............................................................found
candidate secondary superblock...
error reading superblock 54 -- seek to offset 57982058496 failed
unable to verify superblock, continuing...

...........................................................................................................



.............................................................found
candidate secondary superblock...
error reading superblock 54 -- seek to offset 57982058496 failed
unable to verify superblock, continuing...


goes on for ever.

here something else that I saw that you requested from somebody who had
the same bug:

leonzwei root # xfs_db /dev/hdc3
xfs_db: unexpected XFS SB magic number 0x1917d8b3
xfs_db: sb 0
xfs_db: p
magicnum = 0x1917d8b3
blocksize = 689553475
dblocks = 12180848741608851668
rblocks = 8457844901802481315
rextents = 17089333805017595916
uuid = c005688d-587d-e4b5-7729-c2cd4e81e350
logstart = 12437974581420056107
rootino = 2035592538136216092
rbmino = 2311019282328682982
rsumino = 940638864488651459
rextsize = 4062341194
agblocks = 1795335310
agcount = 3583083788
rbmblocks = 745776455
logblocks = 2344638215
versionnum = 0xcd77
sectsize = 57419
inodesize = 22122
inopblock = 22912
fname = "q\275\347\017o;\202\376<l\243I"
blocklog = 253
sectlog = 155
inodelog = 111
inopblog = 173
agblklog = 91
rextslog = 155
inprogress = 45
imax_pct = 183
icount = 3536497887666359542
ifree = 15647017454152257949
fdblocks = 15766340045555572059
frextents = 7127039695291382717
uquotino = 7880036713507589276
gquotino = 3559299706880429710
qflags = 0x5d07
flags = 0xe9
shared_vn = 152
inoalignmt = 237542219
unit = 2706140452
width = 574901660
dirblklog = 54
logsectlog = 60
logsectsize = 49029
logsunit = 1105637059
xfs_db:


anything else I can provide bug hunters with?

erik


rom owner-linux-xfs@xxxxxxxxxxx Wed Mar 10 07:23:40 2004
Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Mar 2004 07:23:48 
-0800 (PST)
Received: from mx.leogic.com (mx.leogic.com [62.245.182.8])
        by oss.sgi.com (8.12.10/8.12.9) with SMTP id i2AFNdKO021392
        for <linux-xfs@xxxxxxxxxxx>; Wed, 10 Mar 2004 07:23:39 -0800
Received: from leogic.com ([192.168.41.28])
        (authenticated bits=0)
        by mx.leogic.com (8.12.11/8.12.10) with ESMTP id i2AFPORH010125
        (version=TLSv1/SSLv3 cipher=IDEA-CBC-SHA bits=128 verify=NO)
        for <linux-xfs@xxxxxxxxxxx>; Wed, 10 Mar 2004 16:25:24 +0100
Message-ID: <404F32F0.9090009@xxxxxxxxxx>
Date: Wed, 10 Mar 2004 16:23:28 +0100
From: "Errikos Pitsos {secure}" <ep@xxxxxxxxxx>
Organization: leogic
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040126
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "linux-xfs@xxxxxxxxxxx {unsecure}" <linux-xfs@xxxxxxxxxxx>
Subject: ran into rare bug: "unable to verify superblock, continuing..."
X-Enigmail-Version: 0.83.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/mixed;
boundary="------------050308000704040508080808"
X-archive-position: 2400
X-ecartis-version: Ecartis v1.0.0
Sender: linux-xfs-bounce@xxxxxxxxxxx
Errors-to: linux-xfs-bounce@xxxxxxxxxxx
X-original-sender: ep@xxxxxxxxxx
Precedence: bulk
X-list: linux-xfs

This is a multi-part message in MIME format.
--------------050308000704040508080808
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi!

Seems like I ran into a known problem wrt to "unable to verify
superblock, continuing..."
http://oss.sgi.com/projects/xfs/faq.html#xfsmountfail

I can't mount the xfs fs.
I can't repair the xfs fs.
Yes, this is my root partition, this is a new system I was setting up.
I don't know what caused the trouble, but it seems that somehow the
system was not properly unmounted.
Using xfs_repai without "L" doesn't change anything.
So if I can help finding that bug tell me.
I am using Gentoo and had a 2.4.24-xfs-r3 on there, syslog says:
Mar 10 07:56:43 leonzwei SGI XFS snapshot-2.4.23-2003-12-01_00:33_UTC
with no debug enabled

For some reason it seems that the XFS was not cleanly unmounted, not
sure though. The system was cleanly shutdown, but I didn't find a:
 Mar 10 03:47:25 leonzwei Ending clean XFS mount for filesystem: ide1(22,3)

in there which I had before.


syslog shows these here when I try to mount the partition.
Mar 10 08:03:37 leonzwei XFS: bad magic number
Mar 10 08:03:37 leonzwei XFS: SB validate failed

I put the console output in a file as my email was alwyas bounced asbulk by the sgi mx.


Anything else I can provide bug hunters with?

erik



--------------050308000704040508080808
Content-Type: text/plain;
name="xfs.log"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="xfs.log"

here some console output:

leonzwei root # xfs_repair -nLv /dev/hdc3
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...

...........................................................................................................



.....................found candidate secondary superblock...
error reading superblock 54 -- seek to offset 57982058496 failed
unable to verify superblock, continuing...

...........................................................................................................



.............................................................found
candidate secondary superblock...
error reading superblock 54 -- seek to offset 57982058496 failed
unable to verify superblock, continuing...

...........................................................................................................



.............................................................found
candidate secondary superblock...
error reading superblock 54 -- seek to offset 57982058496 failed
unable to verify superblock, continuing...


goes on for ever.

here something else that I saw that you requested from somebody who had
the same bug:

leonzwei root # xfs_db /dev/hdc3
xfs_db: unexpected XFS SB magic number 0x1917d8b3
xfs_db: sb 0
xfs_db: p
magicnum = 0x1917d8b3
blocksize = 689553475
dblocks = 12180848741608851668
rblocks = 8457844901802481315
rextents = 17089333805017595916
uuid = c005688d-587d-e4b5-7729-c2cd4e81e350
logstart = 12437974581420056107
rootino = 2035592538136216092
rbmino = 2311019282328682982
rsumino = 940638864488651459
rextsize = 4062341194
agblocks = 1795335310
agcount = 3583083788
rbmblocks = 745776455
logblocks = 2344638215
versionnum = 0xcd77
sectsize = 57419
inodesize = 22122
inopblock = 22912
fname = "q\275\347\017o;\202\376<l\243I"
blocklog = 253
sectlog = 155
inodelog = 111
inopblog = 173
agblklog = 91
rextslog = 155
inprogress = 45
imax_pct = 183
icount = 3536497887666359542
ifree = 15647017454152257949
fdblocks = 15766340045555572059
frextents = 7127039695291382717
uquotino = 7880036713507589276
gquotino = 3559299706880429710
qflags = 0x5d07
flags = 0xe9
shared_vn = 152
inoalignmt = 237542219
unit = 2706140452
width = 574901660
dirblklog = 54
logsectlog = 60
logsectsize = 49029
logsunit = 1105637059
xfs_db:



--------------050308000704040508080808--

<Prev in Thread]	Current Thread	[Next in Thread>
ran into rare bug: "unable to verify superblock, continuing...", Errikos Pitsos {secure} <= ran into rare bug: "unable to verify superblock, continuing...", Errikos Pitsos {secure} Re: ran into rare bug: "unable to verify superblock, continuing...", Eric Sandeen Re: ran into rare bug: "unable to verify superblock, continuing...", Errikos Pitsos {secure} Re: ran into rare bug: "unable to verify superblock, continuing...", Eric Sandeen Re: ran into rare bug: "unable to verify superblock, continuing...", Errikos Pitsos {secure}

Previous by Date:	Re: mkfs under different kernels, Feizhou
Next by Date:	ran into rare bug: "unable to verify superblock, continuing...", Errikos Pitsos {secure}
Previous by Thread:	mkfs under different kernels, Feizhou
Next by Thread:	ran into rare bug: "unable to verify superblock, continuing...", Errikos Pitsos {secure}
Indexes:	[Date] [Thread] [Top] [All Lists]