h the same error name.
On Mon, Dec 20, 2010 at 4:52 PM, Richard Elling wrote:
> 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 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
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
6:03 AM, Erik Trimble wrote:
> On 11/28/2010 1:51 PM, Paul Piscuc wrote:
>
>> Hi,
>>
>> We are a company that want to replace our current storage layout with one
>> that uses ZFS. We have been testing it for a month now, and everything looks
>> promising. On
Hi,
We are a company that want to replace our current storage layout with one
that uses ZFS. We have been testing it for a month now, and everything looks
promising. One element that we cannot determine is the optimum number of
disks in a raid-z pool. In the ZFS best practice guide, 7,9 and 11 di
