RE: aacraid not detecting drives if compiled into kernel

2007-02-23 Thread Salyzyn, Mark
The driver in RHEL3 is old (1.1.5-2412ish, so not that old), use the Adaptec supplied sources and we will investigate. You can find them in our download section, just pick a 'modern' aac based card and browse for the latest. I believe I fixed the last set of problems associate with compiling the

[PATCH] bsg: return SAM device status code

2007-02-23 Thread Pete Wyckoff
Use the status codes from the standard, not the shifted-by-one codes that are marked deprecated in scsi.h. This makes bsg v4 status report the same value as sg v3 status too. Signed-off-by: Pete Wyckoff [EMAIL PROTECTED] --- block/bsg.c |2 +- 1 files changed, 1 insertions(+), 1

Re: [PATCH] bsg: return SAM device status code

2007-02-23 Thread Douglas Gilbert
Pete Wyckoff wrote: Use the status codes from the standard, not the shifted-by-one codes that are marked deprecated in scsi.h. This makes bsg v4 status report the same value as sg v3 status too. Pete, Good pick up. We certainly don't want to re-introduce the SCSI status byte shift from the

GFP_DMA in sd_revalidate_disk

2007-02-23 Thread Bernhard Walle
Hello, is GFP_DMA really needed in sd_revalidate_disk() in every circumstances? That's the code: buffer = kmalloc(SD_BUF_SIZE, GFP_KERNEL | __GFP_DMA); if (!buffer) { printk(KERN_WARNING (sd_revalidate_disk:) Memory allocation failure.\n); goto out; }

[RFC] FC Transport support for vports based on NPIV

2007-02-23 Thread James Smart
Here's the first pass at an RFC for NPIV-based virtual ports within the FC transport. The patch adds the following: - Addition of a new fc_vport object and class. The vport object is to be inserted into the device tree, and then new scsi_host object created as a child of the vport. Below

RE: [PATCH] qla2xxx: fix RSCN handling on big-endian systems

2007-02-23 Thread Seokmann Ju
ACK - Thank you for the findings. Acked-by: Seokmann Ju [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, February 19, 2007 10:19 AM To: linux-scsi@vger.kernel.org; Linux Driver Subject: [PATCH] qla2xxx: fix RSCN handling on

[Patch 2/2] cciss: supercedes add shutdown support (replaces reboot notifier)

2007-02-23 Thread Mike Miller (OS Dev)
Patch 2/2 This patch supercedes yesterdays cciss-shutdown patch. The primary difference is removing __devexit from cciss_remove_one. Instead of create another function I'd rather use the code that was intended to perform the cleanup and cache flush. I've tested as a loadable module and

Re: [Patch 1/2] cciss: fix for 2TB support

2007-02-23 Thread Mike Miller (OS Dev)
On Thu, Feb 22, 2007 at 04:06:41PM -0600, James Bottomley wrote: On Thu, 2007-02-22 at 16:02 -0600, Mike Miller (OS Dev) wrote: Will this patch for my patch work for now? Yes, I think that should be fine ... it's only a theoretical worry; at the moment sector_t is unsigned ... but just in

[Patch 1/2] cciss: fix for 2TB support (again)

2007-02-23 Thread Mike Miller (OS Dev)
Patch 1/2 This patch changes the constant 0x to 0xULL to prevent sign extension. Previously: This patch changes the way we determine if a logical volume is larger than 2TB. The original test looked for a total_size of 0. Originally we added 1 to the total_size. That would

Re: [Patch 2/2] cciss: supercedes add shutdown support (replaces reboot notifier)

2007-02-23 Thread Greg KH
On Fri, Feb 23, 2007 at 02:42:39PM -0600, Mike Miller (OS Dev) wrote: Patch 2/2 This patch supercedes yesterdays cciss-shutdown patch. The primary difference is removing __devexit from cciss_remove_one. Instead of create another function I'd rather use the code that was intended to

Re: [Patch 2/2] cciss: supercedes add shutdown support (replaces reboot notifier)

2007-02-23 Thread Mike Miller (OS Dev)
On Fri, Feb 23, 2007 at 01:32:36PM -0800, Greg KH wrote: On Fri, Feb 23, 2007 at 02:42:39PM -0600, Mike Miller (OS Dev) wrote: Patch 2/2 This patch supercedes yesterdays cciss-shutdown patch. The primary difference is removing __devexit from cciss_remove_one. Instead of create another

end to end error recovery musings

2007-02-23 Thread Ric Wheeler
In the IO/FS workshop, one idea we kicked around is the need to provide better and more specific error messages between the IO stack and the file system layer. My group has been working to stabilize a relatively up to date libata + MD based box, so I can try to lay out at least one appliance

Re: end to end error recovery musings

2007-02-23 Thread H. Peter Anvin
Ric Wheeler wrote: We still have the following challenges: (1) read-ahead often means that we will retry every bad sector at least twice from the file system level. The first time, the fs read ahead request triggers a speculative read that includes the bad sector (triggering the error

Re: end to end error recovery musings

2007-02-23 Thread Andreas Dilger
On Feb 23, 2007 16:03 -0800, H. Peter Anvin wrote: Ric Wheeler wrote: (1) read-ahead often means that we will retry every bad sector at least twice from the file system level. The first time, the fs read ahead request triggers a speculative read that includes the bad sector

Re: end to end error recovery musings

2007-02-23 Thread H. Peter Anvin
Andreas Dilger wrote: And clearing this list when the sector is overwritten, as it will almost certainly be relocated at the disk level. Certainly if the overwrite is successful. -hpa - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to

Re: end to end error recovery musings

2007-02-23 Thread Theodore Tso
On Fri, Feb 23, 2007 at 05:37:23PM -0700, Andreas Dilger wrote: Probably the only sane thing to do is to remember the bad sectors and avoid attempting reading them; that would mean marking automatic versus explicitly requested requests to determine whether or not to filter them against

Re: [Patch 1/2] cciss: fix for 2TB support

2007-02-23 Thread Andrew Morton
On Fri, 23 Feb 2007 14:52:29 -0600 Mike Miller (OS Dev) [EMAIL PROTECTED] wrote: On Thu, Feb 22, 2007 at 04:06:41PM -0600, James Bottomley wrote: On Thu, 2007-02-22 at 16:02 -0600, Mike Miller (OS Dev) wrote: Will this patch for my patch work for now? Yes, I think that should be fine