<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.6000.16809" name=GENERATOR>
<STYLE>@font-face {
        font-family: 宋体;
}
@font-face {
        font-family: Verdana;
}
@font-face {
        font-family: @宋体;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; layout-grid: 15.6pt; }
P.MsoNormal {
        TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
LI.MsoNormal {
        TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
DIV.MsoNormal {
        TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
        FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: Verdana; TEXT-DECORATION: none; mso-style-type: personal-compose
}
DIV.Section1 {
        page: Section1
}
UNKNOWN {
        FONT-SIZE: 10pt
}
BLOCKQUOTE {
        MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
        MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
        MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>
</HEAD>
<BODY style="FONT-SIZE: 10pt; MARGIN: 10px; FONT-FAMILY: verdana">
<DIV><FONT face=Verdana color=#000080 size=2>Thanks a lot ,i will try
again </FONT></DIV>
<DIV><FONT face=Verdana color=#000080 size=2></FONT> </DIV>
<DIV><FONT face=Verdana color=#000080 size=2></FONT> </DIV>
<DIV><FONT face=Verdana color=#c0c0c0 size=2>2009-03-06 </FONT></DIV><FONT
face=Verdana color=#000080 size=2>
<HR style="WIDTH: 100px" align=left color=#b5c4df SIZE=1>
</FONT>
<DIV><FONT face=Verdana color=#c0c0c0 size=2><SPAN>eagleeyes</SPAN>
</FONT></DIV>
<HR color=#b5c4df SIZE=1>
<DIV><FONT face=Verdana size=2><STRONG>发件人:</STRONG> Io Noci </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>发送时间:</STRONG> 2009-03-06 03:01:03
</FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>收件人:</STRONG> gluster-users </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>抄送:</STRONG> eagleeyes </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>主题:</STRONG> Re: [Gluster-users] question
of Replicate(GFS 2.0) </FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV><FONT face=Verdana size=2>
<DIV>hi,</DIV>
<DIV>keep your config file as simple as possible for testing.</DIV>
<DIV>your first mentioned config file seems ok to me. the second one is too</DIV>
<DIV>overloaded for testing.</DIV>
<DIV>your debuglogs from "DEBUG log for replicate" and "What was the matter</DIV>
<DIV>with my GFS 2.0 " seems ok, just 2 warnings and the rest are debugs.</DIV>
<DIV></DIV>
<DIV>please reduced the not needed options to the minumum. then try following</DIV>
<DIV>steps !only if you are in a testing enviroment, this will kill all</DIV>
<DIV>exported data! :</DIV>
<DIV></DIV>
<DIV>* stop all gluster stuff</DIV>
<DIV>* clear all posix filesystems using mkfs</DIV>
<DIV>* use your first mentioned server and client config</DIV>
<DIV>* mount rep1 by</DIV>
<DIV> 'glusterfs -f /etc/glusterfs/glusterfs.vol --volume-name=rep1 /data'</DIV>
<DIV>* write some files to /data and check for the existence and content of</DIV>
<DIV>the files on both node</DIV>
<DIV>* umount and redo the two steps above again for rep2 and rep-ns</DIV>
<DIV>* if all seems to be ok, stop gluster stuff again and cleanup filesystems</DIV>
<DIV>* mount bricks to /data, write some files to /data</DIV>
<DIV>* check how the files get distributed and replicated.</DIV>
<DIV>* stop one gluster-service, remove the file in the posix filesystm of</DIV>
<DIV>the node, start the gluster-service again.</DIV>
<DIV>* do a 'find /data -type f -print0 | xargs -0 head -c1' and check how</DIV>
<DIV>the posix filesystem on the stopped node gots populated again.</DIV>
<DIV>* when you reached this step without any error your gfs seems to bee ok</DIV>
<DIV>to me ;-)</DIV>
<DIV></DIV>
<DIV>hope it works out</DIV>
<DIV></DIV>
<DIV>Io Noci</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>eagleeyes schrieb:</DIV>
<DIV>> Thanks ,but which you mention was i missing when writing mail ,not</DIV>
<DIV>> lossing in my server's config .</DIV>
<DIV>> Are there some else wrong ?</DIV>
<DIV>> Did you have seen my mail about "What was the matter with my GFS 2.0 "</DIV>
<DIV>> its content was DEBUG log what i grabbed,could you help me ?</DIV>
<DIV>> </DIV>
<DIV>> The DEBUG log like this</DIV>
<DIV>> </DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep-ns: no range check required for 'option metadata-lock-server-</DIV>
<DIV>> count 2'</DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep-ns: no range check required for 'option entry-lock-server-cou</DIV>
<DIV>> nt 2'</DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep-ns: no range check required for 'option data-lock-server-coun</DIV>
<DIV>> t 2'</DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep2: no range check required for 'option metadata-lock-server-co</DIV>
<DIV>> unt 2'</DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep2: no range check required for 'option entry-lock-server-count</DIV>
<DIV>> 2'</DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep2: no range check required for 'option data-lock-server-count </DIV>
<DIV>> 2'</DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep1: no range check required for 'option metadata-lock-server-co</DIV>
<DIV>> unt 2'</DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep1: no range check required for 'option entry-lock-server-count</DIV>
<DIV>> 2'</DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep1: no range check required for 'option data-lock-server-count </DIV>
<DIV>> 2'</DIV>
<DIV>> 2009-03-04 16:16:47 D [client-protocol.c:6221:init] client1: setting transport-timeout to 5</DIV>
<DIV>> 2009-03-04 16:16:47 D [client-protocol.c:6235:init] client1: defaulting ping-timeout to 10</DIV>
<DIV>> 2009-03-04 16:16:47 D [transport.c:141:transport_load] transport: attempt to load file /lib/glusterfs/2.0.0rc2/transport/socket.so</DIV>
<DIV>> 2009-03-04 16:16:47 W [xlator.c:426:validate_xlator_volume_options] client1: option 'transport.socket.remote-port' is deprecated, pr</DIV>
<DIV>> eferred is 'remote-port', continuing with correction</DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] client1: no range check required for 'option remote-port 6996'</DIV>
<DIV>> 2009-03-04 16:16:47 D [transport.c:141:transport_load] transport: attempt to load file /lib/glusterfs/2.0.0rc2/transport/socket.so</DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] client1: no range check required for 'option remote-port 6996'</DIV>
<DIV>> 2009-03-04 16:16:47 D [xlator.c:595:xlator_init_rec] client1: Initialization done</DIV>
<DIV>> </DIV>
<DIV>> " no range check required for " meant what ? and the</DIV>
<DIV>> option 'transport.socket.remote-port' is deprecated ?? </DIV>
<DIV>> Why ? i modify configuration files use options which its own . </DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> 2009-03-05</DIV>
<DIV>> ------------------------------------------------------------------------</DIV>
<DIV>> eagleeyes</DIV>
<DIV>> ------------------------------------------------------------------------</DIV>
<DIV>> *发件人:* Io Noci</DIV>
<DIV>> *发送时间:* 2009-03-05 03:31:26</DIV>
<DIV>> *收件人:* eagleeyes</DIV>
<DIV>> *抄送:*</DIV>
<DIV>> *主题:* Re: [Gluster-users] question of Replicate(GFS 2.0)</DIV>
<DIV>> see inline at volume-repns, perhaps thats all.</DIV>
<DIV>> eagleeyes schrieb:</DIV>
<DIV>>> Hello :</DIV>
<DIV>>> I have some question of Replicate ,when i use tow servers and one</DIV>
<DIV>>> client , the configuration files are these :</DIV>
<DIV>>> </DIV>
<DIV>>> GFS server 1 and 2</DIV>
<DIV>>> glusterfsd.vol</DIV>
<DIV>>> =======================================================</DIV>
<DIV>>> volume posix1</DIV>
<DIV>>> type storage/posix # POSIX FS translator</DIV>
<DIV>>> option directory /data1 # Export this directory</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> </DIV>
<DIV>>> volume posix2</DIV>
<DIV>>> type storage/posix # POSIX FS translator</DIV>
<DIV>>> option directory /data2 # Export this directory</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> ### Add POSIX record locking support to the storage brick</DIV>
<DIV>>> volume brick1</DIV>
<DIV>>> type features/posix-locks</DIV>
<DIV>>> #option mandatory-locks on # enables mandatory locking on all</DIV>
<DIV>>> files</DIV>
<DIV>>> subvolumes posix1</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> </DIV>
<DIV>>> volume brick2</DIV>
<DIV>>> type features/posix-locks</DIV>
<DIV>>> #option mandatory-locks on # enables mandatory locking on all files</DIV>
<DIV>>> subvolumes posix2</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> </DIV>
<DIV>>> volume ns</DIV>
<DIV>>> type storage/posix # POSIX FS translator</DIV>
<DIV>>> option directory /export # Export this directory</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> </DIV>
<DIV>>> volume name</DIV>
<DIV>>> type features/posix-locks</DIV>
<DIV>>> #option mandatory-locks on # enables mandatory locking on all</DIV>
<DIV>>> files</DIV>
<DIV>>> subvolumes ns</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> </DIV>
<DIV>>> ### Add network serving capability to above brick.</DIV>
<DIV>>> volume server</DIV>
<DIV>>> type protocol/server</DIV>
<DIV>>> option transport-type tcp # For TCP/IP transport</DIV>
<DIV>>> subvolumes brick1 brick2 name</DIV>
<DIV>>> option auth.addr.brick1.allow * # access to "brick" volume</DIV>
<DIV>>> option auth.addr.brick2.allow * # access to "brick" volume</DIV>
<DIV>>> option auth.addr.name.allow * # access to "brick" volume</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> =================================================================</DIV>
<DIV>>> GFS client</DIV>
<DIV>>> volume client1</DIV>
<DIV>>> type protocol/client</DIV>
<DIV>>> option transport-type tcp # for TCP/IP transport</DIV>
<DIV>>> option remote-host 172.20.92.249 # IP address of the remote brick</DIV>
<DIV>>> option remote-subvolume brick1 # name of the remote volume</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> ### Add client feature and attach to remote subvolume of server2</DIV>
<DIV>>> volume client2</DIV>
<DIV>>> type protocol/client</DIV>
<DIV>>> option transport-type tcp # for TCP/IP transport</DIV>
<DIV>>> option remote-host 172.20.92.249 # IP address of the remote brick</DIV>
<DIV>>> option remote-subvolume brick2 # name of the remote volume</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> </DIV>
<DIV>>> volume client3</DIV>
<DIV>>> type protocol/client</DIV>
<DIV>>> option transport-type tcp # for TCP/IP transport</DIV>
<DIV>>> option remote-host 172.20.92.250 # IP address of the remote brick</DIV>
<DIV>>> option remote-subvolume brick1 # name of the remote volume</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> volume client4</DIV>
<DIV>>> type protocol/client</DIV>
<DIV>>> option transport-type tcp # for TCP/IP transport</DIV>
<DIV>>> option remote-host 172.20.92.250 # IP address of the remote brick</DIV>
<DIV>>> option remote-subvolume brick2 # name of the remote volume</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> </DIV>
<DIV>>> volume ns1 </DIV>
<DIV>>> type protocol/client</DIV>
<DIV>>> option transport-type tcp # for TCP/IP transport</DIV>
<DIV>>> option remote-host 172.20.92.249 # IP address of the remote brick</DIV>
<DIV>>> option remote-subvolume name # name of the remote volume</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> volume ns2 </DIV>
<DIV>>> type protocol/client</DIV>
<DIV>>> option transport-type tcp # for TCP/IP transport</DIV>
<DIV>>> option remote-host 172.20.92.250 # IP address of the remote brick</DIV>
<DIV>>> option remote-subvolume name # name of the remote volume</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> </DIV>
<DIV>>> ## Add replicate feature.</DIV>
<DIV>>> volume rep1</DIV>
<DIV>>> type cluster/replicate</DIV>
<DIV>>> subvolumes client1 client3</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> </DIV>
<DIV>>> volume rep2</DIV>
<DIV>>> type cluster/replicate</DIV>
<DIV>>> subvolumes client2 client4 </DIV>
<DIV>>> end-volume</DIV>
<DIV>>> </DIV>
<DIV>>> volume rep-ns</DIV>
<DIV>>> type cluster/replicate</DIV>
<DIV>> missing subvolumes ns1 ns2</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> </DIV>
<DIV>>> volume bricks</DIV>
<DIV>>> type cluster/unify</DIV>
<DIV>>> option namespace rep-ns # this will not be storage child of unify.</DIV>
<DIV>>> subvolumes rep1 rep2</DIV>
<DIV>>> option self-heal background # foreground off # default is foreground</DIV>
<DIV>>> option scheduler rr</DIV>
<DIV>>> end-volume</DIV>
<DIV>>> ========================================================================</DIV>
<DIV>>> glusterfs -f /etc/glusterfs/glusterfs.vol /data </DIV>
<DIV>>> </DIV>
<DIV>>> After mount ,I touch 11 22 33 44 four files into /data ,for the</DIV>
<DIV>>> Replicate,four files are both exist in 92.249 and 92.250</DIV>
<DIV>>> On GFS client I echo "aaaaaaaaaaaaaaa" > 11 ,then on 92.249 i rm -fr</DIV>
<DIV>>> /data1/11 , just like the file was lost. So on client I couldn't read</DIV>
<DIV>>> 11 correct, I " ll -h ",the file is appear again in 92.249,but have</DIV>
<DIV>>> not the right "aaaaaaaaaaaaaaa",it was like "@@@@@@@@@@@" messy code !</DIV>
<DIV>>> If i copy 11 from 92.250 to 92.249, on GFS client I read the right file</DIV>
<DIV>>> "aaaaaaaaaaaaaaa" . Was that my configuring wrong ? why the file not</DIV>
<DIV>>> renew accurate?</DIV>
<DIV>>> </DIV>
<DIV>>> </DIV>
<DIV>>> </DIV>
<DIV>>> 2009-03-04</DIV>
<DIV>>> ------------------------------------------------------------------------</DIV>
<DIV>>> eagleeyes</DIV>
<DIV>>> </DIV>
<DIV>>> </DIV>
<DIV>>> </DIV>
<DIV>>> ------------------------------------------------------------------------</DIV>
<DIV>>> </DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> Gluster-users mailing list</DIV>
<DIV>>> Gluster-users@gluster.org</DIV>
<DIV>>> http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</DIV>
<DIV></DIV></FONT></DIV></BODY></HTML>