secmgr wrote:
No, I mean self corrupting raid5 sets during initialization. DiscussedIn the following message you seemed to claim that adding 64 sectors of slack to the
about 2-3 weeks ago.
beginning of the vinum partition fixed this problem, as I suggested. Did that fix it or not?
The reason is empirically derived. When I created a 7 disk raid 5 set using "len 0" or all the space available, the raid set would be corrupt after initializing. Every time. When I reserved back that extra space, no corruption.
(freebsd 4.10-p3) There was a thread on this a few days ago.
jim
Joe Koberg joe at osoft dot us
_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
