Date: Thu, 03 Mar 2005 00:22:41 +0100 From: "Julian Stacey" <jhs@berklix.org> To: freebsd-fs@freebsd.org Subject: Re: A bad lost+found causes fsck of FFS to repeatefly fail. Message-ID: <200503022322.j22NMfdD031805@fire.jhs.private> In-Reply-To: Your message of "Wed, 02 Mar 2005 00:46:39 %2B0100." <200503012346.j21NkdrU002367@fire.jhs.private>
next in thread | previous in thread | raw e-mail | index | archive | help
I wrote about 24 hours ago: > I had a FFS error that fsck couldnt fix, & I've seen similar before: > If content of lost+found/ is itself damaged, fsck fails, it seems. > Then one has to manually [copy elsewhere] & rm -rf lost+found then re-fsck. > Should the above be added to man fsck, or > content below submitted as a send-pr ? Or do readers here > include FFS / FSCK maintainers ? > > Log & environ follow: > > uname -a > FreeBSD fire.jhs.private 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sat > Feb 26 21:47:28 CET 2005 > jhs@fire.jhs.private:/usr1/src/sys/amd64/compile/FIRE64.small amd64 Same scenario a day later on another of my hosts ! This one is not a 64bit amd just a normal 686, FreeBSD film.jhs.private 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 & its a 33 Gig instead of 40 Gig partition. Other than that, same story. - Julian Stacey Net & Sys Eng Consultant, Munich http://berklix.com Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503022322.j22NMfdD031805>