On Sat, Mar 27, 2010 at 10:03 PM, William Bauer <bqba...@gmail.com> wrote:
> Depends on a lot of things. I'd let it sit for at least half an hour to > see if you get any messages. 30 seconds, if it's waiting for the driver > stack timeouts, is way too short. > ----------------------------- > > I'm not the OP, but I let my VB guest sit for an hour now, and nothing new > has happened. The last thing it displayed was the "Hostname:" line, as the > original post stated. Personally, I've never seen an OpenSolaris system, > virtual or physical, take more than a few seconds to pause for a missing > mirror member. > > I did notice something a little odd--usually an OpenSolaris VB guest > doesn't use all of its allocated memory immediately, even after a user logs > into gnome. However, this seemingly idle system quickly ate up all of the > 2GB I allocated to it. The host is 2009.06 with 8GB memory and an Intel > quad Q6600, so I have adequate resources for this guest. > > > Sounds exactly like the behavior people have had previously while a system is trying to recover a pool with a faulted drive. I'll have to check and see if I can dig up one of those old threads. I vaguely recall someone here had a single drive fail on an import and it took forever to import the pool, running out of memory every time. I think he eventually added significantly more memory and was able to import the pool (of course my memory sucks, so I'm sure that's not quite accurate). --Tim
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
