I had a 4 disk RAIDZ1 array. I did not monitor it's status as closely
as I should have. My first sign of trouble was that programs doing
writes all locked up. When I looked two drives in the array where
showing problems via "zpool status".
After purchasing more hard drives to move the data to (
Hi All,
No joy.. the system seized up again within a few hours of coming back up.
>
> Now trying another suggestion sent to me by a direct poster:
>
> * Recommendation from Sun (Oracle) to work around a bug:
> * 6958068 - Nehalem deeper C-states cause erratic scheduling behavior
> set
On Wed, November 2, 2011 08:25, Paul Kraus wrote:
> On Wed, Nov 2, 2011 at 7:05 AM, Jim Klimov wrote:
>
>> Really, they WERE still a useful reference for many of us,
>> even if posted a few years back...
>
> I always used the mailing list, and have kept every message since
> I subscribed in ab
On Wed, Nov 2, 2011 at 7:05 AM, Jim Klimov wrote:
> Really, they WERE still a useful reference for many of us,
> even if posted a few years back...
I always used the mailing list, and have kept every message since
I subscribed in about July of 2007 in my Google Apps account to make
searching
2011-11-02 5:52, Edward Ned Harvey пишет:
From: Daniel Carosone [mailto:d...@geek.com.au]
On Tue, Nov 01, 2011 at 06:17:57PM -0400, Edward Ned Harvey wrote:
You can do both poorly for free, or you can do both very well for big
bucks.
That's what opensolaris was doing.
That mess was costing
