Brian A. Seklecki wrote:
This is the expected behavior for a failure on a CCD component. Try
In this case, is there a difference between expected and desired
behavior?
cutting the SATA cable to a live system some time; watch the kernel
panic there as well. Suddenly it cant stat() / or read/write from swap.
Maybe this should be mentioned in the FAQ.
(I expected it to run with one device and attract the admins/roots
attention in a another way. In my case, the only way to recover was a
hard reset.)
You're playing with fire with CCD anyway: RAID0. The stuff in 4.1
wasn't touched for months...6, 10, 11, 11, look at the time between
commits. There's some new recent activity.
Things that old don't have to be bad..? At least I thought/was told so.
Try RAIDFrame w/ raid0 for a little-more-active development.
I considered raid frame, too, but didn't want to build a new kernel.
But I'll give it a shot. Thank you.
~BAS
Marius
