> >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 be
> I recently acquired a 1.3GB MO drive. When I use small (230MB and 540MB)
>
> MO disks which have normal 512 bytes/sector it all works flawlessly but
> as soon
> as a put in a 1.3GB disk which uses the 2048 bytes/sector format it all
> goes
> wrong. As soon as I write something to the disk by is
On Tue, 3 Apr 2001, Harvey Fishman wrote:
>On Tue, 3 Apr 2001, Alan Cox wrote:
>
>> > I also tried it with 2.2.18 there it works but it seems to be >utterly
>> > slow. I'm using kernel 2.4.2(XFS version to be precise).
>>
>>M/O disks are slow. At a minimum make sure you are using a physical >bloc
On Tue, 3 Apr 2001, Alan Cox wrote:
> > I also tried it with 2.2.18 there it works but it seems to be utterly
> > slow. I'm using kernel 2.4.2(XFS version to be precise).
>
> M/O disks are slow. At a minimum make sure you are using a physical block size
> of 2048 bytes when using 2048 byte media
> MO disks which have normal 512 bytes/sector it all works flawlessly but
> as soon
> as a put in a 1.3GB disk which uses the 2048 bytes/sector format it all
> goes
> wrong. As soon as I write something to the disk by issuing a cp command
It will. Linux 2.4.x still hasn't had the scsi disk block
Hi,
I recently acquired a 1.3GB MO drive. When I use small (230MB and 540MB)
MO disks which have normal 512 bytes/sector it all works flawlessly but
as soon
as a put in a 1.3GB disk which uses the 2048 bytes/sector format it all
goes
wrong. As soon as I write something to the disk by issuing a c
6 matches
Mail list logo
