xfs
[Top] [All Lists]

Re: xfs error

To: "Eric Sandeen" <sandeen@xxxxxxxxxxx>
Subject: Re: xfs error
From: "Gomel Kiev" <gomelkiev@xxxxxxxxx>
Date: Wed, 7 Jan 2009 19:00:19 -0700
Cc: "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=L8IZort+FcjsMIv6sV5eiL2EqeF9mrzncB4UbpQRgPQ=; b=xPivI1mghPSSzZw7Y8QxBGRX6v6f0umXktVaR5eVmEKeVUsWolUznV6t1RVrMLbxyk 4lUJTIGGeMCKmOuUt13fu7yZj0+Fa+0gj8OvsUbu2/5qJTeeAIhmeMai+auXkRLz8pBJ qgKdpRW7LTfFXxywAvx1xy7NsmUPNNugRAnd0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=DbLpgNj7V0DGsPgUnWgggC7KjQXWdb5utbHZzAM+inod//8Zq8A1sc7YBela8aQ0wu mzH0HtsOhRQ9IHeRN4lvwPwXHUmqC2vBFaBRPkJOsTb5aZMGurqn1YQhDAGpJ60FTQkA YnqgwMkexNRyjKFAi9oQwCDr8EYqKLHkIj5is=
In-reply-to: <DD209695-62B3-4E36-8BE8-586CB50FEE76@xxxxxxxxxxx>
References: <d96784ac0901062202t42927621r196894b6b2cc9449@xxxxxxxxxxxxxx> <20090108011936.GF9448@disturbed> <d96784ac0901071739u2d38a2fbh28fd8d7d98fe0486@xxxxxxxxxxxxxx> <DD209695-62B3-4E36-8BE8-586CB50FEE76@xxxxxxxxxxx>
I don't have xfs_metadump on ARM ( v 2.5.6)
I have xfs_metadump on X86 (2.10.2), but getting errors:
xfs_metadump: unexpected XFS SB magic number 0x33c08ed0
xfs_metadump: size check failed
xfs_metadump: read failed: Invalid argument
xfs_metadump: data size check failed
xfs_metadump: failed to alloc -225176656 bytes: Cannot allocate memory
thanks



On Wed, Jan 7, 2009 at 6:55 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
> An xfs_metadump of the filesystem might let someone debug the repair hang...
>
> -Eric
>
> On Jan 7, 2009, at 7:39 PM, "Gomel Kiev" <gomelkiev@xxxxxxxxx> wrote:
>
>> I tried xfs_repair on ARM box,results are same as on X86 platform,
>> running for 20+ hours saying :
>> root@BUFFALO:~# xfs_repair /dev/sdd
>> Phase 1 - find and verify superblock...
>> couldn't verify primary superblock - not enough secondary superblocks
>> with matching geometry !!!
>>
>> attempting to find secondary superblock...
>> ...
>>
>> thanks
>> PS. is it possible at least to get list of files, just names?
>>
>>
>> On Wed, Jan 7, 2009 at 6:19 PM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
>>>
>>> On Tue, Jan 06, 2009 at 11:02:20PM -0700, Gomel Kiev wrote:
>>>>
>>>> Hello, here is whole story, maybe somebody can help.
>>>> hardware: buffalo linkstation + "MS2UT+B"  in mirror mode, raid1.
>>>> 2x1tb seagate drives
>>>> buffalo :
>>>> root@BUFFALO:~# uname -a
>>>> Linux BUFFALO 2.6.16.16-arm1 #9 Wed Mar 7 14:17:36 JST 2007 armv5tejl
>>>> unknown
>>>>
>>>> xfs version:
>>>> root@BUFFALO:~# xfs_info -V /mnt/usbdisk2
>>>> xfs_info version 2.5.6
>>>
>>> That's on ARM...
>>>
>>>> on dec 12, log show errors:
>>>> Dec 12 04:26:28 BUFFALO kernel: 0x0: 60 f2 de 8d 58 cf 08 48 46 76 56
>>>> 8f 1e 3e 78 29
>>>> Dec 12 04:26:28 BUFFALO kernel: Filesystem "sdc1": XFS internal error
>>>> xfs_da_do_buf(2) at line 2221 of file fs/xfs/xfs_da_btree.c.  Caller
>>>> 0xc011ff60
>>>
>>> .... and you have a corrupted directory.
>>>
>>>> after that , could not mount drive(any). I removed drives from
>>>> external storage and connected to Knoppix
>>>> here is info:
>>>> Linux Knoppix 2.6.19 #7 SMP PREEMPT Sun Dec 17 22:01:07 CET 2006 i686
>>>> GNU/Linux
>>>>
>>>> xfs version:
>>>> xfs_info version 2.8.11
>>>
>>> Which is x86....
>>>
>>>> dmesg shows:
>>>> Starting XFS recovery on filesystem: hda (logdev: internal)
>>>> Filesystem "hda": XFS internal error xlog_valid_rec_header(1) at line
>>>> 3503 of file fs/xfs/xfs_log_recover.c.  Caller 0xd14f14d2
>>>> [<d14eeceb>] xlog_valid_rec_header+0x10f/0x14c [xfs]
>>>> [<d14f14d2>] xlog_do_recovery_pass+0x1e2/0x940 [xfs]
>>>> [<d14f14d2>] xlog_do_recovery_pass+0x1e2/0x940 [xfs]
>>>> [<d14f34a7>] xlog_recover+0xdf/0x250 [xfs]
>>>
>>> and this is trying to replay a dirty log in ARM format. You need
>>> to get the log cleaned before you'll be able to mount it on a
>>> non-ARM platform.
>>>
>>>> xfs_repair on knoppix running 20 hours, showing:
>>>> Phase 1 - find and verify superblock...
>>>> couldn't verify primary superblock - not enough secondary superblocks
>>>> with match                   ing geometry !!!
>>>
>>> That implies a clean log - did you zero it first to get repair to
>>> run? Have you tried running repair on the ARM box?
>>>
>>> Cheers,
>>>
>>> Dave.
>>> --
>>> Dave Chinner
>>> david@xxxxxxxxxxxxx
>>>
>>
>> _______________________________________________
>> xfs mailing list
>> xfs@xxxxxxxxxxx
>> http://oss.sgi.com/mailman/listinfo/xfs
>>
>

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