> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Paul Piscuc
>
> NAME STATE READ WRITE CKSUM
> zpool ONLINE 0 0 0
> raidz1-0 ONLINE 0 0 0
> c2t0d0 ONLINE 0
Here is a part of "fmdump -eV" :
Dec 19 2010 03:02:47.919024953 ereport.fs.zfs.probe_failure
nvlist version: 0
class = ereport.fs.zfs.probe_failure
ena = 0x4bd7543b8cf1
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
NexentaStor logs are in /var/log. But the real information of
interest is in the FMA ereports. fmdump -eV is your friend.
-- richard
On Dec 20, 2010, at 6:39 AM, Paul Piscuc wrote:
> Hi,
>
> The problem seems to be solved with a zpool clear. It is not clear what
> generated the issue, and I
Hi,
The problem seems to be solved with a zpool clear. It is not clear
what generated the issue, and I cannot locate what caused it, because a
reboot seems to have deleted all logs:| . I have issued serveral grep's
under /var/log, /var and now under /, but I could find any record. Also, I
thought
Also check your email. NexentaStor sends an email message
describing the actions taken when this occurs. If you did not
setup email for the appliance, then look in the NMS log.
-- richard
On Dec 20, 2010, at 5:33 AM, Khushil Dep wrote:
> Check the dmesg and system logs for any output concernin
Check the dmesg and system logs for any output concerning those devices
re-seat one then the other just in case too.
---
W. A. Khushil Dep - khushil@gmail.com - 07905374843
Visit my blog at http://www.khushil.com/
On 20 December 2010 13:10, Paul Piscuc wrote:
> Hi, this is current s
Hi, this is current setup that I have been doing tests on:
NAMESTATE READ WRITE CKSUM
zpool ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
c2t0d0 ONLINE 0 0 0
c2t1d0 ONLINE 0 0 0
