https://bugzilla.kernel.org/show_bug.cgi?id=15579 --- Comment #8 from Andreas Beckmann <kernel-bugs@xxxxxxxxxxxx> 2010-03-29 08:16:54 --- (In reply to comment #7) > If the number of available unmapped blocks has an impact, that seems most > likely to be a SSD firmware bug to me. > > ie. If the linux kernel is sending control messages in the wrong order, then it > should cause corruption regardless of the number of unmapped blocks. That's correct except that you may get a timing issue (e.g. writing to free unmapped blocks is/could be/should be a bit faster than clearing the blocks first) which could turn this into race condition debugging ... -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
