-------- Original-Nachricht -------- > Datum: Thu, 2 Apr 2009 14:13:31 +0800 (CST) > Von: glusterfs <glusterfs at 126.com> > An: avati at gluster.com, gluster-users at gluster.org, gluster-users-bounces at gluster.org > Betreff: AFR trouble in glusterfs > Hello Avati: > I use the AFR function in glusterfs and get some trouble: > 1. have 2 glusterfs-server, A-server and B-server, their config volume > file is : > ------------------------------------------------------------------------------------------------------ > volume posix0 > type storage/posix # POSIX FS translator > option directory /home/yzy/glusterfs/rundir/grundir/gdisk/s0 # Export > this directory > end-volume > > ### Add POSIX record locking support to the storage brick > volume brick0 > type features/posix-locks > option mandatory on # enables mandatory locking on all files > subvolumes posix0 > end-volume > > ### Add network serving capability to above brick. > volume server > type protocol/server > option transport-type tcp/server # For TCP/IP transport > option listen-port 6995 # Default is 6996 > subvolumes brick0 > option auth.addr.brick0.allow * # access to "brick" volume > end-volume > > the B-server's config file is similar with above information except > "option directory" and "listen-port" > ------------------------------------------------------------------------------------------------------ > 2. glusterfs client config volume file is : > ------------------------------------------------------------------------------------------------------ > ### Add client feature and attach to remote subvolume of server1 > volume client0 > type protocol/client > option transport-type tcp/client # for TCP/IP transport > option remote-host 192.168.5.48 # IP address of the remote brick > option remote-port 6995 # default server port is 6996 > option remote-subvolume brick0 # name of the remote volume > end-volume > > ### Add client feature and attach to remote subvolume of server2 > volume client1 > type protocol/client > option transport-type tcp/client # for TCP/IP transport > option remote-host 192.168.5.48 # IP address of the remote brick > option remote-port 6996 # default server port is 6996 > option remote-subvolume brick1 # name of the remote volume > end-volume > > ## Add AFR (Automatic File Replication) feature. > volume afr > type cluster/afr > subvolumes client0 client1 > option data_self_heal on > option metadata_self_heal on > option entry_self_heal on > option data_change_log on > option metadata_change_log on > option entry_change_log on > end-volume > Correct me if I am wrong, but should that not be (- instead of _): option data-self-heal on option metadata-self-heal on option entry-self-heal on option data-change-log on option metadata-change-log on option entry-change-log on ------------------------------------------------------------------------------------------------------ > > I have some trouble about the AFR function as I met : > 1. I set the "option data_self_heal on" option in client.vol, but why > system log say : > "2009-04-02 13:45:41 W [glusterfsd.c:451:_log_if_option_is_invalid] afr: > option 'data_self_heal' is not recognized" > > why? my option information is incorrect? > I think so. See above. > 2. I use the ext3 as the filesystem of glusterfs-server, and it support > the xattr function, I done some test about the xattr : > root at yzy-ubuntu:/mnt# getfattr -d test1 > root at yzy-ubuntu:/mnt# setfattr -n user.comment -v 'xattr is working!' > test1 > root at yzy-ubuntu:/mnt# getfattr -d test1 > # file: test1 > user.comment="xattr is working!" > > root at yzy-ubuntu:/mnt# > > 3. For test the Afr function, I done some test: > (1)I create a file in the glusterfs mountpoint, and write some > information to this file. > (2)I down the A-server > (3)append some new information to the file > (4)restart the A-server > But the file's information is incorrect, the append information > cannot be display as normal, instead of "@" > so, the AFR's self-heal function is invalid. why? > > (5) I test the new file's xattr function, but I cannot get any xattr > information: > #getfattr -d testfile > > I need your help. > Thanks a lot of. > > YZY > > > > -- Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01
