Date: Wed, 10 Feb 2016 10:22:36 +0100 From: Polytropon <freebsd@edvax.de> To: Ian Smith <smithi@nimnet.asn.au> Cc: Paul Beard <paulbeard@gmail.com>, freebsd-questions@freebsd.org Subject: Re: fsck is failing to clean a filesystem Message-ID: <20160210102236.19f9c68c.freebsd@edvax.de> In-Reply-To: <20160210195431.V51785@sola.nimnet.asn.au> References: <mailman.107.1455019202.84699.freebsd-questions@freebsd.org> <20160210160149.V51785@sola.nimnet.asn.au> <C974C8D0-37C0-4708-9F1A-6CDC4716A8D4@gmail.com> <20160210195431.V51785@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 10 Feb 2016 20:11:03 +1100 (EST), Ian Smith wrote: > On Tue, 9 Feb 2016 22:10:14 -0800, Paul Beard wrote: > > > On Feb 9, 2016, at 9:14 PM, Ian Smith <smithi@nimnet.asn.au> wrote: > > >=20 > > > I know your problem is with /usr, but I=20 > > > find the fact that /var is full or too nearly so rather concerning, = and=20 > > > wonder whether that might have contributed to your problem in some w= ay,=20 > > > and whether freeing up some space there might yet help? > >=20 > > Yeah, it=FF=FFs a mess, running a full system in a 64Gb virtual disk i= s=20 > > probably asking for trouble. I think there is some cruft in /var=20 > > (databases that are no longer in use) that can be pitched. >=20 > 64GB should be plenty, depending on usage of course. A full /var is a=20 > worry, especially if it runs short of room for logging. When fsck is running, it usually happens in a mode where only / is mounted read-only, and all other file systems (such as /usr or /var) are not. So I'd say that fsck doesn't do logging somewhere into /var/log because it doesn't exist at that time. Single user mode is a state of heavily reduced system functionality, but usually sufficient for solving file system problems. > > > Also, does 'du /usr/lost+found' reveal anything? > >=20 > > It was full of stuff /usr/src, best I could make out. Not sure why it= =20 > > all ended up in there. >=20 > Well at least /usr/src is easily replaced. Might be worth just deleting= =20 > all that, though of course you need a read-write mount first .. perhaps > after booting from a memstick or live CD? Which is still risky, assuming that the file system has not been marked clean. > You might also check (before and after deleting anything) that /usr=20 > isn't running short of inodes (df -hi)? Good suggestion. > Just stabbing in the dark .. scrambled filesystems are the pits! And a good occassion to read more about UFS (McKusick et al.) - to develop a better understanding of what's happening. :-) --=20 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?20160210102236.19f9c68c.freebsd>