Feizhou wrote:
Is there any difference between running mkfs.xfs under a 2.4 kernel and
running that under a 2.6 kernel?
Any benefits doing it under 2.6?
Let me add some context. I am going to conduct some benchmarks between
xfs and ext3 under different configurations and I wondered if running
mkfs under different kernels would affect the results.
rom owner-linux-xfs@xxxxxxxxxxx Wed Mar 10 07:14:46 2004
Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Mar 2004 07:15:12
-0800 (PST)
Received: from shksmtp01.so-net.com.hk (pop.so-net.com.hk [203.99.142.21])
by oss.sgi.com (8.12.10/8.12.9) with SMTP id i2AFEiKO020340
for <linux-xfs@xxxxxxxxxxx>; Wed, 10 Mar 2004 07:14:45 -0800
Received: (qmail 15513 invoked from network); 10 Mar 2004 15:14:37 -0000
Received: from so165248.bbo165.so-net.com.hk (HELO linuxmail.org)
([203.176.165.248])
(envelope-sender <feizhou@xxxxxxxxxxxxx>)
by shksmtp01.so-net.com.hk (qmail-ldap-1.03) with SMTP
for <linux-xfs@xxxxxxxxxxx>; 10 Mar 2004 15:14:37 -0000
Message-ID: <404F30DD.60507@xxxxxxxxxxxxx>
Date: Wed, 10 Mar 2004 23:14:37 +0800
From: Feizhou <feizhou@xxxxxxxxxxxxx>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040208)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: XFS Mailing List <linux-xfs@xxxxxxxxxxx>
Subject: [Fwd: ran into rare bug: "unable to verify superblock, continuing..."]
Content-Type: multipart/mixed;
boundary="------------080601060505010502060704"
X-archive-position: 2398
X-ecartis-version: Ecartis v1.0.0
Sender: linux-xfs-bounce@xxxxxxxxxxx
Errors-to: linux-xfs-bounce@xxxxxxxxxxx
X-original-sender: feizhou@xxxxxxxxxxxxx
Precedence: bulk
X-list: linux-xfs
This is a multi-part message in MIME format.
--------------080601060505010502060704
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Forwarded to list on behalf of Errikos Pitsos
--------------080601060505010502060704
Content-Type: message/rfc822;
name="[Fwd: Warning: could not send message for past 4 hours]"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="[Fwd: Warning: could not send message for past 4 hours]"
Return-Path: <ep@xxxxxxxxxx>
Delivered-To: feizhou:linuxmail.org@xxxxxxxxxxxxx
Received: (qmail 14181 invoked by uid 0); 10 Mar 2004 15:07:01 -0000
X-OB-Received: from unknown (205.158.62.147)
by mta45-1.us4.outblaze.com; 10 Mar 2004 15:07:01 -0000
Received: from mx.leogic.com (mx.leogic.com [62.245.182.8])
by spf5-2.us4.outblaze.com (Postfix) with ESMTP id 66AD219A486
for <feizhou@xxxxxxxxxxxxx>; Wed, 10 Mar 2004 15:06:56 +0000 (GMT)
Received: from leogic.com ([192.168.41.28])
(authenticated bits=0)
by mx.leogic.com (8.12.11/8.12.10) with ESMTP id i2AF8ZTg021289
(version=TLSv1/SSLv3 cipher=IDEA-CBC-SHA bits=128 verify=NO)
for <feizhou@xxxxxxxxxxxxx>; Wed, 10 Mar 2004 16:08:36 +0100
Message-ID: <404F2EFF.1020307@xxxxxxxxxx>
Date: Wed, 10 Mar 2004 16:06:39 +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: "feizhou@xxxxxxxxxxxxx {unsecure}" <feizhou@xxxxxxxxxxxxx>
Subject: [Fwd: Warning: could not send message for past 4 hours]
X-Enigmail-Version: 0.83.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/mixed;
boundary="------------080509090001010002010203"
This is a multi-part message in MIME format.
--------------080509090001010002010203
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sorry don't know why, but I somehow can't write to the list, have tried
three times now and get funny bounces. Can you forward this email please?
thx
e
-------- Original Message --------
Subject: Warning: could not send message for past 4 hours
Date: Wed, 10 Mar 2004 13:40:09 +0100
From: Mail Delivery Subsystem <MAILER-DAEMON>
To: ep@xxxxxxxxxx
**********************************************
** THIS IS A WARNING MESSAGE ONLY **
** YOU DO NOT NEED TO RESEND YOUR MESSAGE **
**********************************************
The original message was received at Wed, 10 Mar 2004 09:29:31 +0100
from pD950FEA7.dip.t-dialin.net [217.80.254.167]
----- Transcript of session follows -----
451 4.4.1 reply: read error from oss.sgi.com.
<linux-xfs@xxxxxxxxxxx>... Deferred: Connection timed out with oss.sgi.com.
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
--------------080509090001010002010203
Content-Type: message/delivery-status;
name="file:///tmp/nsmail-2.tmp"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="file:///tmp/nsmail-2.tmp"
Reporting-MTA: dns; mx.leogic.com
Arrival-Date: Wed, 10 Mar 2004 09:29:31 +0100
Final-Recipient: RFC822; linux-xfs@xxxxxxxxxxx
Action: delayed
Status: 4.4.2
Remote-MTA: DNS; oss.sgi.com
Diagnostic-Code: SMTP; 451 4.4.1 reply: read error from oss.sgi.com.
Last-Attempt-Date: Wed, 10 Mar 2004 13:40:09 +0100
Will-Retry-Until: Mon, 15 Mar 2004 09:29:31 +0100
--------------080509090001010002010203
Content-Type: message/rfc822;
name="(null).eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="(null).eml"
Return-Path: <ep@xxxxxxxxxx>
Received: from leogic.com (pD950FEA7.dip.t-dialin.net [217.80.254.167])
(authenticated bits=0)
by mx.leogic.com (8.12.11/8.12.10) with ESMTP id i2A8TPl4024540
(version=TLSv1/SSLv3 cipher=IDEA-CBC-SHA bits=128 verify=NO)
for <linux-xfs@xxxxxxxxxxx>; Wed, 10 Mar 2004 09:29:31 +0100
Message-ID: <404ED170.9000601@xxxxxxxxxx>
Date: Wed, 10 Mar 2004 09:27: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: 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
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
--------------080509090001010002010203--
--------------080601060505010502060704--
|