kern/120319: fsck on read-only root fs upgrades it to read-write
Yar Tikhiy
yar at bsd.chem.msu.ru
Wed Feb 6 14:40:01 UTC 2008
>Number: 120319
>Category: kern
>Synopsis: fsck on read-only root fs upgrades it to read-write
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Feb 06 14:40:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Yar Tikhiy
>Release: FreeBSD 8.0-CURRENT i386
>Organization:
none
>Environment:
System: FreeBSD behemoth.ramtel.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #7: Wed Feb 6 15:46:33 MSK 2008 yar at behemoth.ramtel.ru:/mnt/obj/mnt/src/sys/BEHEMOTH2 i386
>Description:
Running fsck(8) on the root file system mounted read-only
(e.g., from single user mode) results in the mount upgraded
to read-write.
This problem seems to manifest itself only on the root file
system. It doesn't matter if fsck runs in read-only (-n)
or read-write mode.
This issue might be related to that from PR bin/106636
as both fsck_ffs and mountd invoke nmount(2) to update
the mount under the conditions described in these PRs.
>How-To-Repeat:
[kernel boots...]
Trying to mount root from ufs:/dev/ad0s3a
Enter full pathname of shell or RETURN for /bin/sh:
# mount
/dev/ad0s3a on / (ufs, local, read-only)
devfs on /dev (devfs, local)
# fsck /
** /dev/ad0s3a
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
3847 files, 190700 used, 63115 free (675 frags, 7805 blocks, 0.3% fragmentation)
# mount
/dev/ad0s3a on / (ufs, local)
devfs on /dev (devfs, local)
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list