* xfs error @ 2009-01-07 6:02 Gomel Kiev 2009-01-07 12:16 ` Justin Piszcz 2009-01-08 1:19 ` Dave Chinner 0 siblings, 2 replies; 8+ messages in thread From: Gomel Kiev @ 2009-01-07 6:02 UTC (permalink / raw) To: xfs 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 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 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 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 Dec 12 04:26:29 BUFFALO kernel: 0x0: 60 f2 de 8d 58 cf 08 48 46 76 56 8f 1e 3e 78 29 Dec 12 04:26:29 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 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 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] [<d14edeca>] xfs_log_mount+0x3ce/0x5cc [xfs] [<d14f5f81>] xfs_mountfs+0xb8d/0x106c [xfs] [<c011cca0>] default_wake_function+0x0/0xc [<c024c88f>] _atomic_dec_and_lock+0x3f/0x74 [<d150ecdf>] xfs_mountfs_check_barriers+0xd3/0xf4 [xfs] [<d14fd33c>] xfs_mount+0x628/0x978 [xfs] [<c024c7de>] __next_cpu+0x12/0x20 [<c0170e0b>] __percpu_populate_mask+0x4b/0x74 [<d14a46d4>] xfs_qm_parseargs+0x0/0x2a4 [xfs] [<d14a48e1>] xfs_qm_parseargs+0x20d/0x2a4 [xfs] [<d14fcd14>] xfs_mount+0x0/0x978 [xfs] [<d150f549>] vfs_mount+0x21/0x24 [xfs] [<d150f3a0>] xfs_fs_fill_super+0x6c/0x1c4 [xfs] [<c0250aa7>] snprintf+0x1f/0x24 [<c01ac963>] disk_name+0xa7/0xb4 [<c017502d>] get_sb_bdev+0xed/0x124 [<d150e788>] xfs_fs_get_sb+0x20/0x28 [xfs] [<d150f334>] xfs_fs_fill_super+0x0/0x1c4 [xfs] [<c0174b74>] vfs_kern_mount+0xcc/0x138 [<c0174c1f>] do_kern_mount+0x27/0x44 [<c0188f55>] do_mount+0x2b9/0x6c8 [<c0188313>] mntput_no_expire+0x13/0x70 [<c017c435>] link_path_walk+0x65/0xcc [<c02d3d74>] idedisk_release+0x3c/0x90 [<c0185541>] iput+0x35/0x68 [<c02d3d74>] idedisk_release+0x3c/0x90 [<c0187eb7>] copy_mount_options+0x2b/0x138 [<c01893dd>] sys_mount+0x79/0xb4 [<c01035cf>] syscall_call+0x7/0xb ======================= XFS: log mount/recovery failed: error 117 XFS: log mount failed XFS mounting filesystem hda 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 !!! attempting to find secondary superblock... Help, anybody? I have 975gb (25 gb was empty) of multimedia files. I tried UFS explorer, able to recover some files, but most files size was wrong. Thanks _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xfs error 2009-01-07 6:02 xfs error Gomel Kiev @ 2009-01-07 12:16 ` Justin Piszcz [not found] ` <d96784ac0901071055k1daa4102v29afba929a91bec7@mail.gmail.com> 2009-01-08 1:19 ` Dave Chinner 1 sibling, 1 reply; 8+ messages in thread From: Justin Piszcz @ 2009-01-07 12:16 UTC (permalink / raw) To: Gomel Kiev; +Cc: xfs On Tue, 6 Jan 2009, 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 > > 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 > 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 > 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 > Dec 12 04:26:29 BUFFALO kernel: 0x0: 60 f2 de 8d 58 cf 08 48 46 76 56 > 8f 1e 3e 78 29 > Dec 12 04:26:29 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 > > 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 > > 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] > [<d14edeca>] xfs_log_mount+0x3ce/0x5cc [xfs] > [<d14f5f81>] xfs_mountfs+0xb8d/0x106c [xfs] > [<c011cca0>] default_wake_function+0x0/0xc > [<c024c88f>] _atomic_dec_and_lock+0x3f/0x74 > [<d150ecdf>] xfs_mountfs_check_barriers+0xd3/0xf4 [xfs] > [<d14fd33c>] xfs_mount+0x628/0x978 [xfs] > [<c024c7de>] __next_cpu+0x12/0x20 > [<c0170e0b>] __percpu_populate_mask+0x4b/0x74 > [<d14a46d4>] xfs_qm_parseargs+0x0/0x2a4 [xfs] > [<d14a48e1>] xfs_qm_parseargs+0x20d/0x2a4 [xfs] > [<d14fcd14>] xfs_mount+0x0/0x978 [xfs] > [<d150f549>] vfs_mount+0x21/0x24 [xfs] > [<d150f3a0>] xfs_fs_fill_super+0x6c/0x1c4 [xfs] > [<c0250aa7>] snprintf+0x1f/0x24 > [<c01ac963>] disk_name+0xa7/0xb4 > [<c017502d>] get_sb_bdev+0xed/0x124 > [<d150e788>] xfs_fs_get_sb+0x20/0x28 [xfs] > [<d150f334>] xfs_fs_fill_super+0x0/0x1c4 [xfs] > [<c0174b74>] vfs_kern_mount+0xcc/0x138 > [<c0174c1f>] do_kern_mount+0x27/0x44 > [<c0188f55>] do_mount+0x2b9/0x6c8 > [<c0188313>] mntput_no_expire+0x13/0x70 > [<c017c435>] link_path_walk+0x65/0xcc > [<c02d3d74>] idedisk_release+0x3c/0x90 > [<c0185541>] iput+0x35/0x68 > [<c02d3d74>] idedisk_release+0x3c/0x90 > [<c0187eb7>] copy_mount_options+0x2b/0x138 > [<c01893dd>] sys_mount+0x79/0xb4 > [<c01035cf>] syscall_call+0x7/0xb > ======================= > XFS: log mount/recovery failed: error 117 > XFS: log mount failed > XFS mounting filesystem hda > > > 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 !!! > > attempting to find secondary superblock... > > > > Help, anybody? > I have 975gb (25 gb was empty) of multimedia files. > I tried UFS explorer, able to recover some files, but most files size was wrong. > > Thanks > > _______________________________________________ > xfs mailing list > xfs@oss.sgi.com > http://oss.sgi.com/mailman/listinfo/xfs > Looks like you have some serious corruption; however your best bet would be to boot knoppix and run xfs_repair (from the latest xfsprogs) package and report back (preferrably with a strace of xfs_repair if its hanging). In addition, a metadump of the filesystem may be useful as well, Eric/other XFS members can analyze why the mount is failing if they have that. Justin. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 8+ messages in thread
[parent not found: <d96784ac0901071055k1daa4102v29afba929a91bec7@mail.gmail.com>]
[parent not found: <alpine.DEB.1.10.0901071520490.19624@p34.internal.lan>]
[parent not found: <d96784ac0901071601q610a6be1n96ebb4ebcb289e2@mail.gmail.com>]
* Re: xfs error [not found] ` <d96784ac0901071601q610a6be1n96ebb4ebcb289e2@mail.gmail.com> @ 2009-01-08 0:03 ` Justin Piszcz 2009-01-08 0:03 ` Gomel Kiev 1 sibling, 0 replies; 8+ messages in thread From: Justin Piszcz @ 2009-01-08 0:03 UTC (permalink / raw) To: Gomel Kiev; +Cc: xfs Adding xfs@oss with results. On Wed, 7 Jan 2009, Gomel Kiev wrote: > xfs_db -V -> 2.10.2 > here is output form xfs_metadump: > 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 > > dmesg: > xfs_db[5893]: segfault at 28 ip b7ec31c0 sp bfd04bcc error 4 in > libpthread-2.7.so[b7ebc000+13000] > xfs_db[5895]: segfault at 28 ip b80701c0 sp bfab217c error 4 in > libpthread-2.7.so[b8069000+13000] > xfs_db[5923]: segfault at 28 ip b80671c0 sp bffaae6c error 4 in > libpthread-2.7.so[b8060000+13000] > xfs_db[5925]: segfault at 28 ip b7ebe1c0 sp bf9ff8bc error 4 in > libpthread-2.7.so[b7eb7000+13000] > xfs_db[5928]: segfault at 28 ip b7f511c0 sp bfc92b8c error 4 in > libpthread-2.7.so[b7f4a000+13000] > xfs_db[5931]: segfault at 28 ip b80591c0 sp bfd9b48c error 4 in > libpthread-2.7.so[b8052000+13000] > xfs_db[5932]: segfault at 28 ip b7f361c0 sp bfc79b6c error 4 in > libpthread-2.7.so[b7f2f000+13000] > > any ideas? > thanks for help > > > > On Wed, Jan 7, 2009 at 1:20 PM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote: >> $ dpkg -S xfs_metadump xfsprogs: /usr/sbin/xfs_metadump >> xfsprogs: /usr/share/man/man8/xfs_metadump.8.gz >> >> >> On Wed, 7 Jan 2009, Gomel Kiev wrote: >> >>> 1. xfs_repair running for 20 hours , and can not find superblock >>> 2. on my knoppix I don't have xfs_metadump. >>> where I can get it? >>> thx >>> >>> >>> On Wed, Jan 7, 2009 at 5:16 AM, Justin Piszcz <jpiszcz@lucidpixels.com> >>> wrote: >>>> >>>> >>>> On Tue, 6 Jan 2009, 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 >>>>> >>>>> 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 >>>>> 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 >>>>> 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 >>>>> Dec 12 04:26:29 BUFFALO kernel: 0x0: 60 f2 de 8d 58 cf 08 48 46 76 56 >>>>> 8f 1e 3e 78 29 >>>>> Dec 12 04:26:29 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 >>>>> >>>>> 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 >>>>> >>>>> 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] >>>>> [<d14edeca>] xfs_log_mount+0x3ce/0x5cc [xfs] >>>>> [<d14f5f81>] xfs_mountfs+0xb8d/0x106c [xfs] >>>>> [<c011cca0>] default_wake_function+0x0/0xc >>>>> [<c024c88f>] _atomic_dec_and_lock+0x3f/0x74 >>>>> [<d150ecdf>] xfs_mountfs_check_barriers+0xd3/0xf4 [xfs] >>>>> [<d14fd33c>] xfs_mount+0x628/0x978 [xfs] >>>>> [<c024c7de>] __next_cpu+0x12/0x20 >>>>> [<c0170e0b>] __percpu_populate_mask+0x4b/0x74 >>>>> [<d14a46d4>] xfs_qm_parseargs+0x0/0x2a4 [xfs] >>>>> [<d14a48e1>] xfs_qm_parseargs+0x20d/0x2a4 [xfs] >>>>> [<d14fcd14>] xfs_mount+0x0/0x978 [xfs] >>>>> [<d150f549>] vfs_mount+0x21/0x24 [xfs] >>>>> [<d150f3a0>] xfs_fs_fill_super+0x6c/0x1c4 [xfs] >>>>> [<c0250aa7>] snprintf+0x1f/0x24 >>>>> [<c01ac963>] disk_name+0xa7/0xb4 >>>>> [<c017502d>] get_sb_bdev+0xed/0x124 >>>>> [<d150e788>] xfs_fs_get_sb+0x20/0x28 [xfs] >>>>> [<d150f334>] xfs_fs_fill_super+0x0/0x1c4 [xfs] >>>>> [<c0174b74>] vfs_kern_mount+0xcc/0x138 >>>>> [<c0174c1f>] do_kern_mount+0x27/0x44 >>>>> [<c0188f55>] do_mount+0x2b9/0x6c8 >>>>> [<c0188313>] mntput_no_expire+0x13/0x70 >>>>> [<c017c435>] link_path_walk+0x65/0xcc >>>>> [<c02d3d74>] idedisk_release+0x3c/0x90 >>>>> [<c0185541>] iput+0x35/0x68 >>>>> [<c02d3d74>] idedisk_release+0x3c/0x90 >>>>> [<c0187eb7>] copy_mount_options+0x2b/0x138 >>>>> [<c01893dd>] sys_mount+0x79/0xb4 >>>>> [<c01035cf>] syscall_call+0x7/0xb >>>>> ======================= >>>>> XFS: log mount/recovery failed: error 117 >>>>> XFS: log mount failed >>>>> XFS mounting filesystem hda >>>>> >>>>> >>>>> 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 !!! >>>>> >>>>> attempting to find secondary superblock... >>>>> >>>>> >>>>> >>>>> Help, anybody? >>>>> I have 975gb (25 gb was empty) of multimedia files. >>>>> I tried UFS explorer, able to recover some files, but most files size >>>>> was >>>>> wrong. >>>>> >>>>> Thanks >>>>> >>>>> _______________________________________________ >>>>> xfs mailing list >>>>> xfs@oss.sgi.com >>>>> http://oss.sgi.com/mailman/listinfo/xfs >>>>> >>>> >>>> Looks like you have some serious corruption; however your best bet would >>>> be >>>> to boot knoppix and run xfs_repair (from the latest xfsprogs) package and >>>> report back (preferrably with a strace of xfs_repair if its hanging). In >>>> addition, a metadump of the filesystem may be useful as well, Eric/other >>>> XFS >>>> members can analyze why the mount is failing if they have that. >>>> >>>> Justin. >>>> >>>> >>>> >>> >> > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 8+ messages in thread
* xfs error [not found] ` <d96784ac0901071601q610a6be1n96ebb4ebcb289e2@mail.gmail.com> 2009-01-08 0:03 ` Justin Piszcz @ 2009-01-08 0:03 ` Gomel Kiev 1 sibling, 0 replies; 8+ messages in thread From: Gomel Kiev @ 2009-01-08 0:03 UTC (permalink / raw) To: xfs more info: xfs_db -V -> 2.10.2 here is output form xfs_metadump: 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 dmesg: xfs_db[5893]: segfault at 28 ip b7ec31c0 sp bfd04bcc error 4 in libpthread-2.7.so[b7ebc000+13000] xfs_db[5895]: segfault at 28 ip b80701c0 sp bfab217c error 4 in libpthread-2.7.so[b8069000+13000] xfs_db[5923]: segfault at 28 ip b80671c0 sp bffaae6c error 4 in libpthread-2.7.so[b8060000+13000] xfs_db[5925]: segfault at 28 ip b7ebe1c0 sp bf9ff8bc error 4 in libpthread-2.7.so[b7eb7000+13000] xfs_db[5928]: segfault at 28 ip b7f511c0 sp bfc92b8c error 4 in libpthread-2.7.so[b7f4a000+13000] xfs_db[5931]: segfault at 28 ip b80591c0 sp bfd9b48c error 4 in libpthread-2.7.so[b8052000+13000] xfs_db[5932]: segfault at 28 ip b7f361c0 sp bfc79b6c error 4 in libpthread-2.7.so[b7f2f000+13000] any ideas? thanks for help On Wed, Jan 7, 2009 at 1:20 PM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote: > $ dpkg -S xfs_metadump xfsprogs: /usr/sbin/xfs_metadump > xfsprogs: /usr/share/man/man8/xfs_metadump.8.gz > > > On Wed, 7 Jan 2009, Gomel Kiev wrote: > >> 1. xfs_repair running for 20 hours , and can not find superblock >> 2. on my knoppix I don't have xfs_metadump. >> where I can get it? >> thx >> >> >> On Wed, Jan 7, 2009 at 5:16 AM, Justin Piszcz <jpiszcz@lucidpixels.com> >> wrote: >>> >>> >>> On Tue, 6 Jan 2009, 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 >>>> >>>> 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 >>>> 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 >>>> 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 >>>> Dec 12 04:26:29 BUFFALO kernel: 0x0: 60 f2 de 8d 58 cf 08 48 46 76 56 >>>> 8f 1e 3e 78 29 >>>> Dec 12 04:26:29 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 >>>> >>>> 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 >>>> >>>> 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] >>>> [<d14edeca>] xfs_log_mount+0x3ce/0x5cc [xfs] >>>> [<d14f5f81>] xfs_mountfs+0xb8d/0x106c [xfs] >>>> [<c011cca0>] default_wake_function+0x0/0xc >>>> [<c024c88f>] _atomic_dec_and_lock+0x3f/0x74 >>>> [<d150ecdf>] xfs_mountfs_check_barriers+0xd3/0xf4 [xfs] >>>> [<d14fd33c>] xfs_mount+0x628/0x978 [xfs] >>>> [<c024c7de>] __next_cpu+0x12/0x20 >>>> [<c0170e0b>] __percpu_populate_mask+0x4b/0x74 >>>> [<d14a46d4>] xfs_qm_parseargs+0x0/0x2a4 [xfs] >>>> [<d14a48e1>] xfs_qm_parseargs+0x20d/0x2a4 [xfs] >>>> [<d14fcd14>] xfs_mount+0x0/0x978 [xfs] >>>> [<d150f549>] vfs_mount+0x21/0x24 [xfs] >>>> [<d150f3a0>] xfs_fs_fill_super+0x6c/0x1c4 [xfs] >>>> [<c0250aa7>] snprintf+0x1f/0x24 >>>> [<c01ac963>] disk_name+0xa7/0xb4 >>>> [<c017502d>] get_sb_bdev+0xed/0x124 >>>> [<d150e788>] xfs_fs_get_sb+0x20/0x28 [xfs] >>>> [<d150f334>] xfs_fs_fill_super+0x0/0x1c4 [xfs] >>>> [<c0174b74>] vfs_kern_mount+0xcc/0x138 >>>> [<c0174c1f>] do_kern_mount+0x27/0x44 >>>> [<c0188f55>] do_mount+0x2b9/0x6c8 >>>> [<c0188313>] mntput_no_expire+0x13/0x70 >>>> [<c017c435>] link_path_walk+0x65/0xcc >>>> [<c02d3d74>] idedisk_release+0x3c/0x90 >>>> [<c0185541>] iput+0x35/0x68 >>>> [<c02d3d74>] idedisk_release+0x3c/0x90 >>>> [<c0187eb7>] copy_mount_options+0x2b/0x138 >>>> [<c01893dd>] sys_mount+0x79/0xb4 >>>> [<c01035cf>] syscall_call+0x7/0xb >>>> ======================= >>>> XFS: log mount/recovery failed: error 117 >>>> XFS: log mount failed >>>> XFS mounting filesystem hda >>>> >>>> >>>> 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 !!! >>>> >>>> attempting to find secondary superblock... >>>> >>>> >>>> >>>> Help, anybody? >>>> I have 975gb (25 gb was empty) of multimedia files. >>>> I tried UFS explorer, able to recover some files, but most files size >>>> was >>>> wrong. >>>> >>>> Thanks >>>> >>>> _______________________________________________ >>>> xfs mailing list >>>> xfs@oss.sgi.com >>>> http://oss.sgi.com/mailman/listinfo/xfs >>>> >>> >>> Looks like you have some serious corruption; however your best bet would >>> be >>> to boot knoppix and run xfs_repair (from the latest xfsprogs) package and >>> report back (preferrably with a strace of xfs_repair if its hanging). In >>> addition, a metadump of the filesystem may be useful as well, Eric/other >>> XFS >>> members can analyze why the mount is failing if they have that. >>> >>> Justin. >>> >>> >>> >> > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xfs error 2009-01-07 6:02 xfs error Gomel Kiev 2009-01-07 12:16 ` Justin Piszcz @ 2009-01-08 1:19 ` Dave Chinner 2009-01-08 1:39 ` Gomel Kiev 1 sibling, 1 reply; 8+ messages in thread From: Dave Chinner @ 2009-01-08 1:19 UTC (permalink / raw) To: Gomel Kiev; +Cc: xfs 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xfs error 2009-01-08 1:19 ` Dave Chinner @ 2009-01-08 1:39 ` Gomel Kiev 2009-01-08 1:55 ` Eric Sandeen 0 siblings, 1 reply; 8+ messages in thread From: Gomel Kiev @ 2009-01-08 1:39 UTC (permalink / raw) To: Gomel Kiev, xfs 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@fromorbit.com> 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@fromorbit.com > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xfs error 2009-01-08 1:39 ` Gomel Kiev @ 2009-01-08 1:55 ` Eric Sandeen 2009-01-08 2:00 ` Gomel Kiev 0 siblings, 1 reply; 8+ messages in thread From: Eric Sandeen @ 2009-01-08 1:55 UTC (permalink / raw) To: Gomel Kiev; +Cc: xfs@oss.sgi.com 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@gmail.com> 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@fromorbit.com> > 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@fromorbit.com >> > > _______________________________________________ > xfs mailing list > xfs@oss.sgi.com > http://oss.sgi.com/mailman/listinfo/xfs > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xfs error 2009-01-08 1:55 ` Eric Sandeen @ 2009-01-08 2:00 ` Gomel Kiev 0 siblings, 0 replies; 8+ messages in thread From: Gomel Kiev @ 2009-01-08 2:00 UTC (permalink / raw) To: Eric Sandeen; +Cc: xfs@oss.sgi.com 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@sandeen.net> 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@gmail.com> 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@fromorbit.com> 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@fromorbit.com >>> >> >> _______________________________________________ >> xfs mailing list >> xfs@oss.sgi.com >> http://oss.sgi.com/mailman/listinfo/xfs >> > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2009-01-08 2:08 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2009-01-08 1:39 ` Gomel Kiev
2009-01-08 1:55 ` Eric Sandeen
2009-01-08 2:00 ` Gomel Kiev
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox