So we finnaly got arround the problem, after replacing almost everything it
seems that the memory was the devil. I pulled it out and replaced it with ECC
memory and now everything works fine for 14 days already.
This knowing i will never putt non ecc memory in my boxes again.
thanks for al the
indeed that's one of the nice things that ZFS is picky on data and allerts you
immediatly. Before some files became corrupt and one was wondering what happend
and how this was possible since everything seems fine for months :)
the more i use solaris the more i love it :)
This message posted
This knowing i will never putt non ecc memory in my boxes again.
What's your mainboard and CPU? I've looked up the thread on the forum
and there's no hardware information. Don't be fooled just because the
RAM's ECC. The mainboard (and CPU in case of AMDs) have to support that.
There are two
On Mon, 28 Jul 2008, BG wrote:
indeed that's one of the nice things that ZFS is picky on data and
allerts you immediatly. Before some files became corrupt and one was
wondering what happend and how this was possible since everything
seems fine for months :)
Unfortunately, ZFS does not
Bob Friesenhahn wrote:
On Mon, 28 Jul 2008, BG wrote:
indeed that's one of the nice things that ZFS is picky on data and
allerts you immediatly. Before some files became corrupt and one was
wondering what happend and how this was possible since everything
seems fine for months :)
On Mon, 28 Jul 2008, Richard Elling wrote:
But ZFS can do better. I filed CR6674679 which basically says
that if redundant copies of data have the same, wrong checksum,
then ZFS should issue an e-report to that effect. This will allow
you to move suspicion away from the disks as a root
mainboard is :
KFN4-DRE
more info you find here :
http://www.asus.com/products.aspx?l1=9l2=39l3=174l4=0model=1844modelmenu=2
cpu:
2x opteron aMD Opteron 2350 2.0GHz HT 4MB SF
memory was cheap stuff non ecc replaced it with kingston ECC mem KVR667D2D8P5/2G
in the mean time we have 4x500Gb in
Bob Friesenhahn wrote:
On Mon, 28 Jul 2008, Richard Elling wrote:
But ZFS can do better. I filed CR6674679 which basically says
that if redundant copies of data have the same, wrong checksum,
then ZFS should issue an e-report to that effect. This will allow
you to move suspicion away from
On Mon, 28 Jul 2008, Richard Elling wrote:
It is not clear to me where ARC validation occurs. Perhaps someone
who deals with the ARC code could shed some light.
More than likely, ARC data is not stored using original filesystem
blocks so the existing filesystem block checksums are not
mainboard is :
KFN4-DRE
more info you find here :
http://www.asus.com/products.aspx?l1=9l2=39l3=174l4=0model=1844modelmenu=2
cpu:
2x opteron aMD Opteron 2350 2.0GHz HT 4MB SF
You'll be fine with that. Just had to make sure.
Regards,
-mg
signature.asc
Description: OpenPGP digital
We already have memory scrubbers which check memory. Actually,
we've had these for about 10 years, but it only works for ECC
memory... if you have only parity memory, then you can't fix anything
at the hardware level, and the best you can hope is that FMA will do
the right thing.
In
Mario Goebbels wrote:
We already have memory scrubbers which check memory. Actually,
we've had these for about 10 years, but it only works for ECC
memory... if you have only parity memory, then you can't fix anything
at the hardware level, and the best you can hope is that FMA will do
the
Hi thanks for you help in the forum help i got an answer also iam gonna try
that. But your suggestion is also an angle with i will investigate. Is there
maybo some diagnostic tool in opensolaris i can use, or shall i use the solaris
bootable cd that inspects of my hw is fully compitble ?
There's nothing I know of I'm afraid, I'm too new to Solaris to have looked
into things that deeply.
If you have access to any spare parts, the easiest way to test is to swop
things over and see if the problem is reproducable. It could even be something
as simple as a struggling power supply.
Hi
I too strongly suspect that some HW component is failing. It is rare to see all
drives (in your case both drives in mirror and the boot drive) reporting errors
at same time.
zfs clear just resets the error counters. You still have got errors in there.
Start with following components (in
Hi
running all kinds of tools now even a tool for my hd from WD, so we will she
what the results are.
I ordered another mobo this morning and if that doesn't work then i will ask a
fellow sysop to punt my disk in his solaris array.
No i didn't notice anything of kernel panics the only thing
Trying the disks in another machine is a great step, it will eliminate those
quickly. Use your own cables too so you can eliminate them from suspicion.
If this is hardware related, from my own experience I would say it's most
likely to be (in order):
- Power Supply
- Memory (especially if
Hi everyone,
i did a nice install of opensolaris and i pulled 2x500 gig sata disk in a zpool
mirror.
Everything went well and i got it so that my mirror called datatank got shared
by using CIFS. I can access it from my macbook and pc.
So with this nice setup i started to put my files on but
On Tue, Jul 8, 2008 at 2:56 PM, BG [EMAIL PROTECTED] wrote:
Hi everyone,
i did a nice install of opensolaris and i pulled 2x500 gig sata disk in a
zpool mirror.
Everything went well and i got it so that my mirror called datatank got
shared by using CIFS. I can access it from my macbook and
i removed the files that were corrupted,scrubbed the datatank mirror and the
did status -v datatank and i got this :
pool: datatank
state: DEGRADED
status: One or more devices has experienced an unrecoverable error. An
attempt was made to correct the error. Applications are
20 matches
Mail list logo
