On Aug 11, 2010, at 9:46 PM, Ville Ojamo wrote:
> I am having a similar issue at the moment.. 3 GB RAM under ESXi, but dedup
> for this zvol (1.2 T) was turned off and only 300 G was used. The pool does
> contain other datasets with dedup turned on but are small enough so I'm not
> hitting the
I am having a similar issue at the moment.. 3 GB RAM under ESXi, but dedup for
this zvol (1.2 T) was turned off and only 300 G was used. The pool does contain
other datasets with dedup turned on but are small enough so I'm not hitting the
memory limits (been there, tried that, never again withou
Just wanted to post a bit of closure to this thread quick...
Most of the "import taking too long threads" I've found on the list tend to
fade out without any definitive answer as to what went wrong. I needed
something a bit more concrete to make me happy.
After zfs send'ing everything to a fre
- Original Message -
> It's alive!! Some 20 hours after starting, the zpool import finished,
> and all data is alive & well.
>
> I ordered the extra RAM, so that'll no doubt help in the future. I'm
> also in the process of de-Xen'ing the server I had running under xVM,
> so Solaris will ge
It's alive!! Some 20 hours after starting, the zpool import finished, and all
data is alive & well.
I ordered the extra RAM, so that'll no doubt help in the future. I'm also in
the process of de-Xen'ing the server I had running under xVM, so Solaris will
get the whole 8GB to itself. Finall
- Original Message -
> Greetings, all!
>
> I've recently jumped into OpenSolaris after years of using Gentoo for
> my primary server OS, and I've run into a bit of trouble on my main
> storage zpool. Reading through the archives, it seems like the
> symptoms I'm seeing are fairly common th
For arc reasons if no other, I would max it out to the 8 gb regardless.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Alas the pool in question has a dozen odd other ZFS' that range in importance
from "nice to have" to "let's not even think about it".
On the bright side, at about 14 hours in, my lights are still blinken. Here's
hoping the +RAM and -xVM were the difference.
One related question: In the unfort
Assuming there are no other volumes sharing slices of those disk, why import?
Just over write the disk with a new pool using the f flag during creation.
I'm just sayin since you were destroying the volume anyway I presume there is
no data we are trying to preserve here.
--
This message posted f
