Subject: Re: RAIDframe: why are only "root" raidsets closed on reboot/halt?
To: Greg Oster <oster@cs.usask.ca>
From: Greywolf <greywolf@starwolf.com>
List: tech-kern
Date: 11/26/2002 09:19:56
On Tue, 26 Nov 2002, Greg Oster wrote:

# > syncing disks... done
# > Closing vnode for row: 0 col: 0
# > Closing vnode for row: 0 col: 1
# > rebooting...
# >
# > I never see any of the other sets give the "Closing vnode for row"
# > message.  Perhaps the closing of the vnode for the components has
# > nothign to do with the fact that parity stays clean or not?  I must
# > admit I have not delved too deeply into the source yet.
#
# I've taken out that message for -current, but in 1.6 (and before) you should
# see those messages for every RAID set.  If you don't, then that means they
# didn't get unconfigured, and that means that the parity status will not have
# been updated in the component labels.

Could you add an option for those?  Yes, I know, heaven knows we need
more options like we need holes in our bodies, but it would be nice to
see things like that.

<wish>
OSx on the Pyramid had a neat feature that I really liked.  When the
machine went down for a reboot or a halt, the kernel would print:

FYI:  Marking the following filesystems CLEAN:

	/dev/ipd00e (/var) /dev/ipd00f (/usr) /dev/ipd00h (/home)

Marking the following filesystems DIRTY:

	/dev/ipd00a (/)

[of course, root gets cleanly umounted, usually...]

				--*greywolf;
--
NetBSD: priapic OS