On Tue, Sep 19, 2006 at 01:55:33PM +0200, Robert Milkowski wrote:
>
> What's the difference between -t and -R /
> ?
>
Basically nothing implementation-wise, except that you don't have the
weird notion 'alternate root=/', which doesn't really make any sense.
It's really just a clarification of be
Hello Eric,
Thursday, September 14, 2006, 7:48:48 PM, you wrote:
ES> On Thu, Sep 14, 2006 at 07:46:33AM -0700, Anton B. Rang wrote:
>>
>> It looks like 'zpool create -R' should solve the problem for anyone
>> who is trying to build their own clustering facility, since it
>> prevents the automati
On Thu, Sep 14, 2006 at 07:46:33AM -0700, Anton B. Rang wrote:
>
> It looks like 'zpool create -R' should solve the problem for anyone
> who is trying to build their own clustering facility, since it
> prevents the automatic import. Maybe we just need to document that
> more clearly? Calling it "a
Anton B. Rang wrote:
You need to rewrite/extend that to deal with the fact that ZFS doesn't use vfstab
and instead express it in terms of ZFS import/export.
The problem (as I see it) is that ZFS import is (by default) implicit at
startup, while UFS mount is (by default) only performed when exp
> You need to rewrite/extend that to deal with the fact that ZFS doesn't use
> vfstab
> and instead express it in terms of ZFS import/export.
The problem (as I see it) is that ZFS import is (by default) implicit at
startup, while UFS mount is (by default) only performed when explicitly
request
Mathias F wrote:
...
Yes it is, you got it ;) VxVM just notices that it's previously imported
DiskGroup(s) (for ZFS this is the Pool) were failed over and doesn't try to
re-acquire them. It waits for an admin action.
The topic of "clustering" ZFS is not the problem atm, we just test the
failover
Mathias F wrote:
I think I get the whole picture, let me summarise:
- you create a pool P and an FS on host A
- Host A crashes
- you import P on host B; this only works with -f, as
"zpool import" otherwise
refuses to do so.
- now P is imported on B
- host A comes back up and re-accesses P, the
> I think I get the whole picture, let me summarise:
>
> - you create a pool P and an FS on host A
> - Host A crashes
> - you import P on host B; this only works with -f, as
> "zpool import" otherwise
> refuses to do so.
> - now P is imported on B
> - host A comes back up and re-accesses P, there
