maximum entropy writes:
> 
> I've recently started experimenting with a RAIDframe configuration on
> a sparc.  I had to power cycle the box, and when it came back up it
> complained:
> 
> /dev/raid0c: Parity status: DIRTY
> /dev/raid0c: Initiating re-write of parity
> [...]
> Automatic boot in progress: starting file system checks.
> /dev/rsd0a: file system is clean; not checking
> /dev/rsd0g: file system is clean; not checking
> /dev/rraid0c: 1 files, 1 used, 6030095 free (7 frags, 753761 blocks, 0.0% fra
> gmentation)
> /dev/rraid0c: MARKING FILE SYSTEM CLEAN
> [...]
> Mounting all filesystems...
> mount_ffs: /dev/raid0c on /export: Device busy
> [...]
> Starting mountd.
> Dec 20 22:19:06 sparky mountd[147]: "/export -alldirs -maproot", line 3: Coul
> d not remount /export: Invalid argument
> 
> Is this really the expected behavior?  I would have expected that if
> the disk can be fscked, it can also be mounted.

The trick here is that raidctl is rebuilding raid0, and will still have 
/dev/raid0c open, waiting for the rebuild to complete...  One doesn't see 
this problem if a non-'entire disk' partition is used for mountable partitions. 

Later...

Greg Oster