public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeffrey V. Merkey" <jmerkey@wolfmountaingroup.com>
To: "Jeffrey V. Merkey" <jmerkey@wolfmountaingroup.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3ware 6x00 monitor/control utilities broken/dropped since 2.6.10?
Date: Sat, 18 Mar 2006 16:52:36 -0700	[thread overview]
Message-ID: <441C9D44.6010209@wolfmountaingroup.com> (raw)
In-Reply-To: <441C7760.3000405@wolfmountaingroup.com>


Corrected FTP link.

ftp://ftp.soleranetworks.com/pub/solera/dsfs/RedHatEnterprise4/


Jeff

Jeffrey V. Merkey wrote:

> Dave,
>
> I had to revert to 2.6.9-22 ES4 kernels to solve this, and I still 
> needed to update the 3Ware driver in 2.6.9. There's a patch that 
> includes the latest 3Ware drivers that appears to make this work at 
> ftp.soleranetworks.com:/var/ftp/pub/solera/dsfs/. Look under the ES4 
> directory for the kernel and patch.
>
> Jeff
>
> Dave Johnson wrote:
>
>> I have a 3ware 6400 controller that I've been using for some 5 years
>> without problems. I just upgraded my kernel from 2.6.9 to
>> 2.6.15.6 and now the 3ware provided monitoring/control daemon (3dm) will
>> no longer talk to the driver in 2.6.15.
>>
>> It appears that /proc/scsi/3w-xxxx which the daemon relies on was 
>> removed
>> from the driver:
>>
>> open("/proc/scsi/3w-xxxx", 
>> O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such 
>> file or directory)
>> open("/proc/scsi/3w-xxxx-z", 
>> O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such 
>> file or directory)
>>
>> The problem is I'm already using the latest 3ware utilities (v6.9 for
>> the 6400). While the driver does allow access to the array from the
>> SCSI subsystem and I can use the filesystem, I have no way to monitor
>> or control it anymore.
>>
>> Any suggestions besides reverting back to 2.6.9 and staying there?
>>
>> I'd be happy to use a different monitor/control program if one exists.
>>
>>
>>
>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>


  reply	other threads:[~2006-03-18 23:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18  6:26 3ware 6x00 monitor/control utilities broken/dropped since 2.6.10? Dave Johnson
2006-03-18 21:10 ` Jeffrey V. Merkey
2006-03-18 23:52   ` Jeffrey V. Merkey [this message]
2006-03-19  3:52 ` David Rees

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=441C9D44.6010209@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox