Nice, that might be useful to know. Thank you. (It is, of course, in the nature of "e2fsck -c" to be persistent (unlike "cp" and "dd" which would simply fail). It seemed as if there was a larger cluster of bad blocks, originally, AFAICT. I wonder whether the occurrence would've been different had there only been a single bad block, i.e. would "e2fsck -c" have been able to glide over it more nicely and continue the check. If I find myself unusually eager to find out, now I could even check it...)
-- e2fsck / linux kernel chokes on I/O errors https://bugs.launchpad.net/bugs/64914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
