Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Jan 2019 23:28:50 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 234954] fsck -T flag suffers from ufs/ffs filesystem type ambiguity
Message-ID:  <bug-234954-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234954

            Bug ID: 234954
           Summary: fsck -T flag suffers from ufs/ffs filesystem type
                    ambiguity
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: ian@FreeBSD.org

The fsck(8) -T option is used to route options to the filesystem-specific
programs it runs.  The fsck(8) wrapper program gleans the name of the
filesystem type from a variety of sources... on the commandline, from fstab,
from geom info, etc.  From some sources of info it decides a filesystem is =
ufs,
from other sources it translates ufs to ffs.

This means that you can't reliably specify either -T ufs: or -T ffs: and be
sure that the option will take effect.  fsck(8) should probably translate
everything (-T names and filesystem type names) to either ufs or ffs, but a=
fter
poking around a bit in the code, it appears that this translation has to ha=
ppen
in many scattered locations.

A workaround is available, by specifying the option(s) you want twice, using
both of the filesystem type names.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234954-227>