<div>Hello Avati:<br>I use the AFR function in glusterfs and get some trouble:<br>1. have 2 glusterfs-server, A-server and B-server, their config volume file is :<br>------------------------------------------------------------------------------------------------------<br>volume posix0<br> type storage/posix # POSIX FS translator<br> option directory /home/yzy/glusterfs/rundir/grundir/gdisk/s0 # Export this directory<br>end-volume<br><br>### Add POSIX record locking support to the storage brick<br>volume brick0<br> type features/posix-locks<br> option mandatory on # enables mandatory locking on all files<br> subvolumes posix0<br>end-volume<br><br>### Add network serving capability to above brick.<br>volume server<br> type protocol/server<br> option transport-type tcp/server # For TCP/IP transport<br> option listen-port 6995 # Default is 6996<br> subvolumes brick0<br> option auth.addr.brick0.allow * # access to "brick" volume<br>end-volume<br><br>the B-server's config file is similar with above information except "option directory" and "listen-port"<br>------------------------------------------------------------------------------------------------------<br>2. glusterfs client config volume file is :<br>------------------------------------------------------------------------------------------------------<br>### Add client feature and attach to remote subvolume of server1<br>volume client0<br> type protocol/client<br> option transport-type tcp/client # for TCP/IP transport<br> option remote-host 192.168.5.48 # IP address of the remote brick<br> option remote-port 6995 # default server port is 6996<br> option remote-subvolume brick0 # name of the remote volume<br>end-volume<br><br>### Add client feature and attach to remote subvolume of server2<br>volume client1<br> type protocol/client<br> option transport-type tcp/client # for TCP/IP transport<br> option remote-host 192.168.5.48 # IP address of the remote brick<br> option remote-port 6996 # default server port is 6996<br> option remote-subvolume brick1 # name of the remote volume<br>end-volume<br><br>## Add AFR (Automatic File Replication) feature.<br>volume afr<br> type cluster/afr<br> subvolumes client0 client1<br> option data_self_heal on<br> option metadata_self_heal on<br> option entry_self_heal on<br> option data_change_log on<br> option metadata_change_log on<br> option entry_change_log on<br>end-volume<br>------------------------------------------------------------------------------------------------------<br><br>I have some trouble about the AFR function as I met :<br>1. I set the "option data_self_heal on" option in client.vol, but why system log say :<br> "2009-04-02 13:45:41 W [glusterfsd.c:451:_log_if_option_is_invalid] afr: option 'data_self_heal' is not recognized"<br><br> why? my option information is incorrect? <br><br>2. I use the ext3 as the filesystem of glusterfs-server, and it support the xattr function, I done some test about the xattr :<br> root@yzy-ubuntu:/mnt# getfattr -d test1 <br> root@yzy-ubuntu:/mnt# setfattr -n user.comment -v 'xattr is working!' test1 <br> root@yzy-ubuntu:/mnt# getfattr -d test1 <br> # file: test1<br> user.comment="xattr is working!"<br><br> root@yzy-ubuntu:/mnt# <br><br>3. For test the Afr function, I done some test:<br> (1)I create a file in the glusterfs mountpoint, and write some information to this file.<br> (2)I down the A-server<br> (3)append some new information to the file<br> (4)restart the A-server<br> But the file's information is incorrect, the append information cannot be display as normal, instead of "@"<br> so, the AFR's self-heal function is invalid. why?<br><br> (5) I test the new file's xattr function, but I cannot get any xattr information:<br> #getfattr -d testfile<br><br>I need your help.<br>Thanks a lot of.<br><br>YZY<br> <br><br><br><br></div><br><!-- footer --><br><span title="neteasefooter"/><hr/>
<a href="http://email.163.com">网易邮箱，中国第一大电子邮件服务商</a>
</span>