Andrew Morton wrote:
Kernel Version: tested 2.6.17 through 2.6.29 with various resultsI assume that means 2.6.17 and 2.6.19 failed.
I tested it with 2.6.17 through 2.6.19 including subversions (like 2.6.17.3 and such). I found that 2.6.19 works and also found two other version in the line that work. The other about 4-5 version that I have tried, did not work. The works/not works is not consistent as I found 2.6.17.x kernel that did work and 2.6.18 that did not.
If the problem is known, I'd also like to know what the problem was as I need to recover two tapes that are inaccessible now. (LTO3 400GB tapes so there was no time to erase all data even if something near the beginning of the tape is bad).
Status: NEW Severity: blocking Owner: [EMAIL PROTECTED] Submitter: [EMAIL PROTECTED] Most recent kernel where this bug did *NOT* occur: 2.6.19And that means that 2.6.19 did not fail.
Right now I'm using 2.6.19 and it works. Haven't tried it with 2.6.19.1 yet though.
- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
