On Mon, Aug 22, 2005 at 05:08:33PM -0600, Moore, Eric Dean wrote:
On Sunday, August 21, 2005 10:53 AM, Christoph Hellwig wrote:
This is just a brindup helper because the Fusion hardware does a SAS
remote port to target ID mapping in firmware, in fact the firmware
interface only addresses
On Wed, Aug 24, 2005 at 10:57:56AM +0200, Christoph Hellwig wrote:
On Wed, Aug 24, 2005 at 12:08:40AM -0700, Jeremy Higdon wrote:
Hi Christoph,
I applied your four (sets of) patches, and they all seem to work
fine. When connected through an expander, the data is a little light,
but
On Tue, Aug 23, 2005 at 07:22:59PM -0400, Luben Tuikov wrote:
On 08/22/05 01:12, Douglas Gilbert wrote:
I was surprised how much code needed changing.
With MODE SELECT's issues with libata addressed
various other SAT extras should be much easier
to implement. That should make libata more
On Wed, Aug 24, 2005 at 02:10:14AM -0700, Jeremy Higdon wrote:
However, after updating firmware on the 1064, this latter problem
seems to be fixed (still doesn't discover devices on the expander
at driver init).
As mentioned expanders aren't tested at all yet, I'll fix it as soon
as I have an
Christoph Hellwig wrote:
On Thu, Aug 18, 2005 at 04:05:29PM -0400, Luben Tuikov wrote:
On 08/18/05 13:56, Christoph Hellwig wrote:
snip/
What we might need an rport for is to support SMP. I'm
not yet sure how to do SMP passthrough, but we will need some object
to represent SMP ports.
Why?
Hello,
On Wed, Aug 24, 2005 at 11:01:12AM +0100, Christoph Hellwig wrote:
yes exactly, only the bootdrive LUN is registered after bootup. I have
to selectively scsiadd the other LUNs if there is a gap between the
boot LUN (1-8 in our setup) and the shared storages (9-14). I don't
On Wed, Aug 24, 2005 at 02:48:03PM +0200, Frederik Schueler wrote:
Hello,
On Wed, Aug 24, 2005 at 11:01:12AM +0100, Christoph Hellwig wrote:
yes exactly, only the bootdrive LUN is registered after bootup. I have
to selectively scsiadd the other LUNs if there is a gap between the
boot
On 8/24/05, Stefan Richter [EMAIL PROTECTED] wrote:
Timers appear to operate in an atomic context, so timers should not be
allowed to call scsi_remove_device, which eventually schedules.
Any suggestions on the best way to fix this?
Workqueue, perhaps.
Perhaps. Actually, of course :)
Hi everybody,
here are some issues I'm having with my system dealing with
hot-swapping.
The box is a Tyan GX28 (B2881) B2881G28U4H with 4 Hot-swap U320 SCSI
bays. SCSI controller is Adaptec AIC-7902 dual channel Ultra320 SCSI.
# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id:
On 08/24/05 07:03, Douglas Gilbert wrote:
Luben Tuikov wrote:
On 08/22/05 01:12, Douglas Gilbert wrote:
I was surprised how much code needed changing.
With MODE SELECT's issues with libata addressed
various other SAT extras should be much easier
to implement. That should make libata more
On Wed, Aug 24, 2005 at 03:08:23PM +0200, Frederik Schueler wrote:
Hello,
no change.
What was logged? Any errors?
Try setting scsi logging_level for scan, after boot/load:
sysctl -w dev.scsi.logging_level=0x1c0
Then reload the qla driver, and post logs.
If the qlogic driver returned
In general, I'm a bit worried about these changes, for two overall reasons:
1) I didn't see any analysis of the ultimate end users of block layer
error values: the filesystems.
2) This begins to converge with the SCSI layer's error/retry/etc. error
values. Since I would eventually like to
Jeff Garzik wrote:
In general, I'm a bit worried about these changes, for two overall reasons:
1) I didn't see any analysis of the ultimate end users of block layer
error values: the filesystems.
The filesystems or helpers they use normally did not even check the
-Exyz error they were
Patrick Mansfield wrote:
On Wed, Aug 24, 2005 at 04:03:58AM -0500, Mike Christie wrote:
-#define end_io_error(uptodate) (unlikely((uptodate) = 0))
+enum {
+ BLK_SUCCESS = 0,/* Must be zero for compat with old usage */
+ BLKERR_IO, /* Generic I/O error */
+
On Wed, 2005-08-24 at 12:21 -0700, Patrick Mansfield wrote:
On Wed, Aug 24, 2005 at 04:03:58AM -0500, Mike Christie wrote:
-#define end_io_error(uptodate) (unlikely((uptodate) = 0))
+enum {
+ BLK_SUCCESS = 0,/* Must be zero for compat with old usage */
+ BLKERR_IO,
Hello, all.
Here's the situation. I am running a QLogic QLA2200 (32-bit mode; lspci
output follows), and when I issue an ioctl() to call
SCSI_IOCTL_PROBE_HOST to /dev/sg0 (example code follows as well), the
ioctl() returns 0, as if to imply that there is no host present, which
is obviously not
On Wed, Aug 24, 2005 at 04:05:03PM -0400, Luben Tuikov wrote:
On 08/24/05 13:12, Patrick Mansfield wrote:
On Tue, Aug 23, 2005 at 07:55:37PM -0400, Luben Tuikov wrote:
Where does udev get its label?
You can call any script or program from udev and use the result. There are
And
James Bottomley wrote:
On Wed, 2005-08-24 at 12:21 -0700, Patrick Mansfield wrote:
On Wed, Aug 24, 2005 at 04:03:58AM -0500, Mike Christie wrote:
-#define end_io_error(uptodate) (unlikely((uptodate) = 0))
+enum {
+ BLK_SUCCESS = 0,/* Must be zero for compat with old usage */
+
On Wed, 2005-08-24 at 15:50 -0500, Mike Christie wrote:
Would it be good then to also extend the fail fast flag to a bit map so
dm-multipath can tell scsi that scsi should handle device errors?
You mean have a REQ_FASTFAIL_{DEV,XPRT,DRV}? The slight problem is that
we're already closing in on
On Wed, 24 Aug 2005, Drew Winstel wrote:
Here's the situation. I am running a QLogic QLA2200 (32-bit mode; lspci
output follows), and when I issue an ioctl() to call
SCSI_IOCTL_PROBE_HOST to /dev/sg0 (example code follows as well), the
ioctl() returns 0, as if to imply that there is no host
On 8/24/05, Lukasz Kosewski [EMAIL PROTECTED] wrote:
On 8/24/05, Stefan Richter [EMAIL PROTECTED] wrote:
Timers appear to operate in an atomic context, so timers should not be
allowed to call scsi_remove_device, which eventually schedules.
Any suggestions on the best way to fix this?
21 matches
Mail list logo
