From: Bgs <bgs@bgs.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-scsi@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
Kai Makisara <Kai.Makisara@kolumbus.fi>
Subject: Re: [Bugme-new] [Bug 7717] New: Tapes unreadable after unload
Date: Wed, 20 Dec 2006 13:55:33 +0100 [thread overview]
Message-ID: <458932C5.4000807@bgs.hu> (raw)
In-Reply-To: <20061220025058.70d3d4ea.akpm@osdl.org>
Andrew Morton wrote:
>> Kernel Version: tested 2.6.17 through 2.6.29 with various results
>
> I 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: io_scsi@kernel-bugs.osdl.org
>> Submitter: bgs@bgs.hu
>>
>>
>> Most recent kernel where this bug did *NOT* occur: 2.6.19
>
> And 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.
next prev parent reply other threads:[~2006-12-20 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200612201031.kBKAVIJS005240@fire-2.osdl.org>
2006-12-20 10:50 ` [Bugme-new] [Bug 7717] New: Tapes unreadable after unload Andrew Morton
2006-12-20 12:55 ` Bgs [this message]
2006-12-20 20:41 ` Kai Makisara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=458932C5.4000807@bgs.hu \
--to=bgs@bgs.hu \
--cc=Kai.Makisara@kolumbus.fi \
--cc=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox