From: Dave Chinner <david@fromorbit.com>
To: Gomel Kiev <gomelkiev@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs error
Date: Thu, 8 Jan 2009 12:19:36 +1100 [thread overview]
Message-ID: <20090108011936.GF9448@disturbed> (raw)
In-Reply-To: <d96784ac0901062202t42927621r196894b6b2cc9449@mail.gmail.com>
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@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-08 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 6:02 xfs error Gomel Kiev
2009-01-07 12:16 ` Justin Piszcz
[not found] ` <d96784ac0901071055k1daa4102v29afba929a91bec7@mail.gmail.com>
[not found] ` <alpine.DEB.1.10.0901071520490.19624@p34.internal.lan>
[not found] ` <d96784ac0901071601q610a6be1n96ebb4ebcb289e2@mail.gmail.com>
2009-01-08 0:03 ` Justin Piszcz
2009-01-08 0:03 ` Gomel Kiev
2009-01-08 1:19 ` Dave Chinner [this message]
2009-01-08 1:39 ` Gomel Kiev
2009-01-08 1:55 ` Eric Sandeen
2009-01-08 2:00 ` Gomel Kiev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090108011936.GF9448@disturbed \
--to=david@fromorbit.com \
--cc=gomelkiev@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox