From: Kevin Richter <xfs@pzystorm.de>
To: xfs@oss.sgi.com
Subject: Problem with XFS on USB 2TB HD
Date: Sat, 18 Dec 2010 12:26:07 +0100 [thread overview]
Message-ID: <4D0C9A4F.4040108@pzystorm.de> (raw)
Hi,
I have an external USB 2TB harddisk with an XFS filesystem connected to
a Debian Lenny with a 2.6.33.4 kernel.
5 days ago I backuped my data to this external drive. While this backup
process the USB port got reset and now all the data on the xfs is lost.
I cannot mount the filesystem anymore.
home:/# mount /dev/mapper/backup /mnt/backup/
mount: wrong fs type, bad option, bad superblock on /dev/mapper/backup,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
home:/# mount -t xfs /dev/mapper/backup /mnt/backup/
mount: wrong fs type, bad option, bad superblock on /dev/mapper/backup,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
The XFS is in a LUKS volume, but the luksOpen works flawlessly
(cryptsetup luksOpen /dev/sdb4 backup).
The syslog at the time of the backup process:
Dec 13 22:34:26 home kernel: usb 1-5: reset high speed USB device using
ehci_hcd and address 5
Dec 13 22:34:37 home kernel: usb 1-5: reset high speed USB device using
ehci_hcd and address 5
Dec 13 22:35:15 home kernel: d2fd1000: c2 5b ed 04 29 c1 19 04 dd 51 f8
84 5c ca 33 79 .[..)....Q..\.3y
Dec 13 22:35:15 home kernel: Filesystem "dm-0": XFS internal error
xfs_da_do_buf(2) at line 2113 of file fs/xfs/xfs_da_btree.c. Caller
0xc115d3cf
Dec 13 22:35:15 home kernel:
Dec 13 22:35:15 home kernel: Pid: 30113, comm: smbd Not tainted 2.6.33.4 #4
Dec 13 22:35:15 home kernel: Call Trace:
Dec 13 22:35:15 home kernel: [<c116720e>] xfs_error_report+0x2c/0x2e
Dec 13 22:35:15 home kernel: [<c1167245>] xfs_corruption_error+0x35/0x40
Dec 13 22:35:15 home kernel: [<c115d3cf>] ? xfs_da_read_buf+0x18/0x1d
Dec 13 22:35:15 home kernel: [<c115d2bc>] xfs_da_do_buf+0x571/0x629
Dec 13 22:35:15 home kernel: [<c115d3cf>] ? xfs_da_read_buf+0x18/0x1d
Dec 13 22:35:15 home kernel: [<c1372a76>] ? ip_output+0x78/0x7d
Dec 13 22:35:15 home kernel: [<c13724f7>] ? ip_queue_xmit+0x2ce/0x304
Dec 13 22:35:15 home kernel: [<c115d3cf>] xfs_da_read_buf+0x18/0x1d
Dec 13 22:35:15 home kernel: [<c11605b0>] ?
xfs_dir2_block_lookup_int+0x39/0x17c
Dec 13 22:35:15 home kernel: [<c11605b0>]
xfs_dir2_block_lookup_int+0x39/0x17c
Dec 13 22:35:15 home kernel: [<c10cb7fb>] ? __ext3_get_inode_loc+0xc6/0x260
Dec 13 22:35:15 home kernel: [<c114f48e>] ? xfs_bmap_last_offset+0xe8/0xfc
Dec 13 22:35:15 home kernel: [<c1160b34>] xfs_dir2_block_lookup+0x16/0xa2
Dec 13 22:35:15 home kernel: [<c115f993>] xfs_dir_lookup+0x98/0x100
Dec 13 22:35:15 home kernel: [<c118131b>] xfs_lookup+0x3d/0x94
Dec 13 22:35:15 home kernel: [<c1188736>] xfs_vn_lookup+0x38/0x70
Dec 13 22:35:15 home kernel: [<c10704d0>] do_lookup+0xd0/0x16f
Dec 13 22:35:15 home kernel: [<c1071e27>] link_path_walk+0x63b/0x9dc
Dec 13 22:35:15 home kernel: [<c10722f5>] path_walk+0x50/0xb2
Dec 13 22:35:15 home kernel: [<c1072400>] do_path_lookup+0x21/0x42
Dec 13 22:35:15 home kernel: [<c1072c27>] user_path_at+0x3c/0x67
Dec 13 22:35:15 home kernel: [<c106cc20>] vfs_fstatat+0x2d/0x54
Dec 13 22:35:15 home kernel: [<c106cd18>] vfs_stat+0x13/0x15
Dec 13 22:35:15 home kernel: [<c106cd2e>] sys_stat64+0x14/0x28
Dec 13 22:35:15 home kernel: [<c10025d0>] sysenter_do_call+0x12/0x26
The current XFS header bytes of the /dev/mapper/backup volume:
00000000 58 46 53 42 00 00 10 00 00 00 00 00 1c d8 c3 a4
|XFSB.........Øä|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
00000020 ec 24 29 ae 9c 2f 4a 75 a8 59 58 14 b5 2d 5e ac
|ì$)®./Ju¨YX.µ-^¬|
00000030 00 00 00 00 10 00 00 04 00 00 00 00 00 00 00 80
|................|
00000040 98 55 e4 53 ef e6 e9 03 9a 71 4f 19 3f 8b 6f 14
|.UäSïæé..qO.?.o.|
00000050 75 d6 51 9a dd 84 53 3e c4 80 ae a1 c2 83 53 5e
|uÖQ.Ý.S>Ä.®¡Â.S^|
00000060 69 c3 f8 1b 35 0b 15 f2 4f 15 46 42 79 6f 8b 13
|iÃø.5..òO.FByo..|
00000070 4c 65 64 ba 38 cd 51 8b 00 00 00 00 2c f9 ac 2c
|Ledº8ÍQ.....,ù¬,|
00000080 47 91 80 45 73 3e 93 77 8f 95 80 81 ab 8b b8 eb
|G..Es>.w....«.¸ë|
00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
000000a0 ec 24 29 ae 9c 2f 4a 75 a8 59 58 14 b5 2d 5e ac
|ì$)®./Ju¨YX.µ-^¬|
000000b0 00 00 00 00 10 00 00 04 00 00 00 00 00 00 00 80
|................|
000000c0 98 55 e4 53 ef e6 e9 03 9a 71 4f 19 3f 8b 6f 14
|.UäSïæé..qO.?.o.|
000000d0 75 d6 51 9a dd 84 53 3e c4 80 ae a1 c2 83 53 5e
|uÖQ.Ý.S>Ä.®¡Â.S^|
000000e0 69 c3 f8 1b 35 0b 15 f2 4f 15 46 42 79 6f 8b 13
|iÃø.5..òO.FByo..|
000000f0 4c 65 64 ba 38 cd 51 8b 00 00 00 00 2c f9 ac 2c
|Ledº8ÍQ.....,ù¬,|
00000100 47 91 80 45 73 3e 93 77 8f 95 80 81 ab 8b b8 eb
|G..Es>.w....«.¸ë|
00000110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
00000120 ec 24 29 ae 9c 2f 4a 75 a8 59 58 14 b5 2d 5e ac
|ì$)®./Ju¨YX.µ-^¬|
00000130 00 00 00 00 10 00 00 04 00 00 00 00 00 00 00 80
|................|
00000140 98 55 e4 53 ef e6 e9 03 9a 71 4f 19 3f 8b 6f 14
|.UäSïæé..qO.?.o.|
00000150 75 d6 51 9a dd 84 53 3e c4 80 ae a1 c2 83 53 5e
|uÖQ.Ý.S>Ä.®¡Â.S^|
00000160 69 c3 f8 1b 35 0b 15 f2 4f 15 46 42 79 6f 8b 13
|iÃø.5..òO.FByo..|
00000170 4c 65 64 ba 38 cd 51 8b 00 00 00 00 2c f9 ac 2c
|Ledº8ÍQ.....,ù¬,|
00000180 47 91 80 45 73 3e 93 77 8f 95 80 81 ab 8b b8 eb
|G..Es>.w....«.¸ë|
00000190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
000001a0 ec 24 29 ae 9c 2f 4a 75 a8 59 58 14 b5 2d 5e ac
|ì$)®./Ju¨YX.µ-^¬|
000001b0 00 00 00 00 10 00 00 04 00 00 00 00 00 00 00 80
|................|
000001c0 98 55 e4 53 ef e6 e9 03 9a 71 4f 19 3f 8b 6f 14
|.UäSïæé..qO.?.o.|
000001d0 75 d6 51 9a dd 84 53 3e c4 80 ae a1 c2 83 53 5e
|uÖQ.Ý.S>Ä.®¡Â.S^|
000001e0 69 c3 f8 1b 35 0b 15 f2 4f 15 46 42 79 6f 8b 13
|iÃø.5..òO.FByo..|
000001f0 4c 65 64 ba 38 cd 51 8b 00 00 00 00 2c f9 ac 2c
|Ledº8ÍQ.....,ù¬,|
xfs_repair runs since a few hours, but has just printed a bunch of dots.
The first line of xfs_repair is "bad or unsupported version" and that it
cant find a superblock.
Some ideas?
What happened?
Do I use a buggy version?
I have 2.9.8 (http://packages.debian.org/lenny/xfsprogs)
What can I do to avoid these problems in the future?
It is a problem with the interaction of LUKS, XFS and USB?
Thanks in advance
Kevin
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-12-18 11:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 11:26 Kevin Richter [this message]
2010-12-19 2:04 ` Problem with XFS on USB 2TB HD Kevin Richter
2010-12-19 2:37 ` Stan Hoeppner
2010-12-19 14:57 ` Emmanuel Florac
2010-12-19 17:30 ` Eric Sandeen
2010-12-20 0:10 ` Dave Chinner
2010-12-20 2:56 ` Kevin Richter
2010-12-20 4:51 ` Dave Chinner
2010-12-20 9:55 ` Emmanuel Florac
2011-01-12 23:37 ` Kevin Richter
2011-01-13 13:15 ` Extreme fragmentation when backing up via NFS Phil Karn
2011-01-14 4:51 ` Dave Chinner
2011-01-13 21:52 ` Problem with XFS on USB 2TB HD Geoffrey Wehrman
2010-12-20 8:59 ` Michael Monnerie
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=4D0C9A4F.4040108@pzystorm.de \
--to=xfs@pzystorm.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.