public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Eric Sandeen <sandeen@sandeen.net>,
	util-linux@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Mount probing not silent. Internal error xfs_sb_read_verify at line 726
Date: Thu, 9 May 2013 09:29:55 +0200	[thread overview]
Message-ID: <20130509072955.GA17527@x2.net.home> (raw)
In-Reply-To: <20130507052430.GA508@x4>

On Tue, May 07, 2013 at 07:24:30AM +0200, Markus Trippelsdorf wrote:
> On 2013.05.07 at 10:23 +1000, Dave Chinner wrote:
> > On Mon, May 06, 2013 at 04:48:39PM -0500, Eric Sandeen wrote:
> > I think that mount needs fixing, not XFS. mount needs to be doing
> > silent mounts when doing this brute forcing, not noisy, explicit
> > mounts that we expect to throw errors if there is a problem.

 Good idea. Fixed.

> > BTW, strace indicates that MS_SILENT is not being used during brute
> > force mounts:
> > 
> > # strace -vx mount /dev/vdb /mnt/scratch/ 2>&1 |grep ^mount
> > mount("/dev/vdb", "/mnt/scratch/", "reiserfs", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument)
> > mount("/dev/vdb", "/mnt/scratch/", "ext3", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument)
> > mount("/dev/vdb", "/mnt/scratch/", "ext2", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument)
> > mount("/dev/vdb", "/mnt/scratch/", "ext4", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument)
> > ....
> > 
> > So this really looks like a bug in mount, not the filesystem handling
> > of slient mounts...
> 
> So, lets CC util-linux...

 Thanks.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

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

  parent reply	other threads:[~2013-05-09  7: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
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 [this message]
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=20130509072955.GA17527@x2.net.home \
    --to=kzak@redhat.com \
    --cc=markus@trippelsdorf.de \
    --cc=sandeen@sandeen.net \
    --cc=util-linux@vger.kernel.org \
    --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