> this sounds like a bug in usb/disk. usb/disk should be > able to handle a sleeping drive without passing i/o > errors up.
That's probably a USB issue, yes. However, now, I've setup my drive not to go into sleep mode at all, but I see the following from earlier today: ... 89806 blocks queued for worm 0 falsehits next dump at ... next dump at ... wrenread: error on w0(1691022): %r 89805 blocks copied to worm where w0 is the disk itself. Note that the final message states 89805 blocks were copied, whereas initially 89806 blocks were queued - was the error on just this one block? If so, what could possibly be the reason? I doubt my USB drive would be acting up. Thanks, ak
