So I can manage the file system mounts/automounts using the legacy option ,
but I can't manage the auto-import of the pools . Or I should delete the
zpool.cache file during boot .
This message posted from opensolaris.org
___
zfs-discuss mailing
Lieven De Geyndt wrote:
So I can manage the file system mounts/automounts using the legacy option
, but I can't manage the auto-import of the pools . Or I should delete
the zpool.cache file during boot .
Doesn't this come back to the problem which is self-induced, namely
that they are trying
On September 7, 2006 6:55:48 PM +1000 James C. McPherson [EMAIL PROTECTED]
wrote:
Doesn't this come back to the problem which is self-induced, namely
that they are trying poor man's cluster ??
If you want cluster functionality then pay for a proper solution.
If you can't afford a proper
Lieven De Geyndt wrote:
I know this is not supported . But we try to build a safe configuration,
till zfs is supported in Sun cluster. The customer did order SunCluster,
but needs a workarround till the release date . And I think it must be
possible to setup .
So build them a configuration
On Thu, Sep 07, 2006 at 11:32:18AM -0700, Darren Dunham wrote:
I know that VxVM stores the autoimport information on the disk
itself. It sounds like ZFS doesn't and it's only in the cache (is this
correct?)
I'm not sure what 'autoimport' is, but ZFS always stores enough
information on the
On Thu, Sep 07, 2006 at 01:09:47PM -0700, Frank Cusack wrote:
That zfs needs to address.
What if I simply lose power to one of the hosts, and then power is restored?
Then use a layered clustering product - that's what this is for. For
example, SunCluster doesn't use the cache file in the
On Thu, Sep 07, 2006 at 01:52:33PM -0700, Darren Dunham wrote:
What are the problems that you see with that check? It appears similar
to what VxVM has been using (although they do not use the `hostid` as
the field), and that appears to have worked well in most cases.
I don't know what
Hi.
Just re-create it or create new pool with disks from the old one and use -f
flag.
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
zpool create -R did his job . Thanks for the tip .
Is ther a way to disable the auto mount when you boot a system ?
The customer has some kind of poor mans cluster .
2 systems has access to a SE3510 with ZFS .
System A was powered-off as test , system B did an import of the pools .
When system
Lieven De Geyndt wrote:
zpool create -R did his job . Thanks for the tip .
Is ther a way to disable the auto mount when you boot a system ?
The customer has some kind of poor mans cluster .
2 systems has access to a SE3510 with ZFS .
System A was powered-off as test , system B did an import
sorry guys ...RTF did the job
[b]Legacy Mount Points[/b]
You can manage ZFS file systems with legacy tools by setting the mountpoint
property to legacy.
Legacy file systems must be managed through the mount and umount commands and the
/etc/vfstab file. ZFS does not automatically mount legacy file
On September 6, 2006 7:19:32 AM -0700 Lieven De Geyndt [EMAIL PROTECTED]
wrote:
sorry guys ...RTF did the job
[b]Legacy Mount Points[/b]
That just means filesystems in the pool won't get mounted, not that the
pool won't be imported.
-frank
___
12 matches
Mail list logo
