Um, no. That's not normal at all, y0ha. There's something funny going on here: basically, when it tries to flush the journal cache, it looks like it's failing (or giving some kind of weird error).
On the last response: we're using standard low-level calls, not cp. In other words, we don't ever access hardware directly: we're using the OS to do it, so if there are hardware changes/problems, we're isolated from them.
__________________
--Dave Nanian
|