What is the recommended action on OmniOS 151014 about the L2Arc Problem
1. what is the recommended way to detect possible problems
a. run scrub? seems useless
b. run zdb pool and check for what
You said: Look for assertion failures, or other non-0 exits. Is
this the key for a corrupt
Apologies, this email escaped without a subject line. I'm hoping this
one, coupled with threading, will help ameliorate the problem.
--
"What is this talk of 'release'? Klingons do not make software
'releases'. Our software 'escapes,' leaving a bloody trail of
designers and quality assurance
Hello again!
With one week left until Surge & illumos Day, I wanted to make sure an update
to bloody happened. With recent illumos bugs (e.g. 6214) taking high priority,
I wanted to make sure their fixes ended up in the bloody release (as well as
appropriate ones making it back into r151014).
> From: Dan McDonald
> Sent: Monday, September 14, 2015 2:58 PM
>
> - OpenSSH is now at version 7.1p1.
Has the packaging been fixed in bloody so you can actually install this now
:)? If so, any thoughts on potentially back porting that to the current LTS
:)?
> - An additional pair of ZFS fixes
> From: Omen Wild
> Sent: Monday, September 14, 2015 3:10 PM
>
> Mostly we are wondering how to clear the corruption off disk and worried
> what else might be corrupt since the scrub turns up no issues.
While looking into possible corruption from the recent L2 cache bug it seems
that running
> From: Guenther Alka
> Sent: Monday, September 14, 2015 9:21 AM
>
> 1. what is the recommended way to detect possible problems
>a. run scrub? seems useless
I don't think it is necessarily useless, it might detect a problem. However,
from what I understand there might be a problem it doesn't
> From: Dan McDonald
> Sent: Monday, September 14, 2015 2:58 PM
>
> Most importantly, this update fixes illumos 6214 for OmniOS. You should
be
> able to restore your L2ARC devices using the method I mentioned in my last
e-
> mail:
Call me a scaredy-cat, but I think I might wait a bit for that
Hi Dan,
I will apply the upgrade to a couple of my OmniOS boxes today and give
it a go.
Thanks,
Stephan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
While trying to look for corruption from the recent L2 cache bug, I noticed
that zdb core dumps trying to list the history on both my data pool (which
had L2 cache) and my rpool (which did not). I'm wondering if there is some
bug with zdb that is causing this as opposed to corruption of the pool.
Am 15.09.15 um 03:46 schrieb Paul B. Henson:
From: Omen Wild
Sent: Monday, September 14, 2015 3:10 PM
Mostly we are wondering how to clear the corruption off disk and worried
what else might be corrupt since the scrub turns up no issues.
While looking into possible corruption from the recent
There have been some fixes there, but I'm not sure if it's all there. I do
know one has to use --reject options to make a switch.
Lauri "lotheac" Tirkkonen can provide more details. Also note - there is an
effort to replace sunssh with OpenSSh altogether.
Dan
Sent from my iPhone (typos,
On 9/14/15 9:18 PM, Doug Hughes wrote:
> That does seem to keep performance at much closer to parity. It still
> seems about 70-80% of peak vs what I was seeing before, but not that
> 100MB/sec bottleneck.
Well, that's the reality of compression. Even the compressibility check
is not free, but
Also I believe the compression is not threaded as well as it could be so you
may be limited by the single core performance of your machine.
-Original Message-
From: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] On
Behalf Of Saso Kiselkov
Sent: Monday, September 14, 2015
On 9/14/15 9:40 PM, Matthew Lagoe wrote:
> Also I believe the compression is not threaded as well as it could be so you
> may be limited by the single core performance of your machine.
It is multi-threaded.
Cheers,
--
Saso
___
OmniOS-discuss mailing
I know it is multithreaded just in my experience (at least historically) it
wasn't completely multi-threaded and you could run into bottlenecks with
spare cpu cores sitting idle.
-Original Message-
From: Saso Kiselkov [mailto:skiselkov...@gmail.com]
Sent: Monday, September 14, 2015 12:46
Probably something for Illumos, but you guys may have seen this or may like
to know.
I've got a 10g connected Xyratex box running OmniOS, and I noticed that no
matter how many streams (1, 2, 3) I only get 100MB/sec write throughput and
it just tops out. Even with 1 stream. This is with the
On 9/14/15 9:05 PM, Doug Hughes wrote:
> Probably something for Illumos, but you guys may have seen this or may
> like to know.
>
> I've got a 10g connected Xyratex box running OmniOS, and I noticed that
> no matter how many streams (1, 2, 3) I only get 100MB/sec write
> throughput and it just
17 matches
Mail list logo
