diff options
| author | Karel Zak <kzak@redhat.com> | 2010-03-15 13:46:43 +0100 |
|---|---|---|
| committer | Karel Zak <kzak@redhat.com> | 2010-03-15 13:46:43 +0100 |
| commit | c6c98f93f5e4b3fb9a8b51ed2ef9967793df7b1c (patch) | |
| tree | 2e7a565f33234947bf90343851f252142c61f4fa /include | |
| parent | f5b1bab190e86bd6a52942047d2c767ec82508d1 (diff) | |
| download | util-linux-old-c6c98f93f5e4b3fb9a8b51ed2ef9967793df7b1c.tar.gz | |
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@gentoo.org>
Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'include')
| -rw-r--r-- | include/fsprobe.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/fsprobe.h b/include/fsprobe.h index 307eb64a..9e2bf50f 100644 --- a/include/fsprobe.h +++ b/include/fsprobe.h @@ -17,6 +17,7 @@ extern char *fsprobe_get_devname_by_spec(const char *spec); extern char *fsprobe_get_label_by_devname(const char *devname); extern char *fsprobe_get_uuid_by_devname(const char *devname); extern char *fsprobe_get_fstype_by_devname(const char *devname); +extern char *fsprobe_get_fstype_by_devname_ambi(const char *devname, int *ambi); extern int fsprobe_known_fstype(const char *fstype); |