On Thu, Jul 07, 2005 at 03:02:52PM +0600, [EMAIL PROTECTED] said:
> Hi.
>
> Since "raidctl -P all" in /etc/rc parity is verified/reconstructed
> _before_ system runs. This lead to bad effect for me, while I have
> "root on RAID", as described in http://www.nomoa.com/bsd/raid_ide.htm
> - when machine has lost power, before mounting there are parity
> checks. This is so long with my more that 150G on RAID.
>
> I want ask, what will occur if not do "raidctl -P all" in /etc/rc,
> but set it in /etc/rc.local, after daemons started?
> What can fsck with such "uncleaned/unreconstructed" RAID?
if your parity isn't clean, you don't HAVE a filesystem to write to, so
there's no point in mounting it until parity is clean. See raid(4) for more
on why this is important. with root on raid, you're basically out of luck -
you have no choice but to wait.
If (as in my case), the RAID filesystem is only used for data storage (not
for the OS), you can run raidctl -P all in background and have your RAID
filesystem set "noauto" in /etc/fstab. If there's been a crash, you will
presumably know about it, and can manually mount the filesystem later after
parity is fixed. I posted about this a few days ago; check the archives.
(as I said earlier, my method may turn out to be a Bad Idea for some reason
that hasn't occurred to me yet; if this is the case, I'd appreciate a
heads-up. Thanks.)
--
Scott Francis | darkuncle(at)darkuncle(dot)net | 0x5537F527
Less and less is done
until non-action is achieved
when nothing is done, nothing is left undone.
-- the Tao of Sysadmin
[demime 1.01d removed an attachment of type application/pgp-signature]
