[4884] in linux-scsi channel archive
Re: 2K sectors
daemon@ATHENA.MIT.EDU (Eric Youngdale)
Wed Oct 14 08:08:40 1998
Date: Wed, 14 Oct 1998 00:36:10 -0400 (EDT)
From: Eric Youngdale <eric@andante.jic.com>
To: Harvey Fishman <fishman@panix.com>
cc: William Brioschi <capo@writeme.com>,
Linux SCSI mailing list <linux-scsi@vger.rutgers.edu>
In-Reply-To: <Pine.GSU.4.03.9810131109560.14915-100000@panix3.panix.com>
On Tue, 13 Oct 1998, Harvey Fishman wrote:
> On Mon, 12 Oct 1998, Eric Youngdale wrote:
> explicitly do the mapping. As an aside, NT seems to have that code builtin
> as I have no trouble with either FAT or NTFS (which also depends upon a 512
> byte logical allocation unit) file systems there. I think that I did once
> try the Linux NTFS driver with a 640 MB disk written under NT and as I
> fuzzily remember it did not work, but the memories are not at all clear.
My gut feel is that it should be the filesystem's responsibility
to deal with this crap. Currently the SCSI cdrom driver deals with 1K
blocks, for what is inherently a 2k sectorsize (mainly because when this
was written the buffer cache didn't support anything other than 1K
sectors). I would like to discard this code in the near future, since
the reasons for it to exist have long ceased to exist.
> > > 3) use the device in raw, sequential mode (through tar or something like that),
> > > probably using the SCSI generic driver; I haven't tried this yet, is it
> > > possible? should I do something particular or can I simply do a
> > > "tar cf /dev/sga"?
> >
> > This absolutely won't work. The generics driver simply doesn't
> > work like this.
>
> Perhaps I do not understand what you are saying but I have never had any
> real trouble using tar to write directly to the disk without a file system.
I meant using the generics driver (/dev/sg?). Using /dev/sd?
should work fine.
-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
