Date: Tue, 9 Feb 2016 00:37:15 +0100 From: Polytropon <freebsd@edvax.de> To: Paul Beard <paulbeard@gmail.com> Cc: FreeBSD-questions <questions@freebsd.org> Subject: Re: fsck is failing to clean a filesystem Message-ID: <20160209003715.86885013.freebsd@edvax.de> In-Reply-To: <15664107-4DD3-4717-9E3E-128507A3434B@gmail.com> References: <201B1734-C8F3-439A-B788-AC177D1280C3@gmail.com> <CAA2O=b9oPKX7yq4DaC2hdNY_dxFbqH9Twz42x64oRnhX5i0t4A@mail.gmail.com> <15664107-4DD3-4717-9E3E-128507A3434B@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 8 Feb 2016 15:25:41 -0800, Paul Beard wrote: > > > On Feb 8, 2016, at 2:36 PM, Anton Sayetsky <vsasjason@gmail.com> wrote: > > > > Do you have free space on partition? > > Yes. After mounting readonly and starting networking, I can get better information. > > Filesystem Size Used Avail Capacity Mounted on > /dev/gpt/gprootfs 1.9G 847M 974M 47% / > devfs 1.0K 1.0K 0B 100% /dev > /dev/gpt/gptmpfs 248M 52K 228M 0% /tmp > /dev/gpt/gpvarfs 4.8G 4.5G 338K 100% /var > fdescfs 1.0K 1.0K 0B 100% /dev/fd > /dev/gpt/gpusrfs 53G 42G 7.1G 85% /usr > > Not sure what to make of "BAD TYPE VALUE FOR '..’ “ This indicates that the inode entry for "..", the parent directory, does not have a valid node type (file, directory, special, link, etc.). So fsck doesn't know how to "re-instantiate" this particular ".." entry, as it seems. Your /usr partition has 7 GB free space. > [root@ ~]# fsck -fy /usr > ** /dev/gpt/gpusrfs > ** Last Mounted on /usr > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > BAD TYPE VALUE FOR '..' I=5628928 OWNER=www MODE=40775 > SIZE=512 MTIME=Jan 2 20:15 2016 > DIR=? > > FIX? yes > > BAD TYPE VALUE I=5605455 OWNER=www MODE=100644 > SIZE=64694 MTIME=Jan 9 16:02 2016 > FILE=? > > FIX? yes > > ** Phase 3 - Check Connectivity > UNREF DIR I=5628928 OWNER=www MODE=40775 > SIZE=512 MTIME=Jan 2 20:15 2016 > RECONNECT? yes > > SORRY. NO SPACE IN lost+found DIRECTORY > > UNREF DIR I=2520064 OWNER=www MODE=40755 > SIZE=512 MTIME=Mar 4 21:20 2015 > RECONNECT? yes > > SORRY. NO SPACE IN lost+found DIRECTORY > > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 876428 files, 21855071 used, 5942870 free (79838 frags, 732879 blocks, 0.3% fragmentation) > > ***** FILE SYSTEM STILL DIRTY ***** > > ***** FILE SYSTEM WAS MODIFIED ***** > > ***** PLEASE RERUN FSCK ***** It looks like fsck needs more free space for entries to create in the lost+found/ subdirectory. However, the fsck output indicates a quite heavy file system inconsistency problem. In worst case, mount -o ro, copy all files, re-initialize the filesystem with newfs, and then copy the files back. Use tar or rsync or cpio to make sure all the file attributes are properly transferred. This should be possible in case you cannot resolve the filesystem problem. And check if /usr/lost+found does already contain something. Just in case. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160209003715.86885013.freebsd>