On Fri, Jan 27, 2012 at 09:30:46PM +1100, Joel Sing wrote:
> From bioctl(8):
>
> CAVEATS
> Use of the CRYPTO & RAID 4/5 disciplines are currently considered
> experimental.
>
> (I probably should remove CRYPTO from that list though, since it is now
> pretty
> stable :)
Yeah, I apologize. There was this, too, on softraid(4), which I totally
failed to read:
The RAID 4 and 5 disciplines do not initialize the parity upon
creation. This is due to the scrub functionality not being currently
implemented.
Had I noted that, I doubt I would have even tried :-)
> That particular trace suggests that your file system is hosed. However, RAID
> 5
> is not ready for prime-time yet - as far as I know it will work correctly
> until you lose a disk, at which point it will support read-only access (e.g.
> you should be able to keep your data), however any attempts to write will
> result in a panic. Also, there is no support for scrubbing or rebuilding,
> which makes it non-ideal for production.
Ah, that does mirror an experience I had once testing. Writing was
indeed what threw it off. Still, yeah, that is not particularly ideal
for my situation--the important data is always going to be backed up
somewhere, but it's the system itself I'd like to preserve so I can
avoid having to rebuild.
Thanks for the reply.
