From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org, "John L. Males" <jlmales@softhome.net>
Subject: Re: Problems with SCSI tape rewind / verify on 2.4.29
Date: Wed, 2 Mar 2005 11:34:41 -0300 [thread overview]
Message-ID: <20050302143440.GA2543@logos.cnet> (raw)
In-Reply-To: <200503021208.51480.gene.heskett@verizon.net>
n Wed, Mar 02, 2005 at 12:08:51PM -0500, Gene Heskett wrote:
> On Wednesday 02 March 2005 07:03, Marcelo Tosatti wrote:
> >On Wed, Mar 02, 2005 at 11:15:42AM -0000, Mark Yeatman wrote:
> >> Hi
> >>
> >> Never had to log a bug before, hope this is correctly done.
> >>
> >> Thanks
> >>
> >> Mark
> >>
> >> Detail....
> >>
> >> [1.] One line summary of the problem:
> >> SCSI tape drive is refusing to rewind after backup to allow verify
> >> and causing illegal seek error
> >>
> >> [2.] Full description of the problem/report:
> >> On backup the tape drive is reporting the following error and
> >> failing it's backups.
> >>
> >> tar: /dev/st0: Warning: Cannot seek: Illegal seek
> >>
> >> I have traced this back to failing at an upgrade of the kernel to
> >> 2.4.29 on Feb 8th. The backups have not worked since. Replacement
> >> Drives have been tried and cables to no avail. I noticed in the
> >> the changelog that a patch by Solar Designer to the Scsi tape
> >> return code had been made.
> >
> >v2.6 also contains the same problem BTW.
> >
> >Try this:
> >
> >--- a/drivers/scsi/st.c.orig 2005-03-02 09:02:13.637158144 -0300
> >+++ b/drivers/scsi/st.c 2005-03-02 09:02:20.208159200 -0300
> >@@ -3778,7 +3778,6 @@
> > read: st_read,
> > write: st_write,
> > ioctl: st_ioctl,
> >- llseek: no_llseek,
> > open: st_open,
> > flush: st_flush,
> > release: st_release,
> >-
>
> Interesting Marcelo. How long has this been true in 2.6?
Actually I just checked and it seems v2.6 is not using "no_llseek".
However John L. Males reports the same problem with v2.6 - John, care
to retest with v2.6.10 ?
> I thought I had an amanda problem, and eventually went to virtual
> tapes on disk, largely because of this. However, I have to say it is
> working better than tapes ever did here. Unforch, that 200GB disk is
> certainly a single point of failure I don't relish thinking about...
:)
next prev parent reply other threads:[~2005-03-02 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 11:15 Problems with SCSI tape rewind / verify on 2.4.29 Mark Yeatman
2005-03-02 12:03 ` Marcelo Tosatti
2005-03-02 17:08 ` Gene Heskett
2005-03-02 14:34 ` Marcelo Tosatti [this message]
2005-03-02 20:46 ` Re[03]: " John L. Males
2005-03-02 21:15 ` John L. Males
2005-03-02 21:26 ` John L. Males
2005-03-02 21:17 ` Kai Makisara
2005-03-02 16:59 ` Marcelo Tosatti
2005-03-02 22:15 ` Kai Makisara
2005-03-02 21:25 ` Andrew Morton
2005-03-02 21:44 ` Andreas Steinmetz
2005-03-02 22:01 ` Kai Makisara
2005-03-02 22:17 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2005-03-02 16:50 Mark Yeatman
2005-03-02 22:25 John L. Males
2005-03-02 23:51 John L. Males
2005-03-03 8:29 Mark Yeatman
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=20050302143440.GA2543@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=gene.heskett@verizon.net \
--cc=jlmales@softhome.net \
--cc=linux-kernel@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