[Top] [All Lists]

Re: Internal error xfs_sb_read_verify at line 726

To: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
Subject: Re: Internal error xfs_sb_read_verify at line 726
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 06 May 2013 16:48:39 -0500
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <51881750.3090309@xxxxxxxxxxx>
References: <20130506112717.GA502@x4> <5187E290.8090109@xxxxxxxxxxx> <20130506183020.GA513@x4> <51880121.8000001@xxxxxxxxxxx> <20130506192629.GA503@x4> <5188074F.2090500@xxxxxxxxxxx> <20130506195521.GB503@x4> <51881750.3090309@xxxxxxxxxxx>
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
On 5/6/13 3:49 PM, Eric Sandeen wrote:

> Interesting, so [mount] really does try to mount by successive fs types.
> I wonder when that behavior changed (my util-linux-ng 2.17 on RHEL6 doesn't 
> do this)
> I'll take a look.

Just to satisfy my curiosity:

commit c6c98f93f5e4b3fb9a8b51ed2ef9967793df7b1c
Author: Karel Zak <kzak@xxxxxxxxxx>
Date:   Mon Mar 15 13:46:43 2010 +0100

    mount: report ambivalent FS detection, improve brute force detection
    The ambivalent probing result should be properly reported and user
    should be informed that the problem is possible to bypass by "-t
    <type>" or resolved by wipefs(8).
    The mount(8) command uses a brute force stage (calls mount(2) for all
    /{proc,etc}/fylesystems) if there is not any other way how to detect
    the filesystem type. The brute force stage should not be restricted by
    libblkid. It's possible that libblkid is not able to detect slightly
    corrupted filesystem, but kernel is able to mount such filesystem.
    Note that the brute force stage should not be used if libblkid returns
    ambivalent probing result. In this case user's intervention is required
    (e.g. mount -t <type>).
    Reported-by: Mike Frysinger <vapier@xxxxxxxxxx>
    Signed-off-by: Karel Zak <kzak@xxxxxxxxxx>

So we're getting into xfs mount with an actual "-t xfs" equivalent,
and not going down the "silent" paths.

I'll send the patch.


<Prev in Thread] Current Thread [Next in Thread>