In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>>> Have you rebuilt your fsck after the last commit ?
>>
>>It turns out fsck was last built on Tuesday morning. I just
>>rebuilt/reinstalled it and everything appears peachy again.
>
>I suppose current fsck's don't work with old kernels. This
>
>> Have you rebuilt your fsck after the last commit ?
>
>It turns out fsck was last built on Tuesday morning. I just
>rebuilt/reinstalled it and everything appears peachy again.
I suppose current fsck's don't work with old kernels. This
is more annoying than ps not working.
Bruce
To Unsubscri
Current from when? I remember having to reboot after a crash first
before the filesystem was accepted as clean. but that is gone. And I
have crashed a CURRENT machine fairly often lately.
Nick
On Thu, 22 Jul 1999, Jos Backus wrote:
> After booting single-user after a crash:
>
> # mount
>
On Thu, Jul 22, 1999 at 11:21:45AM +0200, Poul-Henning Kamp wrote:
> Have you rebuilt your fsck after the last commit ?
It turns out fsck was last built on Tuesday morning. I just
rebuilt/reinstalled it and everything appears peachy again.
fsck had not been updated yesterday because the make wor
Have you rebuilt your fsck after the last commit ?
In message <[EMAIL PROTECTED]>, Jos Backus writes:
>After booting single-user after a crash:
>
># mount
>wd0s1a on / (local, read-only)
># fsck -p
>/dev/rwd0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS
>/dev/rwd0s1a: clean, 12881 free (409 frags, 1559
