Hi Amar, thanks for prompt reply. I've tried space and comma with space between volume names and it didn't work :) is it possible that this option is overriden by some other alu options? I have the following configuration in unify translator: volume unify type cluster/unify subvolumes afr01 afr02 afr03 afr04 option namespace afrns option scheduler alu option alu.read-only-subvolumes afr02,afr03 option alu.limits.min-free-disk 5% option alu.stat-refresh.interval 10sec option alu.order disk-usage:read-usage:write-usage:open-files-usage:disk-speed-usage option alu.disk-usage.entry-threshold 1024M option alu.disk-usage.exit-threshold 32M end-volume if I initiate write operations, I see that afr02 and afr03's underlying file-systems are being used for file storage. 2008/9/5 Amar S. Tumballi <amar at zresearch.com>: > Try with 'option alu.read-only-subvolumes <volume1>,<volume2>,....' (note > the ',' between each volumes) > > > 2008/9/5 Roman Hlynovskiy <roman.hlynovskiy at gmail.com> >> >> Hi All, >> >> is it normal behaviour of alu, that it's option >> alu.read-only-subvolumes accepts only 1 volume? according to it's name >> it should accept several volumes. >> if I put 2 volumes it says: >> 2008-09-05 13:54:13 E [spec.y:75:cut_tree] parser: translator tree cut >> 2008-09-05 13:54:13 E [spec.y:228:yyerror] parser: syntax error (text >> which caused syntax error: afr03) >> 2008-09-05 13:54:13 E [spec.y:243:file_to_xlator_tree] parser: >> yyparser () exited with YYABORT >> 2008-09-05 13:54:13 E [glusterfs.c:190:xlator_graph_get] glusterfs: >> specification file parsing failed, exiting >> >> -- >> ...WBR, Roman Hlynovskiy >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users >> > > > > -- > Amar Tumballi > Gluster/GlusterFS Hacker > [bulde on #gluster/irc.gnu.org] > http://www.zresearch.com - Commoditizing Super Storage! > -- ...WBR, Roman Hlynovskiy
