Here enclosed release 6.05 of the EATA ISA/EISA/PCI and
Ultrastor 14F/34F SCSI drivers.
This patch applies to lk-2.4.4.
*
* 1 May 2001 Rev. 6.05 for linux 2.4.4
*+ Clean up all pci related routines.
*+ Fix data transfer direction for opcode SEND_CUE_SHEET (0x5d)
*
So, will Linux ever support the scsi reservation mechanism as standard ?
Isn't there a standard that says if you scsi reserve a disk, no one
else should be able to access this disk, or is this a "steeleye/Compaq"
standard.
Chris
-Original Message-
From: James Bottomley [mailto:[EMAIL PRO
On Tuesday, 1. May 2001 02:23, Alan Cox wrote:
> > scsi_unregister_host first checks the use count and then marks the device
> > offline. The order is wrong. By the time the device goes offline, it
> > might have been opened again.
>
> That should be right in -ac but you might want to double chec
Hi,
scsi_register_host() can in the error case _decrement_ the module usage
counter of the scsi core module and it has a race with module unload during
bus scan.
if (tpnt->present) {
if (pcount == next_scsi_host) {
if (tpnt->present > 1) {
> reserved.But if you did such a hot swap you would have "bigger
> fish to fry" in a HA application... I mean, none of your data would be
> there!
You need to realise this has happened and do the right thing. Since
it could be an md raid array the hotswap is not fatal.
[EMAIL PROTECTED] said:
> Does this package also tell the kernel to "re-establish" a reservation
> for all devices after a bus reset, or at least inform a user level
> program? Finding out when there has been a bus reset has been a
> stumbling block for me.
[EMAIL PROTECTED] said:
> You cannot
[EMAIL PROTECTED] said:
> So, will Linux ever support the scsi reservation mechanism as standard?
That's not within my gift. I can merely write the code that corrects the
behaviour. I can't force anyone else to accept it.
[EMAIL PROTECTED] said:
> Isn't there a standard that says if you scsi
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.
Doug Ledford writes:
(James Bottomley commented about the need for SCSI reservation kernel patches)
>
> I agree. It's something that needs fixed in general, your software needs it
> as well, and I've written (about 80% done at this point) some open source
> software geared towards getting/ho
James Bottomley wrote:
>
> [EMAIL PROTECTED] said:
> > So, will Linux ever support the scsi reservation mechanism as standard?
>
> That's not within my gift. I can merely write the code that corrects the
> behaviour. I can't force anyone else to accept it.
I think it will be standard before n
> Does this package also tell the kernel to "re-establish" a
> reservation for all devices after a bus reset, or at least inform a
> user level program? Finding out when there has been a bus reset has
> been a stumbling block for me.
You cannot rely on a bus reset. Imagine hot swap disks on an F
Alan Cox writes:
> > Does this package also tell the kernel to "re-establish" a
> > reservation for all devices after a bus reset, or at least inform a
> > user level program? Finding out when there has been a bus reset has
> > been a stumbling block for me.
>
> You cannot rely on a bus re
12 matches
Mail list logo
