From owner-freebsd-questions@freebsd.org Wed Feb 10 09:22:47 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05C3FAA41E4 for ; Wed, 10 Feb 2016 09:22:47 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C17A612B8 for ; Wed, 10 Feb 2016 09:22:46 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-44-23.dynamic.qsc.de [92.195.44.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 72E1F27650; Wed, 10 Feb 2016 10:22:37 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u1A9MakT005341; Wed, 10 Feb 2016 10:22:37 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Wed, 10 Feb 2016 10:22:36 +0100 From: Polytropon To: Ian Smith Cc: Paul Beard , 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: <20160210160149.V51785@sola.nimnet.asn.au> <20160210195431.V51785@sola.nimnet.asn.au> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Feb 2016 09:22:47 -0000 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 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, ...