Date: Wed, 3 Jul 2019 06:41:11 -0400 From: Ed Maste <emaste@freebsd.org> To: Doug Hardie <bc979@lafn.org> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-19:10.ufs Message-ID: <CAPyFy2CRrLZwbpHXAnbT-RWT35TDbtZjtqenLeAp6Vgxp--sXg@mail.gmail.com> In-Reply-To: <D6176CD2-C613-42C0-BC9B-2695B8048C06@lafn.org> References: <20190703004924.8A5411A7D5@freefall.freebsd.org> <D6176CD2-C613-42C0-BC9B-2695B8048C06@lafn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 3 Jul 2019 at 06:05, Doug Hardie <bc979@lafn.org> wrote: > > > Afterwards, reboot the system and run: > > > > # fsck -t ufs -f -p -T ufs:-z > > > > to clean up your existing filesystems. > > After rebooting the system I get: > > master# fsck -t ufs -f -p -T ufs:-z > /dev/ada0p2: NO WRITE ACCESS > /dev/ada0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > > Is this expected result or is there a problem here? Thanks for reporting this - it looks like some more detail will need to be added to the SA. The fsck needs to be run without the filesystem being mounted read-write, most likely in single user mode. I brought a test system down to single user mode, remounted / as read-only, and ran the fsck command as follows: # shutdown now ... Enter full pathname of shell or RETURN for /bin/sh: # mount -u -o ro / # fsck -t ufs -f -p -T ufs:-z /dev/ufsid/5bf225f5889c157d: 28576 files, 304757 used, 27570235 free (899 frags, 3446167 blocks, 0.0% fragmentation) # exit
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2CRrLZwbpHXAnbT-RWT35TDbtZjtqenLeAp6Vgxp--sXg>