On Tue, 24 Mar 2009 13:40:20 +0100 Peter Ankerstål
pe...@pean.org wrote:
Hi,
I have a LSI Logic sata/sas raid running, is there a way to see the
state of
the volume, like optimal, degraded or resyncing?
I've tried several commands with camcontrol but I cant figure it out.
--
Peter
Hi,
I have a LSI Logic sata/sas raid running, is there a way to see the
state of
the volume, like optimal, degraded or resyncing?
I've tried several commands with camcontrol but I cant figure it out.
--
Peter Ankerstål
pe...@pean.org
http://www.pean.org/
On 24 Mar 2009, at 13:40, Peter Ankerstål wrote:
Hi,
I have a LSI Logic sata/sas raid running, is there a way to see the
state of
the volume, like optimal, degraded or resyncing?
There is sysutils/linux-megacli
Yes, looks like ports/130505 is still pending unfortunately
I've tried
On Mar 24, 2009, at 2:08 PM, Ruben van Staveren wrote:
On 24 Mar 2009, at 13:40, Peter Ankerstål wrote:
Hi,
I have a LSI Logic sata/sas raid running, is there a way to see the
state of
the volume, like optimal, degraded or resyncing?
There is sysutils/linux-megacli
Sorry about that.
On Mar 24, 2009, at 9:20 AM, Peter Ankerstål wrote:
On Mar 24, 2009, at 2:08 PM, Ruben van Staveren wrote:
On 24 Mar 2009, at 13:40, Peter Ankerstål wrote:
Hi,
I have a LSI Logic sata/sas raid running, is there a way to see
the state of
the volume, like optimal, degraded or
On Mar 24, 2009, at 8:00 PM, Charles Sprickman wrote:
dev.mpt.0.nonoptimal_volumes: 0
Don't test whether the nonoptimal_volumes parameter works, it does -
but if you pull a drive, FreeBSD likes to panic both on the loss of
a disk
and then again when the drive is reconnected and the
Charles Sprickman wrote:
There is sysutils/linux-megacli
Sorry about that. This is not megaraid its the mpt driver.
LSI SAS3041E-R PCI-e
mpt0: LSILogic SAS/SATA Adapter port 0x2000-0x20ff mem
0xd021-0xd0213fff,0xd020-0xd020 irq 16 at device 0.0 on pci3
mpt0: [ITHREAD]
mpt0: MPI
On Mar 24, 2009, at 8:20 PM, Scott Long wrote:
Peter Ankerstål wrote:
On Mar 24, 2009, at 8:00 PM, Charles Sprickman wrote:
dev.mpt.0.nonoptimal_volumes: 0
Don't test whether the nonoptimal_volumes parameter works, it
does -
but if you pull a drive, FreeBSD likes to panic both on the
Peter Ankerstål wrote:
On Mar 24, 2009, at 8:00 PM, Charles Sprickman wrote:
dev.mpt.0.nonoptimal_volumes: 0
Don't test whether the nonoptimal_volumes parameter works, it does -
but if you pull a drive, FreeBSD likes to panic both on the loss of a
disk
and then again when the drive is
On Mar 24, 2009, at 8:50 PM, Marat N.Afanasyev wrote:
Scott
Im running RELENG_7 cvsuped and built like 15 hours ago. I still
have this problem.
Please come back to me if you want some additional information
about the setup.
--
Peter Ankerstål
pe...@pean.org
http://www.pean.org/
Peter Ankerstål wrote:
On Mar 24, 2009, at 8:20 PM, Scott Long wrote:
Peter Ankerstål wrote:
On Mar 24, 2009, at 8:00 PM, Charles Sprickman wrote:
dev.mpt.0.nonoptimal_volumes: 0
Don't test whether the nonoptimal_volumes parameter works, it does -
but if you pull a drive, FreeBSD likes
Scott Long wrote:
Peter Ankerstål wrote:
The instability during a rebuild should be fixed in 7.2 (and 7-stable as
of about the last month). If you can, please update your sources and
let me know if it helps.
As for actually monitoring and configuring arrays, that work is in
progress.
Scott
On Tue, 24 Mar 2009, Marat N.Afanasyev wrote:
Peter Ankerst?l wrote:
On Mar 24, 2009, at 8:20 PM, Scott Long wrote:
Peter Ankerst?l wrote:
On Mar 24, 2009, at 8:00 PM, Charles Sprickman wrote:
dev.mpt.0.nonoptimal_volumes: 0
Don't test whether the nonoptimal_volumes parameter works, it
Peter Ankerstål wrote:
On Mar 24, 2009, at 8:50 PM, Marat N.Afanasyev wrote:
Scott
Im running RELENG_7 cvsuped and built like 15 hours ago. I still
have this problem.
Please come back to me if you want some additional information about
the setup.
--
Peter Ankerstål
pe...@pean.org
14 matches
Mail list logo
