From: Stef van der Made <svdmade@planet.nl>
To: wrlk@riede.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: The survival of ide-scsi in 2.6.x
Date: Sun, 28 Dec 2003 22:45:22 +0100 [thread overview]
Message-ID: <3FEF4EF2.4080303@planet.nl> (raw)
In-Reply-To: <20031227131724.GG1277@linnie.riede.org>
Hi Willem,
The standard stuff like mt -f /dev/ht0 status etc etc works. But tar
doesn't wan't to-do backups anymore both with and witout the patch on a
2.6.0 kernel. I don't have a 2.4.x kernel handy to test if it still
works with those kernels and my drive.
What I've done is the following:
bash-2.05# tar -cvb 64 -f /dev/ht0 /
tar: Removing leading `/' from absolute path names in the archive
lost+found/
usr/
usr/X11
usr/adm
usr/bin/
usr/bin/w
usr/bin/ar
tar: Cannot write to /dev/ht0: Invalid argument
tar: Error is not recoverable: exiting now
It looks as if the backup starts but it almost immediatly ends after the
drive does some spinning and reading and or writing.
Cheers
Stef
Willem Riede wrote:
>On 2003.12.27 07:43, Stef van der Made wrote:
>
>
>>Willem Riede wrote:
>>
>>snip
>>
>>
>>
>>>(By the way, ide-tape contains code for the ATAPI version, the
>>>DI-30, but that code is old and has serveral known problems -
>>>I'd like to see it removed - or at least deprecated - I will do
>>>that myself later if people want me to.)
>>>
>>>
>>>
>>snip
>>
>>After some fixing on ide-scsi my DI-30 is now working fine. I don't know
>>of any bugs in it. All works fine for me.
>>
>>
>
>If your system ever loses an interrupt form the DI-30 you'll find out :-)
>
>
>
>> Getting rid if ide-scsi might
>>be a good idea but it ain't going to be easy as a lot of programs are
>>using the code.
>>
>>
>
>I was actually trying to save ide-scsi, as we need it for the DI-30 + osst.
>
>
>
>> If you need a tester for the di-30 please feed me the patches and I'll
>>play around with them.
>>
>>
>
>Well, you could try the patch in the oiginal mail, and there is a new
>version of osst on osst.sourceforge.net that you could test.
>
>Thnaks, Willem Riede.
>
>
>
next prev parent reply other threads:[~2003-12-28 21:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-26 18:12 Willem Riede
2003-12-27 2:09 ` Wakko Warner
2003-12-27 12:43 ` Stef van der Made
[not found] ` <20031227131724.GG1277@linnie.riede.org>
2003-12-28 21:45 ` Stef van der Made [this message]
2004-01-03 14:11 ` Bill Davidsen
2004-01-03 14:18 ` Bill Davidsen
[not found] <mailman.1072462764.22951.linux-kernel2news@redhat.com>
2003-12-29 4:57 ` Pete Zaitcev
2003-12-29 13:07 ` Willem Riede
2003-12-30 18:44 James Bottomley
2003-12-30 22:18 ` Willem Riede
2004-01-03 19:08 ` Jens Axboe
2004-01-28 13:24 ` Willem Riede
2004-01-30 22:56 ` Bartlomiej Zolnierkiewicz
2004-01-31 0:48 ` Willem Riede
2004-01-05 22:00 Mikael Pettersson
2004-01-07 22:22 ` bill davidsen
2004-01-05 22:01 Mikael Pettersson
2004-01-05 22:33 ` Bartlomiej Zolnierkiewicz
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=3FEF4EF2.4080303@planet.nl \
--to=svdmade@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=wrlk@riede.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
Powered by JetHome