Hi Thierry and all,

because I missed the RTFM (M = Maillinglist),
I opened a quite similar thread below.

I'd like to discuss the following a little bit more in depth:
> Storage node affinity is based on a top-down preference,
> Legato selecting next entry from the list
> if mount request cannot be satisfied.

IMHO Legato only selects the next entry in the storage node affinity list,
if the storage node is not reachable, etc.
>From my POV, that's not the case, if the "mount request cannot be 
satisfied" (i.e. all drives on storage node are busy).
If all drives on the 1st storage node are busy, the mount request
will be queued for one drive on THIS storage node and not rerouted
to the second storage node, etc.

Unfortunately I would like to have the other
(uses next storage node if 1st is busy) behavior,
but have not tested this yet 
(additional Storage node will go in production end of month)

Pls. correct me if I'm wrong.

Thx -sg-
--
Steffen Gattert; VISIOplant Hamburg

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER