Re: [Gluster-users] HELP : Files lost after DHT expansion

2009-07-05 Thread eagleeyes
The  server configuration file is:

gfs1:~ # cat /etc/glusterfs/glusterfsd-sever.vol 
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 posix5
  type storage/posix   # POSIX FS translator
  option directory /data/data5# Export this directory
end-volume
volume posix6
  type storage/posix   # POSIX FS translator
  option directory /data/data6# Export this directory
end-volume
volume posix7
  type storage/posix   # POSIX FS translator
  option directory /data/data7# Export this directory
end-volume
volume posix8
  type storage/posix   # POSIX FS translator
  option directory /data/data8# 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

volume brick5
  type features/posix-locks
  option mandatory-locks on  # enables mandatory locking on all files
  subvolumes posix5
end-volume

volume brick6
  type features/posix-locks
  option mandatory-locks on  # enables mandatory locking on all files
  subvolumes posix6
end-volume

volume brick7
  type features/posix-locks
  option mandatory-locks on  # enables mandatory locking on all files
  subvolumes posix7
end-volume

volume brick8
  type features/posix-locks
  option mandatory-locks on  # enables mandatory locking on all files
  subvolumes posix8
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  brick5 brick6 brick7 brick8
  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
option auth.addr.brick5.allow * # Allow access to "brick" volume
option auth.addr.brick6.allow * # Allow access to "brick" volume
option auth.addr.brick7.allow * # Allow access to "brick" volume
option auth.addr.brick8.allow * # Allow access to "brick" volume
end-volume


2009-07-06 



eagleeyes 



发件人: Sachidananda 
发送时间: 2009-07-04  11:39:03 
收件人: eagleeyes 
抄送: gluster-users 
主题: Re: [Gluster-users] HELP : Files lost after DHT expansion 
Hi,
eagleeyes wrote:
 > When i  update to gluster2.0.3 ,after dht expansion ,double  directorys
 > appear in the gluster directory ,why ?
 >
 > client configure
 > volume dht
 >   type cluster/dht
 >   option lookup-unhashed yes
 >   option min-free-disk 10%
 >   subvolumes client1 client2  client3 client4 client5 client6 client7 
client8
 >   #subvolumes client1 client2  client3 client4
 > end-volume
 >
 >
Can you please send us your server/client volume files?
--
Sachidananda.
___
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users


Re: [Gluster-users] HELP : Files lost after DHT expansion

2009-07-05 Thread eagleeyes
gfs1:~ # cat /etc/glusterfs/glusterfsd-sever.vol 
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 posix5
  type storage/posix   # POSIX FS translator
  option directory /data/data5# Export this directory
end-volume
volume posix6
  type storage/posix   # POSIX FS translator
  option directory /data/data6# Export this directory
end-volume
volume posix7
  type storage/posix   # POSIX FS translator
  option directory /data/data7# Export this directory
end-volume
volume posix8
  type storage/posix   # POSIX FS translator
  option directory /data/data8# 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


2009-07-06 



eagleeyes 



发件人: Sachidananda 
发送时间: 2009-07-04  11:39:03 
收件人: eagleeyes 
抄送: gluster-users 
主题: Re: [Gluster-users] HELP : Files lost after DHT expansion 
 
Hi,
eagleeyes wrote:
 > When i  update to gluster2.0.3 ,after dht expansion ,double  directorys
 > appear in the gluster directory ,why ?
 >
 > client configure
 > volume dht
 >   type cluster/dht
 >   option lookup-unhashed yes
 >   option min-free-disk 10%
 >   subvolumes client1 client2  client3 client4 client5 client6 client7 
client8
 >   #subvolumes client1 client2  client3 client4
 > end-volume
 >
 >
Can you please send us your server/client volume files?
--
Sachidananda.
___
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users


Re: [Gluster-users] HELP : Files lost after DHT expansion

2009-07-03 Thread Sachidananda

Hi,

eagleeyes wrote:
> When i  update to gluster2.0.3 ,after dht expansion ,double  directorys
> appear in the gluster directory ,why ?
>
> client configure
> volume dht
>   type cluster/dht
>   option lookup-unhashed yes
>   option min-free-disk 10%
>   subvolumes client1 client2  client3 client4 client5 client6 client7 
client8

>   #subvolumes client1 client2  client3 client4
> end-volume
>
>

Can you please send us your server/client volume files?

--
Sachidananda.

___
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users


Re: [Gluster-users] HELP : Files lost after DHT expansion

2009-07-03 Thread eagleeyes
When i  update to gluster2.0.3 ,after dht expansion ,double  directorys  appear 
in the gluster directory ,why ?

client configure
volume dht 
  type cluster/dht
  option lookup-unhashed yes
  option min-free-disk 10%
  subvolumes client1 client2  client3 client4 client5 client6 client7 client8 
  #subvolumes client1 client2  client3 client4
end-volume


2009-07-02 



eagleeyes 



发件人: Anand Babu Periasamy 
发送时间: 2009-07-01  13:41:20 
收件人: Anand Avati 
抄送: eagleeyes 
主题: Re: HELP : Files lost after DHT expansion 
2.0.3 is scheduled for release tomorrow evening PST.
--
Anand Babu Periasamy
GPG Key ID: 0x62E15A31
Blog [http://unlocksmith.org]
GlusterFS [http://www.gluster.org]
GNU/Linux [http://www.gnu.org]
Anand Avati wrote:
>> 
>> Sorry, it is a Intranet , just like what your say , the data is just
>> invisible on the mountpoint , when i designate file name , it will be
>> visible . But in Production environment ,this Phenomenon will make
>> some issue for applications.
>>
> 
> This problem is solved in 2.0.3. Please upgrade and you should be able to see 
> your files again.
> 
> Avati
___
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users


[Gluster-users] HELP !!!!!!Files lost after DHT expansion!!!!!!!!!!

2009-06-28 Thread eagleeyes
Hello all:
 I had a problem with  DHT expansion 
 When i expansion  DHT volumes ,After remounting the filesystem on the 
clients, a bunch of the content in the cluster 
became unavailable! i tried use "option lookup-unhashed on" and  " ls -aR " .  
but no effect ,Am I missing something obvious in the setup and procedure for a
DHT expansion?
 I saw there had some one met the problem like me ,were there a solution of 
it ? Who can help us ? waiting for your help ,thanks a lot 
 
MY change was from "subvolumes client1 client2  client3 client4 " to 
"subvolumes client1 client2  client3 client4 client5 client6 client7 client8 " 
for expansion DHT. 
 


2009-06-26 



eagleeyes 
___
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users