Hi, engineer. > Hmm... I done this trisk, but it's not works ;). I add > CHECK=`raidctl -s raid1 | grep '/dev/wd1e: optimal'` > if [ -n "$CHECK" ]; then > raidctl -f /dev/wd1e raid1 > fi > # Check parity on raid devices. > raidctl -P all > into /etc/rc on /dev/wd0a (where live system exist and kernel booting > from).
Ok, I think this is because raid's with "raidctl -A yes". Thinking about parity checks I'm come to idea that same trick's is bad idea. When I fail component and then reconstruct it I just lose some information which may do things better after parity rebuilding, before fsck start checking partitions. Isn't it? I think my trick is a product of misunderstanding. Sorry about flame. It must be better not autoconfigure radi1 but mount -ro some backup copy (from NFS for example) and then configure raid, re-parity, fsck. But here I not understand. How then I can mount that raid partitions while httpd already start and sit to his "chroot" on /var/www mounted from NFS? I don't have practice with such things. It must be not possible to mount raid's partition above already mounted and used NFS's? -- engineer
