On Jun 19, 14:55, Peter Simons wrote:
> Subject: fsck doesn't work at boot time
>
> Hi,
>
> I have recently installed NetBSD 1.2.1 on a Pentium machine with IDE
> hard disk. So far everything works fine except for this:
>
>  | [date] peti /netbsd: /dev/wd0a: file system not clean; please fsck(8)
>
> Unfortunately not all messages printed on the console appear in the
> kernel.debug log, but it looks like this: fsck is starting up. Then it
> tells me that the wd0a drive would be marked clean. All other
> partitions aren't checked at all, because they are marked clean
> already. And then it prints the message above, which I think is
> slightly confusing, because it told me that it had marked the file
> system as 'clean' only a second earlier.
>
> I have various other installed machines with NetBSD 1.2 and never had
> this problem before.

IIRC NetBSD 1.2 does not use the clean mark.

> Any ideas what this might be?

At boot time, fsck -p checks the raw devices (/dev/rwd0a in this case)
and mark it clean, but mount -a later tries to mount block devices
(/dev/wd0a) and svears about block device not being marked clean. Mount
will not complain if you do fsck /dev/wd0a by hand and then remount it.

Perhaps could be fsck changed to mark clean both raw and block device?
Or is there some deeper reason for this behavior?

						cerno

--
Martin Cernohorsky
Institute of Computer Science
Masaryk University, Brno, Czech Republic
cerno@ics.muni.cz

* .sig 1.2a * The world is comming to an end. Please log out.