Date: Wed, 18 Apr 2007 19:09:57 -0500 From: CyberLeo Kitsana <cyberleo@cyberleo.net> To: Roland Smith <rsmith@xs4all.nl>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: dump/restore corrupted filesystems Message-ID: <4626B36C.5030506@cyberleo.net> In-Reply-To: <20070418213717.GB74368@slackbox.xs4all.nl> References: <4623843B.40006@cyberleo.net> <20070416170825.GA91459@slackbox.xs4all.nl> <462449C2.9000302@cyberleo.net> <20070416222437.GA1924@slackbox.xs4all.nl> <46268919.1080301@cyberleo.net> <20070418213717.GB74368@slackbox.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Roland Smith wrote: >> --8<-- >> ** Phase 2 - Check Pathnames >> DIRECTORY CORRUPTED I=93409222 OWNER=1002 MODE=40755 >> SIZE=512 MTIME=Feb 10 00:49 2007 >> DIR=? >> >> UNEXPECTED SOFT UPDATE INCONSISTENCY > > Did these problems start after a crash? It's possible, but I cannot be absolutely certain. The machine is supposed to start itself up and shut itself down every day, running a total of about 4 hours a day, during the span when all other machines dump their backups. The only reason I noticed this failure was because it didn't power down one day. Investigation revealed that FSCK had failed and dropped to single user, with errors seen in the log. > >> SALVAGE? no > > What happens if you tell it to try and salvage? This was a dry-run to get the error log. When I actually tried to repair the filesystem, fsck aborts shortly after, complaining that it cannot fix the filesystem, and cannot continue. Hence the current path of removing everything and re-newfs'ing. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net <CyberLeo@CyberLeo.Net> Furry Peace! - http://www.fur.com/peace/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4626B36C.5030506>