2.9test9-mm1 and DAO ATAPI cd-burning corrupt
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
On Tue, 11 Nov 2003 06:50:07 +0100, you wrote in linux.kernel:
Quoted 2 lines
As per the MO device that wants ide-scsi, send out patches to the kernel mailing list, and maybe the person can test it. I certainly can't test it.
Well, that person is me and I tried making it work with ide-cd. Got read support to work, submitted to Jens, you have it in your kernel. No luck with write support. I could get it to mount read-write and data actually made it to disk, but umount lead to a BUG_ON. Details in:
http://www.ussg.iu.edu/hypermail/linux/kernel/0305.0/1307.html
(the patch in there won't apply due to minor renaming of flags and the fact that the read support part is already in your tree)
So I'm not only complaining. ;)
Signature · 2 lines
Ciao, Pascal
Quoted 5 lines · Pascal Schmidt
Well, that person is me and I tried making it work with ide-cd. Got read support to work, submitted to Jens, you have it in your kernel. No luck with write support. I could get it to mount read-write and data actually made it to disk, but umount lead to a
BUG_ON.
Hmm.. That looks "impossible", so it's most likely a serious bh corruption issue. But what corrupts it is hard to guess at - the actual trace to that point has nothing to do with the MO drive itself, so you've either hit a generic ext2 bug (hey, it's possible, I guess, but sounds very unlikely), or the ide-scsi driver has corrupted memory.
The latter is obviously the more likely schenario, but it does require somebody with the MO device to actually try to figure out how the corruption occurs.. Probably with a big printk buffer and a lot of printk's..
Linus