Received: by 10.68.75.170 with SMTP id d10mr1148976pbw.6.1326466974291;
        Fri, 13 Jan 2012 07:02:54 -0800 (PST)
Path: lh20ni177764pbb.0!nntp.google.com!news1.google.com!news4.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Michael <michael_laaja...@yahoo.com>
Newsgroups: comp.unix.admin,comp.unix.solaris
Subject: Re: Lost ZFS zpool, Powermt claims the devices are fine
Date: Fri, 13 Jan 2012 16:02:52 +0100
Lines: 55
Message-ID: <9navctFg1uU1@mid.individual.net>
References: <je0326$jg6$1@dont-email.me> <1nndt8-p5e.ln1@mankeli.homeip.net> <je1vkv$s35$1@dont-email.me> <je223h$a12$1@dont-email.me> <je23jt$lrl$1@dont-email.me> <d511c4d5-752b-476c-8cc1-fd110324cd7b@d9g2000yqg.googlegroups.com> <je25ec$j25$5@dont-email.me> <je57rt$5vs$1@dont-email.me> <je7rdj$os3$1@reader1.panix.com> <92e5e7ab-55b1-42c0-8261-57ba46f75dd6@f33g2000yqh.googlegroups.com>
Mime-Version: 1.0
X-Trace: individual.net UCHRz76EQEP/NLFOVasgiQYHWbcklIzbrXX3PaJiZBkgtt0xKn
Cancel-Lock: sha1:rDc0iaYSHN7zdw+qysAXdVhDYJ8=
User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:9.0) Gecko/20111223 Thunderbird/9.0.1
In-Reply-To: <92e5e7ab-55b1-42c0-8261-57ba46f75dd6@f33g2000yqh.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

On 01/07/12 12:39 AM, cindy wrote:
> On Jan 6, 3:08 pm, Cydrome Leader<prese...@MUNGEpanix.com>  wrote:
>> In comp.unix.solaris Doug Freyburger<dfrey...@yahoo.com>  wrote:
>>
>>
><snip>

>>> Thanks so much for the help!  I owe several favors now so I'll stay
>>> subscribed to comp.unix.solaris in addition to comp.unix.admin.
>>
>> try veritas for your next filesystem. it doesn't explode like zfs does.
>>
>> It sounds weird that the world's best most awesome checksumming filesystem
>> could corrupted by bad memory and not warn you at all.
>
> The zpool status command warns you about corrupted data, fmdump,
> fmadm
> faulty, and you can use smtp-notify in OS 11 to send you an email
> notification
> of a fault or error.
>
> Doug had both LUN or LUNs? silently truncated and memory corruption
> so unfortunately, a 30 day health check wasn't enough. If his pool
> devices
> had still been available, he would have seen the corruption in zpool
> status.
>
> For a non-redundant config with underlying LUNs that might be managed
> by
> someone else, I would want to check more often, like weekly.
>
> cs
>
I had maybe a similar issue atleast according to Oracles support, a 
memory corruption that caused the pool to be impossible to import BUT I 
was lucky that I could import it readonly!

For my case I had hoped that since it was possible to import it in 
read-only that it would be also possible to have a zfs tool to make the 
fs well again!

Or atleast when importing the pool read-write not even reboot did work, 
I had to use mdb to force a reboot!

My fs is still in that state on the failing server in the hope for a zdb 
script that can recover the pool but the work to make such as script in 
not high priority at Oracle sadly.

Can you Cindy do something to escalate it perhaps? SR 3-4393435551 since 
I think all effort so recover a failing pool should be made!

/michael