From: "John W. Linville" <linville@tuxdriver.com>
To: Kai.Makisara@kolumbus.fi
Cc: linux-scsi@vger.kernel.org, Fabien.Collin@cern.ch,
Jean-Philippe.Baud@cern.ch
Subject: [patch 2.6.12 1/1] st: support ANSI end-of-volume processing
Date: Mon, 27 Jun 2005 15:15:32 -0400 [thread overview]
Message-ID: <20050627191531.GC17260@tuxdriver.com> (raw)
The ANSI labelled tape standard specifies that the EOD on tape must be
preceeded by a trailer label. If during writing your application hits
LEOT (Logical End Of Tape), it must be able to write the trailer label.
However with the default tape driver (st), you cannot write anything
after the LEOT. So the patch clears the error condition so that the
application can write the trailer label (there is some space available
on tape media between LEOT and PEOT=Physical End Of Tape).
Signed-off-by: Fabien Collin <Fabien.Collin@cern.ch>
Signed-off-by: Jean-Philippe Baud <Jean-Philippe.Baud@cern.ch>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
---
Original patch by Fabien Collin. Description above by Jean-Philippe
Baud. Patch monkeying by me... Honestly, I don't know a lot about
this patch. But, I am told it "works"... If you have questions
regarding this, send them to me and I'll get an answer for you.
drivers/scsi/st.c | 1 +
1 files changed, 1 insertion(+)
diff --git a/drivers/scsi/st.c b/drivers/scsi/st.c
--- a/drivers/scsi/st.c
+++ b/drivers/scsi/st.c
@@ -3440,6 +3440,7 @@ static int st_ioctl(struct inode *inode,
}
STp->recover_reg = 0; /* Clear after read */
+ STps->eof = ST_NOEOF;
retval = 0;
goto out;
} /* End of MTIOCGET */
--
John W. Linville
linville@tuxdriver.com
next reply other threads:[~2005-06-27 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 19:15 John W. Linville [this message]
2005-06-27 19:43 ` [patch 2.6.12 1/1] st: support ANSI end-of-volume processing 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=20050627191531.GC17260@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Fabien.Collin@cern.ch \
--cc=Jean-Philippe.Baud@cern.ch \
--cc=Kai.Makisara@kolumbus.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.