Hi,
I did a quick test (because I'm curious also). The Hardware was a 3 SATA Disk
RaidZ1.
What I did:
1) Create a pool with NexentaStor 3.0.4 (Pool Version 26, Raidz1 with 3 disks)
2) Disabled all caching (primarycache=none, secondarycache=none) to force media
access
3) Copied and extracted
On 18/11/2010 17:53, Cindy Swearingen wrote:
Markus,
Let me correct/expand this:
1. If you create a RAIDZ pool on OS 11 Express (b151a), you will have
some mirrored metadata. This feature integrated into b148 and the pool
version is 29. This is the part I mixed up.
2. If you have an existing
2. If you have an existing RAIDZ pool and upgrade to b151a, you would
need to upgrade the pool version to use this feature. In this case,
newly written metadata would be mirrored.
Hi,
And if one creates raid-z3 pool would meta-data be a 3-way mirror as well?
Also, how are devices
Hi, I'm referring to;
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6977913
It should be in Solaris 11 Express, has anyone tried this? How this is supposed
to work? Any documentation available?
Yours
Markus Kovero
___
zfs-discuss mailing
Hi Markus,
Jeff Bonwick integrated this feature so I'll let him describe it.
In a nutshell:
If you create a RAIDZ pool in OS 11 Express or if you are running at
least build 129, some of the pool metadata is mirrored automatically.
This is a performance feature that should increase read I/O
Markus,
Let me correct/expand this:
1. If you create a RAIDZ pool on OS 11 Express (b151a), you will have
some mirrored metadata. This feature integrated into b148 and the pool
version is 29. This is the part I mixed up.
2. If you have an existing RAIDZ pool and upgrade to b151a, you would
I'm still confused.
What is a -SAFE- way with two drives if you prepare for hardware
faulure? That is: one drive fails and the system does not go down
because the other drive takes over. Do I need raid or mirror?
--
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
++ http://nagual.nl/ + SunOS sxce
Hi Dick
You want Mirroring. A Sun system with mirrored disks can be configured to
not go down due to one disk failing. For this to be valid, you need to also
make sure that the device used for SWAP is mirrored - you won't believe how
many times I've seen this mistake being made.
To be even
jh == Johan Hartzenberg [EMAIL PROTECTED] writes:
jh To be even MORE safe, you want the two disks to be on separate
jh controllers, so that you can survive a controller failure too.
or a controller-driver-failure. At least on Linux, when a disk goes
bad, Linux starts resetting
