[Gluster-users] Error when expand dht model volumes

eagleeyes eagleeyes at 126.com
Fri Jun 26 08:03:59 UTC 2009


HI all:
    I met a problem in expending dht volumes,  i write in a dht storage directory untile it grew up to  90%,so i add four new volumes into the configur file.
   But when start again ,the data in directory  some disappeared ,Why ???  Was there a special  action before expending the volumes?
   
my client cofigure file is this :
volume client1
  type protocol/client
  option transport-type tcp
  option remote-host 172.20.92.240        # IP address of the remote brick2
  option remote-port 6996
  option remote-subvolume brick1       # name of the remote volume
end-volume
volume client2
  type protocol/client
  option transport-type tcp
  option remote-host 172.20.92.240         # IP address of the remote brick2
  option remote-port 6996
  #option transport-timeout 10          # seconds to wait for a reply
  option remote-subvolume brick2       # name of the remote volume
end-volume
volume client3
  type protocol/client
  option transport-type tcp
  option remote-host 172.20.92.240      # IP address of the remote brick2
  option remote-port 6996
  #option transport-timeout 10          # seconds to wait for a reply
  option remote-subvolume brick3       # name of the remote volume
end-volume
volume client4
  type protocol/client
  option transport-type tcp
  option remote-host 172.20.92.240      # IP address of the remote brick2
  option remote-port 6996
  #option transport-timeout 10          # seconds to wait for a reply
  option remote-subvolume brick4       # name of the remote volume
end-volume
volume client5
  type protocol/client
  option transport-type tcp
  option remote-host 172.20.92.184      # IP address of the remote brick2
  option remote-port 6996
  #option transport-timeout 10          # seconds to wait for a reply
  option remote-subvolume brick1       # name of the remote volume
end-volume
volume client6
  type protocol/client
  option transport-type tcp
  option remote-host 172.20.92.184      # IP address of the remote brick2
  option remote-port 6996
  #option transport-timeout 10          # seconds to wait for a reply
  option remote-subvolume brick2       # name of the remote volume
end-volume
volume client7
  type protocol/client
  option transport-type tcp
  option remote-host 172.20.92.184      # IP address of the remote brick2
  option remote-port 6996
  #option transport-timeout 10          # seconds to wait for a reply
  option remote-subvolume brick3       # name of the remote volume
end-volume
volume client8
  type protocol/client
  option transport-type tcp
  option remote-host 172.20.92.184      # IP address of the remote brick2
  option remote-port 6996
  #option transport-timeout 10          # seconds to wait for a reply
  option remote-subvolume brick4       # name of the remote volume
end-volume

volume dht 
  type cluster/dht
  #option lookup-unhashed yes
  option min-free-disk 10%
  subvolumes client1 client2  client3 client4 client5 client6 client7 client8 
end-volume
 
My server configure file is this:
volume posix1
  type storage/posix                   # POSIX FS translator
  option directory /data/data1        # Export this directory
end-volume
volume posix2
  type storage/posix                   # POSIX FS translator
  option directory /data/data2        # Export this directory
end-volume
volume posix3
  type storage/posix                   # POSIX FS translator
  option directory /data/data3        # Export this directory
end-volume
volume posix4
  type storage/posix                   # POSIX FS translator
  option directory /data/data4        # Export this directory
end-volume
volume brick1
  type features/posix-locks
  option mandatory-locks on          # enables mandatory locking on all files
  subvolumes posix1
end-volume
volume brick2
  type features/posix-locks
  option mandatory-locks on          # enables mandatory locking on all files
  subvolumes posix2
end-volume
volume brick3
  type features/posix-locks
  option mandatory-locks on          # enables mandatory locking on all files
  subvolumes posix3
end-volume
volume brick4
  type features/posix-locks
  option mandatory-locks on          # enables mandatory locking on all files
  subvolumes posix4
end-volume
### Add network serving capability to above brick.
volume server
  type protocol/server
  option transport-type tcp
  option transport.socket.bind-address 172.20.92.240     # Default is to listen on all interfaces
  option transport.socket.listen-port 6996              # Default is 6996
  subvolumes brick1 brick2 brick3 brick4 
  option auth.addr.brick1.allow * # Allow access to "brick" volume
  option auth.addr.brick2.allow * # Allow access to "brick" volume
  option auth.addr.brick3.allow * # Allow access to "brick" volume
  option auth.addr.brick4.allow * # Allow access to "brick" volume
end-volume
26 



eagleeyes 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090626/e8a48ebf/attachment.html>


More information about the Gluster-users mailing list