On May 18, 2015, at 2:25 PM, Jeff Stockett jstock...@molalla.com wrote:
A drive failed in one of our supermicro 5048R-E1CR36L servers running omnios
r151012 last night, and somewhat unexpectedly, the whole system seems to have
panicked.
The panic was done for protection of your pool:
A drive failed in one of our supermicro 5048R-E1CR36L servers running omnios
r151012 last night, and somewhat unexpectedly, the whole system seems to have
panicked.
May 18 04:43:08 zfs01 scsi: [ID 365881 kern.info]
/pci@0,0/pci8086,2f02@1/pci15d9,808@0 (mpt_sas0):
May 18 04:43:08 zfs01
Dan McDonald wrote:
On May 18, 2015, at 2:25 PM, Jeff Stockett jstock...@molalla.com wrote:
A drive failed in one of our supermicro 5048R-E1CR36L servers running omnios
r151012 last night, and somewhat unexpectedly, the whole system seems to have
panicked.
The panic was done for
Dan McDonald wrote:
On May 18, 2015, at 3:01 PM, Jeff Stockett jstock...@molalla.com wrote:
Hi Dan,
The pool is made up of 36 disks - 6 x 6 raidz2 vdevs with some SSDs for l2arc
and slog. I already replaced the drive and the rebuild is nearly done, but I
was mostly curious why a disk
On Mon, May 18, 2015 at 06:25:34PM +, Jeff Stockett wrote:
A drive failed in one of our supermicro 5048R-E1CR36L servers running
omnios r151012 last night, and somewhat unexpectedly, the whole system
seems to have panicked.
You don't happen to have failmode set to panic on the pool?
From
Jeff,
I have them WD40001FYYG drives in my home server but just as a simple
mirror. AFAIK those drives are equivalent to the SATA WD Re 4GB drives
but just w/ a SAS controller instead a SATA controller on top and just a
little more expensive than their SATA equivalents...
I have no real
On May 18, 2015, at 6:31 PM, Tim Rice t...@multitalents.net wrote:
My question to you all is this: To which gcc version should we jump? I see
two viable candidates:
Any reason not to consider CLANG instead of GCC?
Completely new beast and potential for least-surprise. I can imagine
The pool is set to fail mode wait.
In looking at the fmdump -e and fmdump -eV output, it looks just like the drive
started having media/disk/transport errors around 3:40am and eventually
culminated in the reboot around 6:18am. The funny thing is that
driver-assessment = fatal was returned
My question to you all is this: To which gcc version should we jump?
I see two viable candidates:
- gcc 4.9.2 (last updated October 2014)
or
- gcc 5.1 (last updated April 2015)
Naïvely, shouldn't the newer be better? Less work during the the next
version jump...
Regards
I am indeed seeing this problem.
I'm not sure how to fix it (or how it got that way in the first place.
The only other thing I can recommend is the new for '014 and later -m latest
option to pkgrecv, which only gets you the LATEST version(s) of the packages:
nowhere(~/junk)[0]%
Hi Dan!
I'll be updating the whole wad of bloody later this week. Can y'all
wait a couple of days? I want to include some illumos updates that
I'm about to push this afternoon.
So after that push, everything was fine with the bloody repo.
However, it seems that the original problem Chavdar
Hello all, I have a RaidZ setup with 5 disks and rad performance is good.
I have no ZIL pool and 8 GB or ECC Ram. Writes are like 2 MB a second with
a 1GB network. I'm pulling faster writes on a similar drive in a windows
VM over CIFS on VMware. My OmniOS box is bare metal. Any tips on
On Mon, May 18, 2015 at 4:56 PM, Volker A. Brandt v...@bb-c.de wrote:
Naïvely, shouldn't the newer be better? Less work during the the next
version jump...
The very first thing on the 5-series changes list
(https://gcc.gnu.org/gcc-5/changes.html):
* The default mode for C is now -std=gnu11
18 мая 2015 г. 23:18:15 CEST, Dain Bentley dain.bent...@gmail.com пишет:
Hello all, I have a RaidZ setup with 5 disks and rad performance is
good.
I have no ZIL pool and 8 GB or ECC Ram. Writes are like 2 MB a second
with
a 1GB network. I'm pulling faster writes on a similar drive in a
windows
In message alpine.uw2.2.11.1505181528490.29...@server01.int.multitalents.net,
Tim Rice writes:
Any reason not to consider CLANG instead of GCC?
Does anyone have a build recipe for LLVM/clang on OmniOS?
I'm about to try that path to build Google's V8.
John
groenv...@acm.org
Now this isn't a gcc update for illumos/illumos-omnios... that way is full of
pain, and I'll wait for now.
OTOH, we've transitioned gcc before going into r151008 with 4.8.1.
My question to you all is this: To which gcc version should we jump? I see
two viable candidates:
- gcc 4.9.2
On Mon, May 18, 2015 at 4:38 PM, Dan McDonald dan...@omniti.com wrote:
My question to you all is this: To which gcc version should we jump? I see
two viable candidates:
- gcc 4.9.2 (last updated October 2014)
or
- gcc 5.1 (last updated April 2015)
The current gcc
ISTR there being an old pull request in omnios-build for it. I can't just take
something like that in, but it may serve your needs.
Dan
Sent from my iPhone (typos, autocorrect, and all)
On May 18, 2015, at 9:23 PM, John D Groenveld jdg...@elvis.arl.psu.edu
wrote:
In message
18 matches
Mail list logo
