[7816] in linux-scsi channel archive
RE: Going from 2.0.34 to 2.2.x Optical Jukebox drive - 2.2.x gets
daemon@ATHENA.MIT.EDU (Beitler, David)
Wed Jan 12 09:29:58 2000
Message-ID: <D093B780D598D311813E00608C14D345337EB2@NDC_EXCHANGE1>
From: "Beitler, David" <dbeitler@ndcwireless.com>
To: linux-scsi@vger.rutgers.edu
Date: Tue, 11 Jan 2000 16:15:25 -0800
MIME-Version: 1.0
Content-Type: text/plain
So, any understanding why this worked in 2.0.34? I was hoping there was
something simple I could do, like pass it some parameters when making the
file system,or mounting it??
David
> -----Original Message-----
> From: Alan Cox [SMTP:alan@lxorguk.ukuu.org.uk]
> Sent: Monday, January 03, 2000 8:25 AM
> To: dbeitler@ndcwireless.com
> Cc: linux-scsi@vger.rutgers.edu
> Subject: Re: Going from 2.0.34 to 2.2.x Optical Jukebox drive - 2.2.x
> gets con
>
> > 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
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
