From: James Bottomley <[EMAIL PROTECTED]>
Date: Sat, 30 Jul 2005 15:23:20 -0500
> Actually, I saw this and increased MAX_LINKS as well.
That does absolutely nothing, you cannot create sockets
with protocol numbers larger than NPROTOS which like MAX_LINKS
has the value 32. And NPROTOS is somethin
From: Dmitry Yusupov <[EMAIL PROTECTED]>
Date: Sat, 30 Jul 2005 14:25:28 -0700
> It would be nice to set MAX_LINKS to 64 and close this issue for now,
James and Dmitry, increasing MAX_LINKS does't work, did you actually
try to open a netlink socket with a protocol number larger than 32?
It will
I wrote:
According to dmesg with SBP2_DEBUGs enabled,
scsi_remove_device() is entered but sbp2_logout_device() not.
IOW scsi_remove_device() is not completed.
Another evidence of this is that "Synchronizing SCSI cache for
disk sda:" appears again when I shut the system down.
Perhaps you can t
Ben Collins wrote on 2005-07-26:
Sounds like it is probably hanging in sbp2 while it is trying to logout.
I don't think so. According to dmesg with SBP2_DEBUGs enabled,
scsi_remove_device() is entered but sbp2_logout_device() not.
IOW scsi_remove_device() is not completed. (I'm using sbp2 rev
1
On Sat, 2005-07-30 at 15:23 -0500, James Bottomley wrote:
> On Sat, 2005-07-30 at 12:53 -0700, David S. Miller wrote:
> > From: James Bottomley <[EMAIL PROTECTED]>
> > Date: Sat, 30 Jul 2005 12:32:42 -0500
> >
> > > FIB has taken your netlink number, so I changed it to 32
> >
> > MAX_LINKS is 32,
On Sat, 2005-07-30 at 12:53 -0700, David S. Miller wrote:
> From: James Bottomley <[EMAIL PROTECTED]>
> Date: Sat, 30 Jul 2005 12:32:42 -0500
>
> > FIB has taken your netlink number, so I changed it to 32
>
> MAX_LINKS is 32, so there is no way this reassignment would
> work.
Actually, I saw thi
From: Christoph Hellwig <[EMAIL PROTECTED]>
Subject: Re: [ANNOUNCE 0/7] Open-iSCSI/Linux-iSCSI-5 High-Performance Initiator
Date: Sat, 30 Jul 2005 20:38:03 +0200
> On Sat, Jul 30, 2005 at 11:36:22AM -0700, Alex Aizman wrote:
> > OK. Hopefully that'll remain.
>
> Please ask davem for a netlink num
From: James Bottomley <[EMAIL PROTECTED]>
Date: Sat, 30 Jul 2005 12:32:42 -0500
> FIB has taken your netlink number, so I changed it to 32
MAX_LINKS is 32, so there is no way this reassignment would
work.
You have to pick something in the range 0 --> 32, and as is
no surprise, there are no numbe
On Sat, Jul 30, 2005 at 11:36:22AM -0700, Alex Aizman wrote:
> OK. Hopefully that'll remain.
Please ask davem for a netlink number allocation.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.
James Bottomley wrote:
On Wed, 2005-06-01 at 13:08 -0700, Alex Aizman wrote:
This is open-iscsi/linux-iscsi-5 Initiator. This submission is ready for
inclusion into mainline kernel.
OK, I tried to put this into scsi-misc.
FIB has taken your netlink number, so I changed it to 32
OK. Hopef
On Wed, 2005-06-01 at 13:08 -0700, Alex Aizman wrote:
> This is open-iscsi/linux-iscsi-5 Initiator. This submission is ready for
> inclusion into mainline kernel.
OK, I tried to put this into scsi-misc.
FIB has taken your netlink number, so I changed it to 32
__nlm_put() has had an updated proto
On Mon, 2005-07-25 at 10:07 +0200, Hannes Reinecke wrote:
> But this is not the root problem.
>
> target5:0:10: FAST-160 WIDE SCSI 320.0 MB/s ST IU (6.25 ns, offset 127)
> scsi5: target 10 synchronous with period = 0x8, offset =
> 0x7f(RDSTRM|DT|IU|QAS)
>
> So, the ppr_options (which have genera
On Wed, 2005-07-27 at 10:22 -0400, conway, heather wrote:
> I'd like to request that the enclosed patch to scsi_devinfo.c be considered
> for inclusion in the v2.6.x kernel. This would add support for sparse LUNs
> and large LUNs for the EMC Invista product.
For 2.6, I assume this device report
13 matches
Mail list logo
