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
------------------------------------------------------------------------------------------------------
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?
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090402/5727ca24/attachment.html>
-------- 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: [Gluster-users] 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
?2009-04-02?14:31:11?Steve?<steeeeeveee at gmx.net>????> >--------?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:?[Gluster-users]?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 >Yes, Thanks, I correct this wrong. I done the AFR function again, but the self-heal function is still invalid.> >------------------------------------------------------------------------------------------------------ >>? >>?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 > >_______________________________________________ >Gluster-users?mailing?list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090402/afdba290/attachment.html>
> Yes, Thanks, I correct this wrong. > I done the AFR function again, but the self-heal function is still > invalid. >What do you mean with "self-heal function is invalid"? -- Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01
I append some information to a file under mountpoint after A-server down then I restart the A-server But the new append information is display as "@" in this file. If the "self-heal" function is ok, I think the file should be can be display as normal and file content is last change information, And A-server, B-server has some file and file content. But now the file in B-server is last change information and file content is ok, the file in A-server, the new append information be display as "@" ?2009-04-02?15:11:01?Steve?<steeeeeveee at gmx.net>????>>?Yes,?Thanks,?I?correct?this?wrong. >>?I?done?the?AFR?function?again,?but?the?self-heal?function?is?still >>?invalid. >>? >What?do?you?mean?with?"self-heal?function?is?invalid"? >--? >Psssst!?Schon?vom?neuen?GMX?MultiMessenger?geh?rt??Der?kann`s?mit?allen:?http://www.gmx.net/de/go/multimessenger01 > >_______________________________________________ >Gluster-users?mailing?list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090402/094769b9/attachment.html>
I use the AFR function in Glusterfs system : 1. Add a new server to Glusterfs system. 2. do the /bin/ls in mountpoint of client The new server have some files, and files size is same with files in other exist servers, but these files content is empty. so only the file name and file size is success with AFR function, but the file content isn't be fixed. And I cannot see any file xattr use the "getfattr -d filename" in all servers. anybody can explain this trouble? Thanks. YZY