Date: Mon, 25 Mar 1996 12:25:38 +0000 (GMT) From: Adam David <adam@veda.is> To: hsu@clinet.fi (Heikki Suonsivu) Cc: freebsd-current@freebsd.org Subject: Re: async mounts, etc. Message-ID: <199603251225.MAA02695@veda.is> In-Reply-To: <199603250430.GAA21047@cantina.clinet.fi> from Heikki Suonsivu at "Mar 25, 96 06:30:08 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> From: Adam David <adam@veda.is>
> it seems that some limit was exceeded and it panicked on average twice an hour
> with "bad dir". It did not help to let fsck exercise the disk - I mean that
> repair to the filesystem claimed to be successful but there were further panics.
>
> Run fsck several times in row, running once may not be enough. If you run
> into directories which are "corrupted" and fsck keeps cleaning and
> salvaging them endlessly, clri the offending directory and salvage the
> files from lost+found.
>
> The "endless fsck" problem is not specific to async mouts, but async mounts
> naturally increase the amount of damage.
>
> --
> Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi
> mobile +358-40-5519679 work +358-0-4375360 fax -4555276 home -8031121
>
The second run through fsck showed no further damage, and later "bad dir"
panics involved directories that were not part of the previous damage.
Something is broken, whether from a race condition or some other kind of
size/load limit.
--
Adam David <adam@veda.is>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603251225.MAA02695>