[7795] in linux-scsi channel archive
Re: Going from 2.0.34 to 2.2.x Optical Jukebox drive - 2.2.x gets con
daemon@ATHENA.MIT.EDU (Alan Cox)
Mon Jan 3 11:32:02 2000
To: dbeitler@ndcwireless.com (Beitler, David)
Date: Mon, 3 Jan 2000 16:25:08 +0000 (GMT)
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <D093B780D598D311813E00608C14D345337E93@NDC_EXCHANGE1> from "Beitler, David" at Jan 03, 2000 08:20:02 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E125AIA-0001Zd-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> There is a regular scsi hard drive that was also formatted with 2.0.34,
> which 2.2.x has no problems with whatsoever, so whatever the problem is, it
> is isolated to the optical drive.
>
> Any hints?
Optical vendors under DOS scale the partition tables by the block size for
2K media. There isnt a clear spec on 1K media. Seeing the values apparently
doubled would probably by explained by this. In wich case you can tweak
the partition code to be back compatible.
I know 2K media is scaled, 512 byte media is not. Does anyone have an official
reference on 1K media ?
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
