From: Giuliano Pochini <pochini@denise.shiny.it>
To: John William <jw2357@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2048 byte/sector problems with kernel 2.4
Date: Wed, 04 Apr 2001 21:39:47 +0200 [thread overview]
Message-ID: <3ACB7883.3DEBAD6A@denise.shiny.it> (raw)
In-Reply-To: <F38vnbEG10Gai4omRXf000005a9@hotmail.com>
> >There WERE direct overwrite media for a while that would, in theory, be
> >able to write the data directly, but a combination of high cost, >limited
> >sources, and strong questions about the permanence of the recorded data
> >severely limited the demand for these and I think that they have been
> >withdrawn.
I have 2 OW disks and they work just fine. According to specs their
reliability is the same as nornal MO disks.
> No, direct overwrite disks are expensive, but they are still available. I do
> not know of any, and have not heard of any problems related to direct
> overwrite technology. For some reason M/O never really caught on in the US,
> and the high price of direct overwrite disks is what seems to be killing
> them off. I have a bunch I use for backup and have never had any problems.
RW CDs killed almost all removables.
And about 2KB sectors related problems, I confirm what I wrote in my previous
message: I have no problems. 640MB and 1.3GB both work fine here.
(kernel 2.4.3, old aic7xxx driver, adaptec 2930CU, Fujitsu GigaMO, PowerPC
750)
Bye.
next prev parent reply other threads:[~2001-04-04 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 4:37 2048 byte/sector problems with kernel 2.4 John William
2001-04-04 19:39 ` Giuliano Pochini [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-03 21:34 Jurgen Kramer
2001-04-03 21:58 ` Alan Cox
2001-04-03 22:48 ` Harvey Fishman
2001-04-04 9:24 ` Giuliano Pochini
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=3ACB7883.3DEBAD6A@denise.shiny.it \
--to=pochini@denise.shiny.it \
--cc=jw2357@hotmail.com \
--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 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.