<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=GB2312">
<META content="MSHTML 6.00.6000.16850" 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>How could i remove one of fuse
?</FONT></DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080>client 1</FONT></DIV>
<DIV><FONT color=#000080>2.6.30 </FONT></DIV>
<DIV>
<DIV>gfs1:~ # dmesg | grep -i fuse</DIV>
<DIV>fuse init (API version 7.11)</DIV></DIV><FONT
color=#000080>
<DIV>gfs1:~ # grep -i FUSE_MINOR_VERSION /usr/local/include/fuse/fuse_common.h </DIV>
<DIV>#define FUSE_MINOR_VERSION 7</DIV>
<DIV>#define FUSE_VERSION FUSE_MAKE_VERSION(FUSE_MAJOR_VERSION, FUSE_MINOR_VERSION)</DIV>
<DIV># undef FUSE_MINOR_VERSION</DIV>
<DIV># define FUSE_MINOR_VERSION 5</DIV>
<DIV># define FUSE_MINOR_VERSION 4</DIV>
<DIV># define FUSE_MINOR_VERSION 1</DIV>
<DIV># define FUSE_MINOR_VERSION 1</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>client 2</DIV>
<DIV>2.6.16.21-0.8-smp </DIV></FONT>
<DIV>
<DIV>linux-2ca1:~ # dmesg | grep -i fuse </DIV>
<DIV>fuse: module not supported by Novell, setting U taint flag.</DIV>
<DIV>fuse init (API version 7.6)</DIV></DIV>
<DIV><FONT color=#000080>
<DIV>linux-2ca1:~ # grep -i FUSE_MINOR_VERSION /usr/local/include/fuse/fuse_common.h </DIV>
<DIV>#define FUSE_MINOR_VERSION 8</DIV>
<DIV>#define FUSE_VERSION FUSE_MAKE_VERSION(FUSE_MAJOR_VERSION, FUSE_MINOR_VERSION)</DIV>
<DIV># undef FUSE_MINOR_VERSION</DIV>
<DIV># define FUSE_MINOR_VERSION 5</DIV>
<DIV># define FUSE_MINOR_VERSION 4</DIV>
<DIV># define FUSE_MINOR_VERSION 1</DIV>
<DIV># define FUSE_MINOR_VERSION 1</DIV></FONT></DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080></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-07-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> Harshavardhana
</FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>发送时间：</STRONG> 2009-07-06 17:18:34
</FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>收件人：</STRONG> eagleeyes </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>抄送：</STRONG> Anand Avati; gluster-users
</FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>主题：</STRONG> Re: [Gluster-users] Error :
gluster2.0.3rc1 with fuse2.8 inkernel2.6.30 ,help !!!!! </FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV><FONT face=Verdana size=2>Eagleyes,<BR><BR> I think you are
using glusterfs with two different versions of fuse API versions. API versions
for 2.6.30 kernel are not compatible with 2.6.16-21 version. I would suggest you
to use same fuse API versions for glusterfs. Can i have a few details
<BR><BR>1. dmesg | grep -i fuse (on each clients)<BR>2. grep -i
FUSE_MINOR_VERSION /usr/include/fuse/fuse_common.h (on each
clients)<BR><BR>Regards<BR>--<BR clear=all>Harshavardhana<BR>Z Research Inc <A
href="http://www.zresearch.com/">http://www.zresearch.com/</A><BR><BR><BR>
<DIV class=gmail_quote>On Mon, Jul 6, 2009 at 12:31 PM, eagleeyes <SPAN
dir=ltr><<A href="mailto:eagleeyes@126.com">eagleeyes@126.com</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV style="FONT-SIZE: 10pt; MARGIN: 10px; FONT-FAMILY: verdana">
<DIV><FONT face=Verdana color=#000080 size=2>HI </FONT></DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080> 1. I use gluster2.0.3rc2 with
fuse init (API version 7.11) in SUSE sp10 ,kernel
2.6.30.</FONT></DIV>
<DIV><FONT color=#000080>There were some error log
:</FONT></DIV>
<DIV>
<DIV>pending frames:</DIV>
<DIV>frame : type(1) op(WRITE)</DIV>
<DIV>frame : type(1) op(READ)</DIV>
<DIV>frame : type(1) op(READ)</DIV>
<DIV>frame : type(1) op(READ)</DIV>
<DIV></DIV>
<DIV>patchset: 65524f58b29f0b813549412ba6422711a505f5d8</DIV>
<DIV class=im>
<DIV>signal received: 11</DIV>
<DIV>configuration details:argp 1</DIV>
<DIV>backtrace 1</DIV>
<DIV>dlfcn 1</DIV>
<DIV>fdatasync 1</DIV>
<DIV>libpthread 1</DIV>
<DIV>llistxattr 1</DIV>
<DIV>setfsid 1</DIV>
<DIV>spinlock 1</DIV>
<DIV>epoll.h 1</DIV>
<DIV>xattr.h 1</DIV>
<DIV>st_atim.tv_nsec 1</DIV></DIV>
<DIV>package-string: glusterfs 2.0.3rc2</DIV>
<DIV>[0xffffe400]</DIV>
<DIV>/usr/local/lib/libfuse.so.2(fuse_session_process+0x26)[0xb752fb56]</DIV>
<DIV>/lib/glusterfs/2.0.3rc2/xlator/mount/fuse.so[0xb755de25]</DIV>
<DIV>/lib/libpthread.so.0[0xb7f0d2ab]</DIV>
<DIV>/lib/libc.so.6(__clone+0x5e)[0xb7ea4a4e]</DIV>
<DIV>---------</DIV>
<DIV> 2. Use glusterfs 2.0.3rc2 with
fuse init (API version 7.6) in suse
sp10, kernel 2.6.16.21-0.8-smp ,</DIV>
<DIV>when i expanded dht volumes from four to six ,then i "rm *"
in gluster directory , there were some error :</DIV>
<DIV>
<DIV>[2009-07-06 22:56:23] W [fuse-bridge.c:921:fuse_unlink_cbk] glusterfs-fuse: 1636: RMDIR() /scheduler => -1 (No such file or directory)</DIV>
<DIV>[2009-07-06 22:56:23] W [fuse-bridge.c:921:fuse_unlink_cbk] glusterfs-fuse: 1643: RMDIR() /transport => -1 (No such file or directory)</DIV>
<DIV>[2009-07-06 22:56:23] W [fuse-bridge.c:921:fuse_unlink_cbk] glusterfs-fuse: 1655: RMDIR() /xlators/cluster => -1 (No such file or directory)</DIV>
<DIV>[2009-07-06 22:56:23] W [fuse-bridge.c:921:fuse_unlink_cbk] glusterfs-fuse: 1666: RMDIR() /xlators/debug => -1 (No such file or directory)</DIV>
<DIV>[2009-07-06 22:56:23] W [fuse-bridge.c:921:fuse_unlink_cbk] glusterfs-fuse: 1677: RMDIR() /xlators/mount => -1 (No such file or directory)
</DIV>
<DIV> </DIV>
<DIV> and new files didn't write into the new volumes after
expansion .</DIV></DIV>
<DIV> </DIV>
<DIV> </DIV></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-07-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><B>发件人：</B> Anand Avati </FONT></DIV>
<DIV><FONT face=Verdana size=2><B>发送时间：</B> 2009-07-06 12:09:13
</FONT></DIV>
<DIV class=im>
<DIV><FONT face=Verdana size=2><B>收件人：</B> eagleeyes </FONT></DIV>
<DIV><FONT face=Verdana size=2><B>抄送：</B> gluster-users </FONT></DIV></DIV>
<DIV><FONT face=Verdana size=2><B>主题：</B> Re: [Gluster-users] Error :
gluster2.0.3rc1 with fuse2.8 in kernel2.6.30 ,help !!!!! </FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT></DIV>
<DIV><FONT face=Verdana size=2>
<DIV class=im>
<DIV>Please use 2.0.3 stable, or upgrade to the next rc2 until then. This</DIV>
<DIV>has been fixed in rc2.</DIV>
<DIV></DIV>
<DIV>Avati</DIV>
<DIV></DIV>
<DIV>On Mon, Jul 6, 2009 at 8:31 AM, eagleeyes<<A
href="mailto:eagleeyes@126.com"
target=_blank>eagleeyes@126.com</A>> wrote:</DIV></DIV>
<DIV>
<DIV></DIV>
<DIV class=h5>
<DIV>> HI</DIV>
<DIV>> I use gluster2.0.3rc1 with fuse 2.8 in kernel</DIV>
<DIV>> 2.6.30(SUSE Linux Enterprise Server 10 SP1 with kernel 2.6.30 ) . the mount</DIV>
<DIV>> message was :</DIV>
<DIV>></DIV>
<DIV>> /dev/hda4 on /data type reiserfs (rw,user_xattr)</DIV>
<DIV>> glusterfs-client.vol.dht on /home type fuse.glusterfs (rw,allow_other,default_permissions,max_read=131072)</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> There was some error when i "touce 111" in gluster directory ,the error was</DIV>
<DIV>> :</DIV>
<DIV>> /home: Transport endpoint is not connected</DIV>
<DIV>></DIV>
<DIV>> pending frames:</DIV>
<DIV>> patchset: e0db4ff890b591a58332994e37ce6db2bf430213</DIV>
<DIV>> signal received: 11</DIV>
<DIV>> configuration details:argp 1</DIV>
<DIV>> backtrace 1</DIV>
<DIV>> dlfcn 1</DIV>
<DIV>> fdatasync 1</DIV>
<DIV>> libpthread 1</DIV>
<DIV>> llistxattr 1</DIV>
<DIV>> setfsid 1</DIV>
<DIV>> spinlock 1</DIV>
<DIV>> epoll.h 1</DIV>
<DIV>> xattr.h 1</DIV>
<DIV>> st_atim.tv_nsec 1</DIV>
<DIV>> package-string: glusterfs 2.0.3rc1</DIV>
<DIV>> [0xffffe400]</DIV>
<DIV>> /lib/glusterfs/2.0.3rc1/xlator/mount/fuse.so[0xb75c6288]</DIV>
<DIV>> /lib/glusterfs/2.0.3rc1/xlator/performance/write-behind.so(wb_create_cbk+0xa7)[0xb75ccad7]</DIV>
<DIV>> /lib/glusterfs/2.0.3rc1/xlator/performance/io-cache.so(ioc_create_cbk+0xde)[0xb7fbe8ae]</DIV>
<DIV>> /lib/glusterfs/2.0.3rc1/xlator/performance/read-ahead.so(ra_create_cbk+0x167)[0xb7fc78b7]</DIV>
<DIV>> /lib/glusterfs/2.0.3rc1/xlator/cluster/dht.so(dht_create_cbk+0xf7)[0xb75e25b7]</DIV>
<DIV>> /lib/glusterfs/2.0.3rc1/xlator/protocol/client.so(client_create_cbk+0x2ad)[0xb76004ad]</DIV>
<DIV>> /lib/glusterfs/2.0.3rc1/xlator/protocol/client.so(protocol_client_interpret+0x1ef)[0xb75ef8ff]</DIV>
<DIV>> /lib/glusterfs/2.0.3rc1/xlator/protocol/client.so(protocol_client_pollin+0xcf)[0xb75efaef]</DIV>
<DIV>> /lib/glusterfs/2.0.3rc1/xlator/protocol/client.so(notify+0x1ec)[0xb75f6ddc]</DIV>
<DIV>> /lib/glusterfs/2.0.3rc1/transport/socket.so(socket_event_poll_in+0x3b)[0xb75b775b]</DIV>
<DIV>> /lib/glusterfs/2.0.3rc1/transport/socket.so(socket_event_handler+0xae)[0xb75b7b8e]</DIV>
<DIV>> /lib/libglusterfs.so.0[0xb7facbda]</DIV>
<DIV>> /lib/libglusterfs.so.0(event_dispatch+0x21)[0xb7fabac1]</DIV>
<DIV>> glusterfs(main+0xc2e)[0x804b6ae]</DIV>
<DIV>> /lib/libc.so.6(__libc_start_main+0xdc)[0xb7e6087c]</DIV>
<DIV>> glusterfs[0x8049c11]</DIV>
<DIV>> ---------</DIV>
<DIV>></DIV>
<DIV>> the server configuration</DIV>
<DIV>></DIV>
<DIV>> gfs1:/ # cat /etc/glusterfs/glusterfsd-sever.vol</DIV>
<DIV>> volume posix1</DIV>
<DIV>> type storage/posix # POSIX FS translator</DIV>
<DIV>> option directory /data/data1 # Export this directory</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume posix2</DIV>
<DIV>> type storage/posix # POSIX FS translator</DIV>
<DIV>> option directory /data/data2 # Export this directory</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume posix3</DIV>
<DIV>> type storage/posix # POSIX FS translator</DIV>
<DIV>> option directory /data/data3 # Export this directory</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume posix4</DIV>
<DIV>> type storage/posix # POSIX FS translator</DIV>
<DIV>> option directory /data/data4 # Export this directory</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume posix5</DIV>
<DIV>> type storage/posix # POSIX FS translator</DIV>
<DIV>> option directory /data/data5 # Export this directory</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume posix6</DIV>
<DIV>> type storage/posix # POSIX FS translator</DIV>
<DIV>> option directory /data/data6 # Export this directory</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume posix7</DIV>
<DIV>> type storage/posix # POSIX FS translator</DIV>
<DIV>> option directory /data/data7 # Export this directory</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume posix8</DIV>
<DIV>> type storage/posix # POSIX FS translator</DIV>
<DIV>> option directory /data/data8 # Export this directory</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume brick1</DIV>
<DIV>> type features/posix-locks</DIV>
<DIV>> option mandatory-locks on # enables mandatory locking on all files</DIV>
<DIV>> subvolumes posix1</DIV>
<DIV>> end-volume</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>> volume brick3</DIV>
<DIV>> type features/posix-locks</DIV>
<DIV>> option mandatory-locks on # enables mandatory locking on all files</DIV>
<DIV>> subvolumes posix3</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume brick4</DIV>
<DIV>> type features/posix-locks</DIV>
<DIV>> option mandatory-locks on # enables mandatory locking on all files</DIV>
<DIV>> subvolumes posix4</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume brick5</DIV>
<DIV>> type features/posix-locks</DIV>
<DIV>> option mandatory-locks on # enables mandatory locking on all files</DIV>
<DIV>> subvolumes posix5</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume brick6</DIV>
<DIV>> type features/posix-locks</DIV>
<DIV>> option mandatory-locks on # enables mandatory locking on all files</DIV>
<DIV>> subvolumes posix6</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume brick7</DIV>
<DIV>> type features/posix-locks</DIV>
<DIV>> option mandatory-locks on # enables mandatory locking on all files</DIV>
<DIV>> subvolumes posix7</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume brick8</DIV>
<DIV>> type features/posix-locks</DIV>
<DIV>> option mandatory-locks on # enables mandatory locking on all files</DIV>
<DIV>> subvolumes posix8</DIV>
<DIV>> end-volume</DIV>
<DIV>> ### Add network serving capability to above brick.</DIV>
<DIV>> volume server</DIV>
<DIV>> type protocol/server</DIV>
<DIV>> option transport-type tcp</DIV>
<DIV>> option transport.socket.bind-address 172.20.92.240 # Default is to listen on all interfaces</DIV>
<DIV>> option transport.socket.listen-port 6996 # Default is 6996</DIV>
<DIV>> subvolumes brick1 brick2 brick3 brick4</DIV>
<DIV>> option auth.addr.brick1.allow * # Allow access to "brick" volume</DIV>
<DIV>> option auth.addr.brick2.allow * # Allow access to "brick" volume</DIV>
<DIV>> option auth.addr.brick3.allow * # Allow access to "brick" volume</DIV>
<DIV>> option auth.addr.brick4.allow * # Allow access to "brick" volume</DIV>
<DIV>> option auth.addr.brick5.allow * # Allow access to "brick" volume</DIV>
<DIV>> option auth.addr.brick6.allow * # Allow access to "brick" volume</DIV>
<DIV>> option auth.addr.brick7.allow * # Allow access to "brick" volume</DIV>
<DIV>> option auth.addr.brick8.allow * # Allow access to "brick" volume</DIV>
<DIV>> end-volume</DIV>
<DIV>></DIV>
<DIV>> the client configuration:</DIV>
<DIV>></DIV>
<DIV>> gfs1:/ # cat /etc/glusterfs/glusterfs-client.vol.dht</DIV>
<DIV>> volume client1</DIV>
<DIV>> type protocol/client</DIV>
<DIV>> option transport-type tcp</DIV>
<DIV>> option remote-host 172.20.92.240 # IP address of the remote brick2</DIV>
<DIV>> option remote-port 6996</DIV>
<DIV>> option remote-subvolume brick1 # name of the remote volume</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume client2</DIV>
<DIV>> type protocol/client</DIV>
<DIV>> option transport-type tcp</DIV>
<DIV>> option remote-host 172.20.92.240 # IP address of the remote brick2</DIV>
<DIV>> option remote-port 6996</DIV>
<DIV>> #option transport-timeout 10 # seconds to wait for a reply</DIV>
<DIV>> option remote-subvolume brick2 # name of the remote volume</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume client3</DIV>
<DIV>> type protocol/client</DIV>
<DIV>> option transport-type tcp</DIV>
<DIV>> option remote-host 172.20.92.240 # IP address of the remote brick2</DIV>
<DIV>> option remote-port 6996</DIV>
<DIV>> #option transport-timeout 10 # seconds to wait for a reply</DIV>
<DIV>> option remote-subvolume brick3 # name of the remote volume</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume client4</DIV>
<DIV>> type protocol/client</DIV>
<DIV>> option transport-type tcp</DIV>
<DIV>> option remote-host 172.20.92.240 # IP address of the remote brick2</DIV>
<DIV>> option remote-port 6996</DIV>
<DIV>> #option transport-timeout 10 # seconds to wait for a reply</DIV>
<DIV>> option remote-subvolume brick4 # name of the remote volume</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume client5</DIV>
<DIV>> type protocol/client</DIV>
<DIV>> option transport-type tcp</DIV>
<DIV>> option remote-host 172.20.92.240 # IP address of the remote brick2</DIV>
<DIV>> option remote-port 6996</DIV>
<DIV>> #option transport-timeout 10 # seconds to wait for a reply</DIV>
<DIV>> option remote-subvolume brick1 # name of the remote volume</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume client6</DIV>
<DIV>> type protocol/client</DIV>
<DIV>> option transport-type tcp</DIV>
<DIV>> option remote-host 172.20.92.240 # IP address of the remote brick2</DIV>
<DIV>> option remote-port 6996</DIV>
<DIV>> #option transport-timeout 10 # seconds to wait for a reply</DIV>
<DIV>> option remote-subvolume brick2 # name of the remote volume</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume client7</DIV>
<DIV>> type protocol/client</DIV>
<DIV>> option transport-type tcp</DIV>
<DIV>> option remote-host 172.20.92.240 # IP address of the remote brick2</DIV>
<DIV>> option remote-port 6996</DIV>
<DIV>> #option transport-timeout 10 # seconds to wait for a reply</DIV>
<DIV>> option remote-subvolume brick3 # name of the remote volume</DIV>
<DIV>> end-volume</DIV>
<DIV>> volume client8</DIV>
<DIV>> type protocol/client</DIV>
<DIV>> option transport-type tcp</DIV>
<DIV>> option remote-host 172.20.92.240 # IP address of the remote brick2</DIV>
<DIV>> option remote-port 6996</DIV>
<DIV>> #option transport-timeout 10 # seconds to wait for a reply</DIV>
<DIV>> option remote-subvolume brick4 # name of the remote volume</DIV>
<DIV>> end-volume</DIV>
<DIV>> #volume afr3</DIV>
<DIV>> # type cluster/afr</DIV>
<DIV>> # subvolumes client3 client6</DIV>
<DIV>> #end-volume</DIV>
<DIV>> volume dht</DIV>
<DIV>> type cluster/dht</DIV>
<DIV>> option lookup-unhashed yes</DIV>
<DIV>> subvolumes client1 client2 client3 client4</DIV>
<DIV>> end-volume</DIV>
<DIV>></DIV>
<DIV>> Could you help me ?</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> 2009-07-06</DIV>
<DIV>> ________________________________</DIV>
<DIV>> eagleeyes</DIV>
<DIV>> ________________________________</DIV>
<DIV>> 发件人： Sachidananda</DIV>
<DIV>> 发送时间： 2009-07-04 11:39:03</DIV>
<DIV>> 收件人： eagleeyes</DIV>
<DIV>> 抄送： gluster-users</DIV>
<DIV>> 主题： Re: [Gluster-users] HELP : Files lost after DHT expansion</DIV>
<DIV>> Hi,</DIV>
<DIV>> eagleeyes wrote:</DIV>
<DIV>> > When i update to gluster2.0.3 ,after dht expansion ,double directorys</DIV>
<DIV>> > appear in the gluster directory ，why ？</DIV>
<DIV>> ></DIV>
<DIV>> > client configure</DIV>
<DIV>> > volume dht</DIV>
<DIV>> > type cluster/dht</DIV>
<DIV>> > option lookup-unhashed yes</DIV>
<DIV>> > option min-free-disk 10%</DIV>
<DIV>> > subvolumes client1 client2 client3 client4 client5 client6 client7</DIV>
<DIV>> client8</DIV>
<DIV>> > #subvolumes client1 client2 client3 client4</DIV>
<DIV>> > end-volume</DIV>
<DIV>> ></DIV>
<DIV>> ></DIV>
<DIV>> Can you please send us your server/client volume files?</DIV>
<DIV>> --</DIV>
<DIV>> Sachidananda.</DIV></DIV></DIV>
<DIV class=im>
<DIV>> _______________________________________________</DIV>
<DIV>> Gluster-users mailing list</DIV>
<DIV>> <A href="mailto:Gluster-users@gluster.org"
target=_blank>Gluster-users@gluster.org</A></DIV>
<DIV>> <A
href="http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users"
target=_blank>http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</A></DIV>
<DIV>></DIV>
<DIV>></DIV></DIV></FONT></DIV></DIV><BR>_______________________________________________<BR>Gluster-users
mailing list<BR><A
href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</A><BR><A
href="http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users"
target=_blank>http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</A><BR><BR></BLOCKQUOTE></DIV><BR></FONT></DIV></BODY></HTML>