On Sun, Mar 11, 2007 at 06:51:53PM -0400, Ric Wheeler wrote:
During the recent IO/FS workshop, we spoke briefly about the coming
change to a 4k sector size for disks on linux. If I recall correctly,
the general feeling was that the impact was not significant since we
already do most file
Now, if this disk was copied byte per byte (/bin/dd) to a
4096-based disk, and Linux would start using a sector size of
4096, then I would suddenly have
The ATA drives I'm aware of report 512 byte sector size, do 512 byte
I/O's but use 4K physical sectors and to get sane performance except the
First generation of 1K sector drives will continue to use the same
512-byte ATA sector size you are familiar with. A single 512-byte write
will cause the drive to perform a read-modify-write cycle. This
configuration is physical 1K sector, logical 512b sector.
The problem case is
MasthanUsha wrote:
Hi All,
Any one og you have any idea on scsi inquiry command ?
I want to send an Inquiry command to a scsi device through sd path (.i.e.
/dev/sda or /dev/sdb) by using SG_IO ioctl. Please explain me...
If you look at http://www.torque.net/sg/sg3_utils.html
and fetch
Make SG_SET_FORCE_LOW_DMA behave as advertised
I came across this by accident. I have serious doubts whether ISA DMA
is really relevant these days :-) but what the heck. Feel free to disregard
if this code is headed for the recycler anyway.
The SCSI-HOWTO says this about SG_SET_FORCE_LOW_DMA:
dudekula mastan wrote:
Hi Gilbert,
Thanks for quick reply.
The example program (sg_Simple --- not only this all examples) is taking
/dev/sg path as input but I want /dev/sd path as input.
In the lk 2.6 series, it will also work for sd devices
(and hd devices if they happen to
Olaf Kirch wrote:
Make SG_SET_FORCE_LOW_DMA behave as advertised
I came across this by accident. I have serious doubts whether ISA DMA
is really relevant these days :-) but what the heck. Feel free to disregard
if this code is headed for the recycler anyway.
The SCSI-HOWTO says this about
Alan Cox wrote:
First generation of 1K sector drives will continue to use the same
512-byte ATA sector size you are familiar with. A single 512-byte write
will cause the drive to perform a read-modify-write cycle. This
configuration is physical 1K sector, logical 512b sector.
The problem
Alan Cox wrote:
First generation of 1K sector drives will continue to use the same
512-byte ATA sector size you are familiar with. A single 512-byte write
will cause the drive to perform a read-modify-write cycle. This
configuration is physical 1K sector, logical 512b sector.
The problem
Jan Engelhardt wrote:
On Mar 11 2007 18:51, Ric Wheeler wrote:
During the recent IO/FS workshop, we spoke briefly about the
coming change to a 4k sector size for disks on linux. If I
recall correctly, the general feeling was that the impact was
not significant since we already do most file
On Mon, 2007-03-12 at 08:18 +, Christoph Hellwig wrote:
The FS stack and higher levels of the I/O stack should be mostly ready.
The S/390 DASDs are commonly used with 4k sector sizes, and we've had
the occasional 2k sector SCSI MO device aswell. It would be nice to
get samples of large
Jan Engelhardt wrote:
On Mar 11 2007 22:45, Ric Wheeler wrote:
Jan Engelhardt wrote:
On Mar 11 2007 18:51, Ric Wheeler wrote:
During the recent IO/FS workshop, we spoke briefly about the
coming change to a 4k sector size for disks on linux. If I
recall correctly, the general feeling was that
For 1K/4K logical sector sizes, who knows. EFI? grins and runs
Certainly seems incompatible with the current popular DOS partition format.
Its a bit messier than that. There are two interpretations of DOS
partition formats found on 2K sector size magneto opticals. One is that
everything is
Christoph Hellwig wrote:
the occasional 2k sector SCSI MO device aswell. It would be nice to
get samples of large sector size ATA devices into the hands of developers
to do real world testing of the whole stack.
hands of developers meaning you specifically? :)
I've had a
On Mon, Mar 12, 2007 at 10:45:16AM -0400, Jeff Garzik wrote:
Christoph Hellwig wrote:
the occasional 2k sector SCSI MO device aswell. It would be nice to
get samples of large sector size ATA devices into the hands of developers
to do real world testing of the whole stack.
hands of
This patchset updates the qla2xxx driver to 8.01.07-k6.
drivers/scsi/qla2xxx/qla_def.h | 13 -
drivers/scsi/qla2xxx/qla_os.c |4 +++-
drivers/scsi/qla2xxx/qla_sup.c | 11 +--
drivers/scsi/qla2xxx/qla_version.h |2 +-
4 files changed, 17 insertions(+),
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
qla2xxx driver fails to handle RSCN events affecting area or domain due
to an endian issue on big endian systems. This fixes the port_id_t
structure on big endian systems.
Signed-off-by: Malahal Naineni [EMAIL PROTECTED]
Acked-by: Seokmann Ju [EMAIL
Signed-off-by: Andrew Vasquez [EMAIL PROTECTED]
---
drivers/scsi/qla2xxx/qla_os.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/qla2xxx/qla_os.c b/drivers/scsi/qla2xxx/qla_os.c
index 68f5d24..f67ef38 100644
--- a/drivers/scsi/qla2xxx/qla_os.c
+++
We're observing soft lockups during HBA FLASH retrieval and
update. Add cond_resched() each time around the tight-loops
during flash read()s/write()s.
Signed-off-by: Andrew Vasquez [EMAIL PROTECTED]
---
drivers/scsi/qla2xxx/qla_sup.c |5 +
1 files changed, 5 insertions(+), 0
There's no need given, I/O has been quiesced, RISC
interrupts have been disabled, and finally the RISC has been
paused. Flash manipulation on ISP21xx, ISP22xx, and ISP23xx
parts requires the RISC to go through a full reset to
recover.
Signed-off-by: Andrew Vasquez [EMAIL PROTECTED]
---
Signed-off-by: Andrew Vasquez [EMAIL PROTECTED]
---
drivers/scsi/qla2xxx/qla_version.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/qla2xxx/qla_version.h
b/drivers/scsi/qla2xxx/qla_version.h
index 61347ae..dc85495 100644
---
Aravind Parchuri wrote:
[EMAIL PROTECTED] wrote:
Aravind Parchuri wrote:
My log messages were getting all mixed up, so I cleaned up my little
test to send just one command at a time. It actually looks like the mid
layer passes the command through to open-iscsi with the right size the
This patch updates the FC transport for all speeds identified in SM-HBA.
Note: it does not sync the bit definitions, as that is actually insulated
from user-space via the sysfs text string. (I could do it, but it does introduce
a potential binary-incompatibility).
-- james s
Signed-off-by: James
This fixes an oops during driver load time.
mptsas_probe calls mpt_attach(over in mptbase.c). Inside that
call, we read some manufacturing config pages to setup some
defaults. While reading the config pages, the firmware doesn't
complete the reply in time, and we have a timeout. The
DOS partitions start partitions on odd-numbered sectors
I don't get this. If you mean partitions defined by the classic DOS
partition table format, then AFAICS, such a partition can start in any
sector.
so presuming you have odd-aligned disks, life is good.
What is an odd-aligned disk?
-
To
Hello.
Bryan Henderson wrote:
DOS partitions start partitions on odd-numbered sectors
I don't get this. If you mean partitions defined by the classic DOS
partition table format, then AFAICS, such a partition can start in any
sector.
Only at logical cylinder boudary (except for the
Bryan Henderson wrote:
DOS partitions start partitions on odd-numbered sectors
I don't get this. If you mean partitions defined by the classic DOS
partition table format, then AFAICS, such a partition can start in any
sector.
Bryan,
Typically the first partition on a DOS partitioned disk
[EMAIL PROTECTED] wrote:
Aravind Parchuri wrote:
[EMAIL PROTECTED] wrote:
Aravind Parchuri wrote:
My log messages were getting all mixed up, so I cleaned up my little
test to send just one command at a time. It actually looks like the mid
layer passes the command through to open-iscsi with
As Doug pointed out, it's would be better for tgt to do nothing than
send the bugus sense when tgt hits the user-space bugs.
The patch was made against scsi-misc tree.
---
From: FUJITA Tomonori [EMAIL PROTECTED]
tgt notifies a LLD of the failure with sense when it hits the
user-space daemon
On Tue, Mar 13, 2007 at 01:11:44AM -0400, Andreas Dilger wrote:
I'd guess a vast majority of IO will have the end similarly
misaligned as the start. Very little filesystem IO is 512 bytes,
possibly excluding XFS in an unusual mode.
XFS (mkfs.xfs) can be told what the native sector size is
30 matches
Mail list logo
