your point have only a rethoric meaning. System breaks regardless the ressource
you put to build it. Bad hardware, typo, human mistakes, bugs, This
mailing-list is full of examples. Having some tools like zdb, mdb, zfs import
-fFX and labelfix for analyzis and repair is always a good thing.
I am running Nexenta NCP 3.0 (134f).
My stmf configuration was corrupted. I was getting errors like in
/var/adm/messages:
Sep 1 10:32:04 llift-zfs1 svc-stmf[378]: [ID 130283 user.error] get
property view_entry-0/all_hosts failed - entity not found
Sep 1 10:32:04 llift-zfs1 svc.startd[9]: [ID 6
Just to update everyone...this turned out to be OpenSolaris bug 6884007
"zfs_send() can leave temporary holds around". It was fixed in b142 and I was
able to apply the patch to NCP3 and the issue is resolved on my system.
Apparently the system was stuck in dnode_special_close() due to some snap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Bacon wrote:
> I have a bunch of sol10U8 boxes with ZFS pools, most all raidz2 8-disk
> stripe. They're all supermicro-based with retail LSI cards.
>
> I've noticed a tendency for things to go a little bonkers during the
> weekly scrub (they all
I have a file server that I've basically maxed out the drive bays for. At the
moment, I'm running Nexenta on an SSD that is sort of resting on something else
in the case. I was wondering if, instead, I could install Nexenta on a SATA
Disk on Module (DOM), say something like 4 GB, dual channel, S
31.08.2010 21:23, Ray Van Dolson пишет:
Here's an article with some benchmarks:
http://wikis.sun.com/pages/viewpage.action?pageId=186241353
Seems to really impact IOPS.
This is really interesting reading. Can someone do same tests with Intel
X25-E?
_
