* Yar Tikhiy <yar_at_comp.chem.msu.su> wrote: > Hi all, > > Has anybody else noticed the following strangeness: running fsck > on the read-only / (from single user) results in the / mount upgraded > to read-write? E.g.: > > Trying to mount root from ufs:/dev/ad0s3a > WARNING: / was not properly dismounted > start_init: trying /sbin/init > 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 > 3850 files, 189623 used, 64192 free (680 frags, 7939 blocks, 0.3% fragmentation) > ***** FILE SYSTEM MARKED CLEAN ***** > # mount > /dev/ad0s3a on / (ufs, local) > devfs on /dev (devfs, local) > > I guess that `fsck /' issues a mount reload after modifying the FS, > but IMHO it shouldn't remount the FS read-write, should it? Could be related to this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/106636 -- Ed Schouten <ed_at_fxq.nl> WWW: http://g-rave.nl/
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:26 UTC