On Thu, Sep 07, 2006 at 06:31:30PM -0700, Darren Dunham wrote:
>
> It certainly changes some semantics...
>
> In a UFS/VxVM world, I still have filesystems referenced in /etc/vfstab.
> I might expect (although have seen counterexamples), that if my VxVM
> group doesn't autoimport, then obviously
On Thu, Sep 07, 2006 at 06:07:40PM -0700, Anton B. Rang wrote:
>
> And why would we want a pool imported on another host, or not marked
> as belonging to this host, to show up as faulted? That seems an odd
> use of the word. Unavailable, perhaps, but not faulted.
>
That's FMA terminology, and
> And why would we want a pool imported on another host, or not marked
> as belonging to this host, to show up as faulted? That seems an odd
> use of the word. Unavailable, perhaps, but not faulted.
It certainly changes some semantics...
In a UFS/VxVM world, I still have filesystems referenced i
A determined administrator can always get around any checks and cause problems.
We should do our very best to prevent data loss, though! This case is
particularly bad since simply booting a machine can permanently damage the pool.
And why would we want a pool imported on another host, or not mar
This could still corrupt the pool.
Probably the customer has to write its own tool to import a pool using libzfs
and not creating zpool.cache.
Eventually just after pool is imported remove zpool.cache - I'm not sure but it
should work.
This message posted from opensolaris.org
___
