--J/dobhs11T7y2rNN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Fri, Dec 21, 2001 at 12:52:45AM -0500, maximum entropy wrote:
> 
> /dev/rraid0c: 1 files, 1 used, 6030095 free (7 frags, 753761 blocks, 0.0% fragmentation)
> /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: Could 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.

I've never NFS mounted a RAID device, so I can't give any advice here.

> If this is normal, is there any way to force the system to wait for
> the parity to be rebuilt before attempting to mount that partition?

You can apply the attached patch to /etc/rc.d/raidframe.  I've been running
this way on my machines for a long while now.

	Cheers,

	-- Johnny Lam <jlam@netbsd.org>

--J/dobhs11T7y2rNN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=diff

--- raidframe.orig	Fri Dec 21 02:10:55 2001
+++ raidframe
@@ -34,9 +34,9 @@
 			[ ! -f $cfg ] && continue
 			dev=${cfg##*/}
 			dev=${dev%%.conf}
-			raidctl -P $dev
+			raidctl -Pv $dev
 		done
-	) &
+	)
 }
 
 load_rc_config $name

--J/dobhs11T7y2rNN--