Well,
Hardcoding of block size to 512 bytes for disk devices is what currently
either the block device driver or the sd driver is doing. Because, if
I run dd to the same device using the corresponding block device (sde)
it runs fine. So, I feel that either the sg driver or the block device
dri
Hi List,
I am trying to use sg_dd which goes through the scsi generic driver.
This is how use it.
sg_dd if=/dev/zero of=/dev/sg5 bs=4096 count=1
And sg5 is actually a disk.
The question that I have is, does the scsi generic driver have a knowledge
about what kind of device it is dealing with
Hi List,
I was going through the 2.4.2/2.4.4 scsi error handling
and scsi_done routine. I could not figure out how the
scsi layer handles the DID_BAD_TARGET status in the
host-byte of result that is returned by low-level driver.
It looks like, DID_BAD_TARGET is not being handled at
all in th
Hi List,
Is Compaq's cpqfc driver enabled for 2.4.x kernel ? In the
drivers/scsi/Config.in file there is an entry for this driver,
but the drivers/scsi/Makefile does not know how to build this
driver. The sources are present in the drivers/scsi directory,
but don't know how to build it.
Regards
Hi List,
In the scsi_unjam_host(), after issueing a Bus Device Reset
(scsi_try_bus_device_reset()), we just restart only one command
to the device. What about other commands which are issued to the
same device and not completed yet ? Shouldn't they be restarted ?
There is the following comment b
Hi List,
I was looking at scsi_error.c In the scsi_unjam_host(),
we call scsi_try_to_abort_command() which calls eh_abort_handler(),
now, if somehow the lowlevel driver cannot abort the command
successfully, then it can return FAILED status. Well, in scsi_unjam_host()
there is a case for doing ce
Hi List,
I am running a couple of dd processes on the scsi drives
on ia64 running 2.4.2 kernel.
e.g.
while [ 1 ]; do
dd if=/dev/zero of=/dev/sdb1 bs=1024 count=2500
done &
while [ 1 ] ; do
dd if=/dev/zero of=/dev/sdb2 bs=1024 count=2500
done &
while [ 1 ] ; do
dd if=/dev/zero of=/dev/sdb
Hi List,
I tried to do dd to a bunch of scsi drives running in background.
e.g. dd if=/dev/zero of=/dev/sdb bs=1024 &
dd if=/dev/zero of=/dev/sdc bs=1024 &
dd if=/dev/zero of=/dev/sdd bs=1024 &
Then I tried to kill the first dd process writing to /dev/sdb
and it freezes up the system.
Hi list,
Can we call scsi_done() to complete the I/O from the
queuecommand() ? (e.g. in case of some error, or
to make queuecommand synchronous).
Regards,
-hiren
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
sym53c8xx driver tries to lock io_request_lock before calling done
routine. Also, scsi mid-layer routine scsi_done tries to acquire
the same lock. Won't the system hang at that point ?
-hiren
> -Original Message-
> From: GĂ©rard Roudier [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, Februa
Hi List,
Is it possible to force linux scsi layer to rescan the
devices on a scsi_bus ? Are there any application/ioctls available
which can do this ?
Regards,
-hiren
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
Hi list,
I want to create a subdirectory under scsi for my module. The
tree that I want to create a something like this:
drivers/scsi/xxx
drivers/scsi/xxx/lib
drivers/scsi/xxx/my_hba_driver
Basically the files in lib get compiled and linked together
which ultimately gets linked with the file in
Greetings.
Any idea when the support for medium changer or tape-library
will be available in linux ? As I understand the scsi.c and st.c
does not recognize medium changer devices.
Regards,
-hiren
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to
Here, to release the io_request_lock, should I use spin_unlock_irqrestore()
or just spin_unlock() ? The problem with using spin_unlock_irqrestore()
is that it needs the previously saved value of flags, which I don't
have in the low level driver. If I just use spin_unlock(), then the
interrupts wi
There is one problem here (atleast I think, unless I misunderstood
something). The scsi_error_handler() routine calls spin_lock_irqsave()
before calling scsi_unjam host(). On UP system atleast, spin_lock_irqsave()
is nothing but save_flags(); cli(). So basically, do we disable all the
interrupts
Hi All,
I was looking at the scsi_error.c and in particular at the scsi_unjam_host()
routine. It calls scsi_try_to_abort_command which calls eh_abort_handler()
routine of the hba driver. We are passing timeout to the
scsi_try_to_abort_command(). But we don't seem to making use of it.
Shouldn't
Hi All,
I received many responses on FORMAT_UNIT command.
I really appreciate.
Does anybody know, why fdisk is dumping core if partition table
is bad ?
Thanks and regards,
-hiren
> -Original Message-
> From: Robin T. Miller [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 24, 2001
I tried this driver and on my qlogic ISP2100 I am getting the following
error. I am not sure what is going on. Is there something wrong with
the card ?
qla2x00: detect() found an HBA
qla2x00: VID=1077 DID=2100 SSVID=0 SSDID=0
(scsi): Found a QLA2100 @ bus 5, device 1, irq 80, iobase 0xf800
scsi(
where can I find ISP2x00 driver for kernel 2.4.0 running on ia64 ?
Thanks and regards,
-hiren
> -Original Message-
> From: Craig Ruff [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 19, 2001 9:03 AM
> To: Klaus Naumann
> Cc: [EMAIL PROTECTED]
> Subject: Re: QLogic ISP2x00 problem
>
>
19 matches
Mail list logo