Boyd and all,
Just an update of what happened and what the customer found out
regarding the issue.
===
It does appear that the disk is fill up by 140G.
I think I now know what happen. I created a raidz pool and I did not
write any data to it before I just pulled out
On Thu, Aug 24, 2006 at 10:12:12AM -0600, Arlina Goce-Capiral wrote:
It does appear that the disk is fill up by 140G.
So this confirms what I was saying, that they are only able to write
ndisks-1 worth of data (in this case, ~68GB * (3-1) == ~136GB. So there
is no unexpected behavior with
I need help on this and don't know what to give to customer.
System is V40z running Solaris 10 x86 and customer is trying to create 3
disks as Raidz. After creating the pool,
looking at the disk space and configuration, he thinks that this is not
raidz pool but rather
stripes. THis is what
On 8/23/06, Arlina Goce-Capiral [EMAIL PROTECTED] wrote:
I need help on this and don't know what to give to customer.
System is V40z running Solaris 10 x86 and customer is trying to create 3
disks as Raidz. After creating the pool,
looking at the disk space and configuration, he thinks that
Hello James,
Thanks for the response.
Yes. I got the bug id# and forwarded that to customer. But cu said that
he can create a large file
that is large as the stripe of the 3 disks. And if he pull a disk, the
whole zpool failes, so there's no
degraded pools, just fails.
Any idea on this?
On 24/08/2006, at 10:14 AM, Arlina Goce-Capiral wrote:
Hello James,
Thanks for the response.
Yes. I got the bug id# and forwarded that to customer. But cu said
that he can create a large file
that is large as the stripe of the 3 disks. And if he pull a disk,
the whole zpool failes, so
