Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 31 Jan 2009 14:02:49 -0500
From:      Gary Palmer <gpalmer@freebsd.org>
To:        Charles Sprickman <spork@bway.net>
Cc:        freebsd-stable@freebsd.org, Richard Tector <richardtector@thekeelecentre.com>
Subject:   Re: 7.1, mpt and slow writes
Message-ID:  <20090131190249.GH81380@in-addr.com>
In-Reply-To: <alpine.OSX.2.00.0901310139480.37588@toasty.nat.fasttrackmonkey.com>
References:  <alpine.OSX.2.00.0901290351250.37588@toasty.nat.fasttrackmonkey.com> <49819672.1090208@thekeelecentre.com> <alpine.OSX.2.00.0901292253160.37588@toasty.nat.fasttrackmonkey.com> <20090130050451.GF81380@in-addr.com> <alpine.OSX.2.00.0901310139480.37588@toasty.nat.fasttrackmonkey.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 31, 2009 at 01:48:46AM -0500, Charles Sprickman wrote:
> On Fri, 30 Jan 2009, Gary Palmer wrote:
> 
> >On Thu, Jan 29, 2009 at 11:43:11PM -0500, Charles Sprickman wrote:
> >
> >[ snip ]
> >
> >>Any idea what happened to the sysctl?  Is there some other method to
> >>verify the loader tunable took (other than testing the throughput)?
> >
> >Boot with -v.  If the loader tunable took effect, you should see
> >"Enabling SATA WC on phy " instead of "Disabling SATA ..."
> 
> Cool, it works then.  Why was the info removed from the sysctl mib?
> 
> mpt0: Enabling SATA WC on phy 0
> mpt0: Enabling SATA WC on phy 1
> 
> Bonnie++ is showing me about 24MB/s writes and 70MB/s reads.
> 
> Is any of this verbose stuff problematic?
> 
> mpt0: No Handlers For Any Event Notify Frames. Event 0xa (ACK not required).
> mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not 
> required).
> mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not 
> required).
> mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not 
> required).
> mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not 
> required).
> mpt0: No Handlers For Any Event Notify Frames. Event 0xb (ACK not required).
> 
> And is any of this info found at boot-time accessible while the system is 
> running?

Hi,

Sorry, I can't answer your questions - all I did to find the
boot -v information was to look in the kernel source code.  Grepping
through the CVS history I don't actually see a point in CVS history
where there was a sysctl MIB value for the SATA WC status, although I
might be mistaken.  Perhaps you are remembering using kenv to get
at hw.mpt.enable_sata_wc instead of sysctl?

Regards,

Gary

> mpt0:vol0(mpt0:0:0): Settings ( Hot-Plug-Spares High-Priority-ReSync )
> mpt0:vol0(mpt0:0:0): Using Spare Pool: 0
> mpt0:vol0(mpt0:0:0): 2 Members:
>       (mpt0:1:32:0): Primary Online
>       (mpt0:1:1:0): Secondary Online
> mpt0:vol0(mpt0:0:0): RAID-1 - Optimal
> mpt0:vol0(mpt0:0:0): Status ( Enabled )
> (mpt0:vol0:1): Physical (mpt0:0:1:0), Pass-thru (mpt0:1:0:0)
> (mpt0:vol0:1): Online
> (mpt0:vol0:0): Physical (mpt0:0:32:0), Pass-thru (mpt0:1:1:0)
> (mpt0:vol0:0): Online
> 
> Thanks,
> 
> Charles
> 
> ps - would it kill Dell to make a damn ISO of a bootable media for RAID 
> controller firmware upgrades???  I don't even own anything with a floppy 
> drive anymore.
> 
> >Regards,
> >
> >Gary
> >
> >_______________________________________________
> >freebsd-stable@freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> >
> 
> 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090131190249.GH81380>