In the example
<http://www.gluster.org/docs/index.php/Mixing_Unify_and_Stripe> the
unified brick is defined as:

> volume unify0
>   type cluster/unify
>   option scheduler switch
>   option switch.case *.dat:stripe0;*:remote1,remote2 # stripe only *.dat files
>   option namespace remote-ns
>   subvolumes remote1 remote2 afr0
> end-volume

In  this case how are the files that don't match "*.dat" distributed
across the remote1 and remote2 bricks.


-- 
Dr. Rodney G. McDuff                 |Ex ignorantia ad sapientiam
Manager, Strategic Technologies Group|    Ex luce ad tenebras
Information Technology Services      |
The University of Queensland         |
EMAIL: [EMAIL PROTECTED]          |
TELEPHONE: +61 7 3365 8220           |



_______________________________________________
Gluster-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/gluster-devel

Reply via email to