public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: Internal error xfs_sb_read_verify at line 726
Date: Mon, 6 May 2013 20:30:20 +0200	[thread overview]
Message-ID: <20130506183020.GA513@x4> (raw)
In-Reply-To: <5187E290.8090109@sandeen.net>

On 2013.05.06 at 12:04 -0500, Eric Sandeen wrote:
> On 5/6/13 6:27 AM, Markus Trippelsdorf wrote:
> > 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
> 
> This seems to be a recent regression.
> 
> Comments above xfs_sb_quiet_read_verify() indicate that this behavior is
> to be avoided:
> 
>  * We may be probed for a filesystem match, so we may not want to emit
>  * messages when the superblock buffer is not actually an XFS superblock.
> 
> and it checks for proper magic prior to all the chattiness above int
> that function.
> 
> The superblock read is suposed to choose whether to be noisy or not,
> in xfs_readsb():
> 

The following patch fixes the issue for me:


diff --git a/fs/xfs/xfs_mount.c b/fs/xfs/xfs_mount.c
index f6bfbd7..db8f27f 100644
--- a/fs/xfs/xfs_mount.c
+++ b/fs/xfs/xfs_mount.c
@@ -721,6 +721,11 @@ xfs_sb_read_verify(
 	}
 	error = xfs_sb_verify(bp);
 
+	if (error == XFS_ERROR(EWRONGFS)) {
+		xfs_buf_ioerror(bp, EWRONGFS);
+		return;
+	}
+
 out_error:
 	if (error) {
 		XFS_CORRUPTION_ERROR(__func__, XFS_ERRLEVEL_LOW, mp, bp->b_addr);

-- 
Markus

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-05-06 18:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 11:27 Internal error xfs_sb_read_verify at line 726 Markus Trippelsdorf
2013-05-06 17:04 ` Eric Sandeen
2013-05-06 18:30   ` Markus Trippelsdorf [this message]
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=20130506183020.GA513@x4 \
    --to=markus@trippelsdorf.de \
    --cc=sandeen@sandeen.net \
    --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