From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: xfs@oss.sgi.com
Subject: Internal error xfs_sb_read_verify at line 726
Date: Mon, 6 May 2013 13:27:17 +0200 [thread overview]
Message-ID: <20130506112717.GA502@x4> (raw)
Today I accidentally tried to mount my backup disk at /dev/sdc instead
of /dev/sdc1 and this is what happened:
...
EXT4-fs (sdc): VFS: Can't find ext4 filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
ISOFS: Unable to identify CD-ROM format.
XFS (sdc): bad magic number
ffff8800db620000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
ffff8800db620010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
ffff8800db620020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
ffff8800db620030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
XFS (sdc): Internal error xfs_sb_read_verify at line 726 of file fs/xfs/xfs_mount.c. Caller 0xffffffff8119e5cd
CPU: 3 PID: 68 Comm: kworker/3:1H Not tainted 3.9.0-10518-gd7ab730-dirty #440
Hardware name: System manufacturer System Product Name/M4A78T-E, BIOS 3503 04/13/2011
Workqueue: xfslogd xfs_buf_iodone_work
ffffffff81537e9c ffffffff811a0416 000002d600000000 ffffffff8119e5cd
ffff8800db2e7500 0000000000000016 ffff8801c0242800 ffff88021fd94f00
ffffffff811e93d5 ffffffff8119e5cd ffff8802168ed820 ffff8800db2e75a0
Call Trace:
[<ffffffff81537e9c>] ? dump_stack+0xc/0x15
[<ffffffff811a0416>] ? xfs_corruption_error+0x56/0x80
[<ffffffff8119e5cd>] ? xfs_buf_iodone_work+0x6d/0xa0
[<ffffffff811e93d5>] ? xfs_sb_read_verify+0xf5/0x120
[<ffffffff8119e5cd>] ? xfs_buf_iodone_work+0x6d/0xa0
[<ffffffff8119e5cd>] ? xfs_buf_iodone_work+0x6d/0xa0
[<ffffffff81072cbc>] ? process_one_work+0x13c/0x3c0
[<ffffffff8107304d>] ? worker_thread+0x10d/0x3a0
[<ffffffff81072f40>] ? process_one_work+0x3c0/0x3c0
[<ffffffff8107912f>] ? kthread+0xaf/0xc0
[<ffffffff81079080>] ? __kthread_parkme+0x80/0x80
[<ffffffff8153cf2c>] ? ret_from_fork+0x7c/0xb0
[<ffffffff81079080>] ? __kthread_parkme+0x80/0x80
XFS (sdc): Corruption detected. Unmount and run xfs_repair
XFS (sdc): SB validate failed with error 22.
XFS (sdc1): Mounting Filesystem
XFS (sdc1): Ending clean mount
Seems a bit overkill to me ;-).
--
Markus
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-05-06 11:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 11:27 Markus Trippelsdorf [this message]
2013-05-06 17:04 ` Internal error xfs_sb_read_verify at line 726 Eric Sandeen
2013-05-06 18:30 ` Markus Trippelsdorf
2013-05-06 19:14 ` Eric Sandeen
2013-05-06 19:26 ` Markus Trippelsdorf
2013-05-06 19:41 ` Eric Sandeen
2013-05-06 19:55 ` Markus Trippelsdorf
2013-05-06 20:49 ` Eric Sandeen
2013-05-06 21:48 ` Eric Sandeen
2013-05-07 0:23 ` Dave Chinner
2013-05-07 0:34 ` Dave Chinner
2013-05-07 0:38 ` Eric Sandeen
2013-05-07 0:54 ` Dave Chinner
2013-05-07 5:24 ` Mount probing not silent. " Markus Trippelsdorf
2013-05-07 13:43 ` Markus Trippelsdorf
2013-05-09 7:29 ` Karel Zak
2013-05-06 21:53 ` Eric Sandeen
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=20130506112717.GA502@x4 \
--to=markus@trippelsdorf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox