On Sat, Sep 30, 2000 at 12:14:56PM -0500, [EMAIL PROTECTED] wrote:
> I do appreciate the many responses I've received to my initial query. I'm
> glad that there *is* a solution that allows me read/write one hardsector,
> and I'll be implementing such in my EFI partition code after the weekend.
>
I do appreciate the many responses I've received to my initial query. I'm
glad that there *is* a solution that allows me read/write one hardsector,
and I'll be implementing such in my EFI partition code after the weekend.
As for the issue of understanding a drive's true capacity and capabilities
On Sat, 30 Sep 2000, Vojtech Pavlik wrote:
> That, again, is the IDE driver issue, not the FS layer's. If you want to
Nope it is a SCSI issues also.
If it was not Matt would not be asking the question.
I have more of a heads up on what he was wanting because I spoke with him
for about 45 min on
On Sat, Sep 30, 2000 at 11:16:47AM +0200, Vojtech Pavlik wrote:
> Really, there is no problem with Linux accessing some extra areas hidden
> by the BIOS (via the new IDE commands) or the firmware on Linux side.
I see that the topic changed.
First it was the difficulty to get at a partial block
a
On Sat, Sep 30, 2000 at 12:29:01AM +0100, Anton Altaparmakov wrote:
> What about the case that the partition was formatted by another OS though
> and that other OS put something on the last sector? (eg. copy of
> bootsector) Would that be accessible just by setting the block size to 512?
Yes.
On Sat, Sep 30, 2000 at 01:47:48AM -0700, Andre Hedrick wrote:
> On Sat, 30 Sep 2000, Alexander Viro wrote:
>
> > How about /dev/hda? If you are talking about absolute block addresses you
> > are way below the partitioning level.
>
> But are you beyond what the detected capacity of the drive?
T
On Sat, 30 Sep 2000, Alexander Viro wrote:
> How about /dev/hda? If you are talking about absolute block addresses you
> are way below the partitioning level.
But are you beyond what the detected capacity of the drive?
> > We are narrowing to point that appears to make zero sense, until you
> >
On Sat, 30 Sep 2000, Andre Hedrick wrote:
> Now how do you access beyond the limits of the FS/Partition?
How about /dev/hda? If you are talking about absolute block addresses you
are way below the partitioning level.
> We are narrowing to point that appears to make zero sense, until you
> rea
On Sat, 30 Sep 2000, Alexander Viro wrote:
> WTF does FS have to that? But anyway, the most trivial way is
> to have the driver set blk_size[major][minor] to sector size and do
>
> fd = open("your_device_name",O_RDONLY);
> lseek(fd, 25600, 0);
> read(fd, buf, 16384);
Thank yo
On Sat, 30 Sep 2000, Peter Samuelson wrote:
>
> I guess FS is FS like you said ... OEM is who labels the box on the
> shelf, and I guess MAN is manufacturer. I would have said "Mfr".
OEM == Dell, Gateway, Compaq, HP, etc ...
MAN == Fugitsu, IBM, Maxtor, Quantum, Seagate, Western Digital, etc .
On Sat, 30 Sep 2000, Andre Hedrick wrote:
> Can you tell me how to get/do this request? (seriously).
>
> read(32 sectors, beginning at LBA 50)
>
> How can one do this through the FS-layer?
WTF does FS have to that? But anyway, the most trivial way is
to have the driver set blk_size[m
On Sat, 30 Sep 2000, Alexander Viro wrote:
> ??? If "FS" means "filesystem" - it couldn't care less. If your driver can
Yes FS == "filesystem", sorry, I thought that was generic.
> give these blocks some numbers and is ready to serve requests - fine,
> filesystem will neither know nor care abou
[Hedrick]
> > FF FS-DeStroke
> > OEM-DeStroke
> > OO MAN-DeStroke
> > AAA MAN-ALL
[Viro]
On Fri, 29 Sep 2000, Andre Hedrick wrote:
> Yes all OEM's do this because they need everything to look the same.
> This is why you may get a replacement drive that is in reality a 30GB
> drive but because you had a 15GB drive originally, that is the capacity of
> the new drive. It has been "de
Greetings All,
WARNING: More infor than you every really wanted to know about the world
of storage and the concerns + issues, but read the whole thing or you will
never get the point.
On Sat, 30 Sep 2000, Theodore Y. Ts'o wrote:
>Date: Fri, 29 Sep 2000 22:16:53 -0700 (PDT)
>From: Andre
Date: Fri, 29 Sep 2000 22:16:53 -0700 (PDT)
From: Andre Hedrick <[EMAIL PROTECTED]>
Basically you can de-stroke a drive with what you let the OS/FS report.
Once this is done there is no way any FS can get to the stuff beyond what
it knows about.
I'm not sure what you mean by "de-s
Well I am of the opinion (some say it stinks),
Linux needs a mixed layer(s) above/below the FS to do direct access to the
drives. This must be placed in the request/list_head for continuity, but
I know what Matt wants and why.
I am working on it in ATA, but my partner in SCSI land refuse to at
"Theodore Y. Ts'o" wrote:
>Date:Fri, 29 Sep 2000 17:49:04 -0600
>From: "Jeff V. Merkey" <[EMAIL PROTECTED]>
>
>This is going to be a continuing problem for non-Unix file systems like
>NTFS and NWFS that rely on the ability to read and write variable length
>sector runs
Date:Fri, 29 Sep 2000 17:49:04 -0600
From: "Jeff V. Merkey" <[EMAIL PROTECTED]>
This is going to be a continuing problem for non-Unix file systems like
NTFS and NWFS that rely on the ability to read and write variable length
sector runs.
It's not just non-Unix file syste
Al,
This is going to be a continuing problem for non-Unix file systems like
NTFS and NWFS that rely on the ability to read and write variable length
sector runs. At some point, the AIO subsystem needs to get fixed. I
submitted a patch based on Linus' suggestion that the check in
ll_rw_block()
At 00:35 30/09/2000, Alexander Viro wrote:
>On Sat, 30 Sep 2000, Anton Altaparmakov wrote:
>
> > All those problems disappear as soon as you change BLOCK_SIZE to 512. And
>
>Have you actually tried that? Go ahead, just do full backup before the
>experiment...
I hope you don't mind me quoting my o
On Sat, 30 Sep 2000, Anton Altaparmakov wrote:
> All those problems disappear as soon as you change BLOCK_SIZE to 512. And
Have you actually tried that? Go ahead, just do full backup before the
experiment...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bod
At 23:59 29/09/2000, Andries Brouwer wrote:
>On Fri, Sep 29, 2000 at 05:36:48PM -0500, [EMAIL PROTECTED] wrote:
> > > >But the question was about reading from disk, not about reading
> > > >from partition.
> > Actually, that's next. In EFI, all partitions have a starting LBA and
> > ending LBA on
On Fri, Sep 29, 2000 at 05:36:48PM -0500, [EMAIL PROTECTED] wrote:
> > >But the question was about reading from disk, not about reading
> > >from partition.
> Actually, that's next. In EFI, all partitions have a starting LBA and
> ending LBA on the disk. So, it would be easy to have an "odd si
> > > That's what prevents linear raid and proper NTFS support
> from working on
> > > "odd sized" partitions...
> >
> >But the question was about reading from disk, not about reading
> >from partition.
>
Actually, that's next. In EFI, all partitions have a starting LBA and
ending LBA on the d
At 13:03 29/09/2000, Andries Brouwer wrote:
>On Fri, Sep 29, 2000 at 02:20:25AM +0100, Anton Altaparmakov wrote:
> > And if it has an odd number then you can't read the last sector at all! -
> > That's what prevents linear raid and proper NTFS support from working on
> > "odd sized" partitions...
At 00:40 29/09/2000, [EMAIL PROTECTED] wrote:
> >I'm writing some code to grok the Intel EFI GUID Partition Table structures.
> >To to so, my partition reading code (in fs/partitions) needs to be able to
> >read one physical sector at a time, particularly the first and last sectors
> >on the disk
On Fri, 29 Sep 2000, Alan Cox wrote:
> > To read say 32 sectors anywhere on the disk, I have to do 1024-byte aligned
> > bread()s, possibly doing an unaligned first block, aligned middle, and
> > unaligned last block.
> >
> > Is there an easier method?
>
> Set the block size, but set it back wh
> To read say 32 sectors anywhere on the disk, I have to do 1024-byte aligned
> bread()s, possibly doing an unaligned first block, aligned middle, and
> unaligned last block.
>
> Is there an easier method?
Set the block size, but set it back when finished
-
To unsubscribe from this list: send
At 00:40 29/09/2000, [EMAIL PROTECTED] wrote:
>I'm writing some code to grok the Intel EFI GUID Partition Table structures.
>To to so, my partition reading code (in fs/partitions) needs to be able to
>read one physical sector at a time, particularly the first and last sectors
>on the disk. The br
I'm writing some code to grok the Intel EFI GUID Partition Table structures.
To to so, my partition reading code (in fs/partitions) needs to be able to
read one physical sector at a time, particularly the first and last sectors
on the disk. The bread() function ultimately calls ll_rw_block(), whi
31 matches
Mail list logo
