comment below...
Robert Milkowski wrote:
Hello Richard,
Wednesday, November 1, 2006, 11:36:14 PM, you wrote:
REP> Adam Leventhal wrote:
On Wed, Nov 01, 2006 at 04:00:43PM -0500, Torrey McMahon wrote:
Lets say server A has the pool with NFS shared, or iSCSI shared,
volumes. Server A exports t
Hello Richard,
Wednesday, November 1, 2006, 11:36:14 PM, you wrote:
REP> Adam Leventhal wrote:
>> On Wed, Nov 01, 2006 at 04:00:43PM -0500, Torrey McMahon wrote:
>>> Lets say server A has the pool with NFS shared, or iSCSI shared,
>>> volumes. Server A exports the pool or goes down. Server B imp
Richard Elling - PAE wrote:
Adam Leventhal wrote:
On Wed, Nov 01, 2006 at 04:00:43PM -0500, Torrey McMahon wrote:
Lets say server A has the pool with NFS shared, or iSCSI shared,
volumes. Server A exports the pool or goes down. Server B imports the
pool.
Which clients would still be active
Cyril Plisko wrote:
> Can we do something similar to NFS case, where sharenfs can be
> "on", "off", or something else, in which case it is a list of options ?
> Would this technique be applicable to shareiscsi too ?
Absolutely. We would, however, like to be conservative about adding
options
