>In this case it threw up another problem for me though. You also changed
>the ext2 code for those devices between 2.2.0 and 2.2.5, right?
>When I did the copy-reformat-copyback thing under 2.2.0
>(/dev/sdc1->harddisk->/dev/sdc) and then tried to access the MO under
>2.2.5, it *mostly* worked, but one copy op gave me an error. I checked the
>media with e2fsck - and it found tons of errors. I could repair most, but
>some data was lost before I recovered from the first surprise. I then dis
>the copy-reformat-copyback again -copying everything to the harddisk under
>2.2.0 and formatting/copying things back under 2.2.5
>Now it works. 't was a nasty pitfall though.
UPDATE: It does *NOT* work. I did an e2fsck -B 2048 -f -n /dev/sdc
immediately after copying the files and it gave me no errors. One reboot
later I copied two files to one of the "regenerated" MOs (that worked) and
tried to create a new directory on it. That failed. Another e2fsck run
yielded quite some errors. Looks like the previous case. 2.2.0 can read the
disk slightly better than 2.2.5, though there are still corrupt dir entries
and such.
I'm not gonna touch that /§(/$(%/ MO thingy again until you give me a big
fat "IT'S FIXED".
Christian
--Drive A: not responding...Formatting C: instead
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/