[Gluster-users] install glustefs2.02 on freebsd

2009-06-24 Thread 郝洪标
who is useing glusterfs 2.02 on freebsd 7.3? 
I install glusterfs2.0.2 on freebsd 7.3

make -C /usr/ports/sysutils/fusefs-kmod install clean
make -C /usr/ports/devel/bison install clean
make -C  /usr/ports/databases/db47/  install clean
echo 'fusefs_enable="YES"'>>/etc/rc.conf 
bash
export CFLAGS="-march=nocona -O2 -pipe -fomit-frame-pointer" 
export CXXFLAGS="-march=nocona -O2 -pipe -fomit-frame-pointer"
export LDFLAGS=”-L/usr/local/lib -liconv”
export CFLAGS=”-I/usr/local/include/”
./configure --enable-fuse-client --enable-bdb --enable-libglusterfsclient  
--prefix=/usr/local/glusterfs
/*
GlusterFS configure summary
===
FUSE client: yes
Infiniband verbs   : no
epoll IO multiplex : no
Berkeley-DB: no
libglusterfsclient : no
mod_glusterfs  : no (2.0)
argp-standalone: yes
*/
make
make install
ln -s /usr/local/glusterfs/sbin/glusterfs* /bin/


glusterfs -f www-c-photo.vol /mnt/ 

# df -h /mnt/
FilesystemSizeUsed   Avail Capacity  Mounted on
/dev/fuse06.4T2.6T3.8T41%/mnt

# ls
ls: .: Socket is not connected
# pwd
/mnt

the glusterfs server is centos4.6 and  this www-c-photo.vol useing on centos 
4.6 is  ok

what's wrong?



# cat www-c-photo.vol 
client41
volume client41-ns
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.141 # IP address of the remote brick 
option remote-port 6990 # default server port is 6996 
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client41-1
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.141 # IP address of the remote brick 
option remote-port 6991 # default server port is 6996 
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client41-2
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.141 # IP address of the remote brick 
option remote-port 6992 # default server port is 6996 
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client41-3
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.141 # IP address of the remote brick 
option remote-port 6993 # default server port is 6996 
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client41-4
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.141 # IP address of the remote brick 
option remote-port 6994 # default server port is 6996 
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client41-5
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.141 # IP address of the remote brick
option remote-port 6995 # default server port is 6996
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client41-6
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.141 # IP address of the remote brick
option remote-port 6996 # default server port is 6996
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client41-7
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.141 # IP address of the remote brick
option remote-port 6997 # default server port is 6996
option remote-subvolume brick
option ping-timeout 240
end-volume
client64 
volume client64-ns
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.164 # IP address of the remote brick
option remote-port 6990 # default server port is 6996
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client64-1
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.164 # IP address of the remote brick
option remote-port 6991 # default server port is 6996
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client64-2
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.164 # IP address of the remote brick
option remote-port 6992 # default server port is 6996
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client64-3
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.164 # IP address of the remote brick
option remote-port 6993 # default server port is 6996
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client64-4
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.164 # IP address of the remote brick
option remote-port 6994 # default server port is 6996
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client64-5
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184.164 # IP address of the remote brick
option remote-port 6995 # default server port is 6996
option remote-subvolume brick
option ping-timeout 240
end-volume
volume client64-6
type protocol/client
option transport-type tcp/client
option remote-host 10.15.184

Re: [Gluster-users] Gluster (2.0.1 -> git) with fuse 2.8 crashes NFS

2009-06-24 Thread Justice London
Here you go. Let me know if you need anything else:

Core was generated by `/usr/local/sbin/glusterfsd
-p /var/run/glusterfsd.pid -f /etc/glusterfs/gluster'.
Program terminated with signal 11, Segmentation fault.
[New process 653]
[New process 656]
[New process 687]
[New process 657]
[New process 658]
[New process 659]
[New process 660]
[New process 661]
[New process 662]
[New process 663]
[New process 665]
[New process 666]
[New process 667]
[New process 668]
[New process 669]
[New process 670]
[New process 671]
[New process 672]
[New process 679]
[New process 680]
[New process 681]
[New process 682]
[New process 683]
[New process 684]
[New process 686]
[New process 676]
[New process 685]
[New process 674]
[New process 675]
[New process 677]
[New process 654]
[New process 673]
[New process 678]
[New process 664]
#0  0xb808ee9c in __glusterfs_this_locat...@plt ()
   from /usr/local/lib/libglusterfs.so.0
(gdb) backtrace
#0  0xb808ee9c in __glusterfs_this_locat...@plt ()
   from /usr/local/lib/libglusterfs.so.0
#1  0xb809b935 in default_fxattrop (frame=0x809cc68, this=0x8055a80, 
fd=0x809ca20, flags=GF_XATTROP_ADD_ARRAY, dict=0x809cac8)
at defaults.c:1122
#2  0xb809b930 in default_fxattrop (frame=0x8063570, this=0x8055f80, 
fd=0x809ca20, flags=GF_XATTROP_ADD_ARRAY, dict=0x809cac8)
at defaults.c:1122
#3  0xb76b3c35 in server_fxattrop (frame=0x809cc28, bound_xl=0x8055f80, 
hdr=0x8064c88, hdrlen=150, iobuf=0x0) at server-protocol.c:4596
#4  0xb76a9f1b in protocol_server_interpret (this=0x8056500,
trans=0x8064698, 
hdr_p=0x8064c88 "", hdrlen=150, iobuf=0x0) at server-protocol.c:7502
#5  0xb76aa1cc in protocol_server_pollin (this=0x8056500,
trans=0x8064698)
at server-protocol.c:7783
#6  0xb76aa24f in notify (this=0x8056500, event=2, data=0x8064698)
at server-protocol.c:7839
#7  0xb809737f in xlator_notify (xl=0x8056500, event=2, data=0x8064698)
at xlator.c:912
#8  0xb4ea08dd in socket_event_poll_in (this=0x8064698) at socket.c:713
#9  0xb4ea099b in socket_event_handler (fd=8, idx=1, data=0x8064698, 
poll_in=1, poll_out=0, poll_err=0) at socket.c:813
#10 0xb80b168a in event_dispatch_epoll (event_pool=0x8050d58) at
event.c:804
#11 0xb80b0471 in event_dispatch (event_pool=0x8051338) at event.c:975
---Type  to continue, or q  to quit---
#12 0x0804b880 in main (argc=5, argv=0xbfae1044) at glusterfsd.c:1263
Current language:  auto; currently asm


Justice London
jlon...@lawinfo.com

On Mon, 2009-06-22 at 10:47 +0530, Harshavardhana wrote:
> Hi Justice,
> 
>  Can you get a backtrace from the segfault through gdb? . 
> 
> Regards
> --
> Harshavardhana
> Z Research Inc http://www.zresearch.com/
> 
> 
> On Sat, Jun 20, 2009 at 10:47 PM,  wrote:
> Sure, the kernel version is 2.6.29 and the fuse release is the
> just
> released 2.8.0-pre3 (although I can use pre2 if needed).
> 
> 
> Justice London
> jlon...@lawinfo.com
> 
> > Hi Justice,
> >
> >  There are certain modifications required in
> fuse-extra.c to make
> > glusterfs work properly for fuse 2.8.0 release. glusterfs
> 2.0.1 release is
> > not tested against 2.8.0 release fuse and certainly will not
> work without
> > those modifications.  May i know the kernel version you are
> trying to use?
> > and the version of fuse being under use? pre1 or pre2
> release?
> >
> > Regards
> > --
> > Harshavardhana
> > Z Research Inc http://www.zresearch.com/
> >
> >
> > On Fri, Jun 19, 2009 at 11:14 PM, Justice London
> > wrote:
> >
> >>  No matter what I do I cannot seem to get gluster to stay
> stable when
> >> doing any sort of writes to the mount, when using gluster
> in combination
> >> with fuse 2.8.0-preX and NFS. I tried both unfs3 and
> standard kernel-nfs
> >> and
> >> no matter what, any sort of data transaction seems to crash
> gluster
> >> immediately. The error log is as such:
> >>
> >>
> >>
> >> pending frames:
> >>
> >>
> >>
> >> patchset: git://git.sv.gnu.org/gluster.git
> >>
> >> signal received: 11
> >>
> >> configuration details:argp 1
> >>
> >> backtrace 1
> >>
> >> bdb->cursor->get 1
> >>
> >> db.h 1
> >>
> >> dlfcn 1
> >>
> >> fdatasync 1
> >>
> >> libpthread 1
> >>
> >> llistxattr 1
> >>
> >> setfsid 1
> >>
> >> spinlock 1
> >>
> >> epoll.h 1
> >>
> >> xattr.h 1
> >>
> >> st_atim.tv_nsec 1
> >>
> >> package-string: glusterfs 2.0.0git
> >>
> >> [0xf57fe400]
> >>
> >> 

Re: [Gluster-users] Permissions on mount point

2009-06-24 Thread Scruffy Poo
On Wed, Jun 17, 2009 at 3:25 PM, Marcio
Teixeira wrote:
> However, even though I set the permissions to 1777 on the mount point, once
> that mount is established, the permissions change and I do not know where
> those permissions are coming from. Is there any way to override those
> default permissions?

If I might ask, did you set these permissions while gluster was
mounted on the mount point, or did you do this without the mount
having been established?  Also, is the glusterfs process running as
root in this scenario, or is it running as a low-priority user?

Ess

-- 
SO not teh 1337

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


Re: [Gluster-users] Limit of Glusterfs help

2009-06-24 Thread eagleeyes
Thanks
  Another question :
   1.  in  glusterfs-2.0.2/xlators/cluster  i saw a mode named "map",could we 
use it ? what should we do? 
   2.  in glusterfs-2.0.0/xlators/features  there was a "trash" ,and if we  
want to use it ,what should we do ? 
   3.  Could you give us a whole parameter for configure for server and client 
? i found if i use page-size  and page-count  the log it show they didn't 
effect .


2009-06-24 



eagleeyes 



发件人: Vikas Gorur 
发送时间: 2009-06-24  15:47:27 
收件人: eagleeyes 
抄送: gluster-users 
主题: Re: [Gluster-users] Limit of Glusterfs help 
 
- "eagleeyes"  wrote:
> Thanks a lot, but in unify ,dht and stripe mode  ,is there a limit of
> the number of servers ?
No.
--
Engineer - http://gluster.com/
A: Because it messes up the way people read text.
Q: Why is a top-posting such a bad thing?
--
___
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users


Re: [Gluster-users] Limit of Glusterfs help

2009-06-24 Thread Vikas Gorur

- "eagleeyes"  wrote:

> Thanks a lot, but in unify ,dht and stripe mode  ,is there a limit of
> the number of servers ?

No.
--
Engineer - http://gluster.com/

A: Because it messes up the way people read text.
Q: Why is a top-posting such a bad thing?
--

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


Re: [Gluster-users] Limit of Glusterfs help

2009-06-24 Thread eagleeyes
 Thanks a lot, but in unify ,dht and stripe mode  ,is there a limit of the 
number of servers ?


2009-06-24 



eagleeyes 



发件人: Vikas Gorur 
发送时间: 2009-06-24  15:17:55 
收件人: eagleeyes 
抄送: gluster-users 
主题: Re: [Gluster-users] Limit of Glusterfs help 
 
- "eagleeyes"  wrote:
> HI:
> Was there  a limit of servers which was used as storage in Gluster
> ?
No, there is no limit on the number of servers that can be used as storage.
Vikas
--
Engineer - http://gluster.com/
A: Because it messes up the way people read text.
Q: Why is a top-posting such a bad thing?
--
___
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users


Re: [Gluster-users] Limit of Glusterfs help

2009-06-24 Thread Vikas Gorur

- "eagleeyes"  wrote:

> HI:
> Was there  a limit of servers which was used as storage in Gluster
> ?

No, there is no limit on the number of servers that can be used as storage.

Vikas
--
Engineer - http://gluster.com/

A: Because it messes up the way people read text.
Q: Why is a top-posting such a bad thing?
--

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


[Gluster-users] Limit of Glusterfs help

2009-06-24 Thread eagleeyes
HI:
Was there  a limit of servers which was used as storage in Gluster ?


2009-06-24 



eagleeyes 



发件人: gluster-users-request 
发送时间: 2009-06-24  03:00:42 
收件人: gluster-users 
抄送: 
主题: Gluster-users Digest, Vol 14, Issue 34 
Send Gluster-users mailing list submissions to
gluster-users@gluster.org
To subscribe or unsubscribe via the World Wide Web, visit
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
or, via email, send a message with subject or body 'help' to
gluster-users-requ...@gluster.org
You can reach the person managing the list at
gluster-users-ow...@gluster.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gluster-users digest..."
Today's Topics:
   1. Re: bailout after period of inactivity (mki-gluste...@mozone.net)
   2. AFR problem (maurizio oggiano)
--
Message: 1
Date: Tue, 23 Jun 2009 05:48:11 -0700
From: mki-gluste...@mozone.net
Subject: Re: [Gluster-users] bailout after period of inactivity
To: Vikas Gorur 
Cc: gluster-users@gluster.org
Message-ID: <20090623124811.gl3...@cyclonus.mozone.net>
Content-Type: text/plain; charset=us-ascii
On Tue, Jun 23, 2009 at 07:22:31AM -0500, Vikas Gorur wrote:
> > So there is a timeout, but whatever the cause is, it's triggered by
> > long term inactivity. We never had any network problems.
> > 
> > Other machines that access the filesystem on a regular basis do not
> > show this problem. It's only the machine that get's used once in a while.
> > The problem is reproducable, not a one time event.
>  
> Thanks everyone for the reports. We will try to reproduce this and resolve
> the issue.
Perhaps adding SO_KEEPALIVE may help maintain the socket connection in the
event that there's some form of tcp session timeout happening on the
network and/or router (such as in the case of NAT)?
Just a thought.
Mohan
--
Message: 2
Date: Tue, 23 Jun 2009 16:50:10 +0200
From: maurizio oggiano 
Subject: [Gluster-users] AFR problem
To: gluster-users@gluster.org
Message-ID:

Content-Type: text/plain; charset="iso-8859-1"
I all,
I have some problem with automatic file translator ( afr). I have two server
A e B. Both servers have afr client configured.
If I stop one server, for example B, The file system managed from AFR is not
available for 30 sec in the server A.
 Below there is the gluster-client.vol of one of the server.
  volume TSU-1.localdomain-disk
  type protocol/client
  option transport-type tcp/client
  option remote-host 127.0.0.1
  option remote-subvolume disk
  end-volume
  volume TSU-2.localdomain-disk
  type protocol/client
  option transport-type tcp/client
  option remote-host 10.1.48.51
  option remote-subvolume disk
  option transport-timeout 5
  end-volume
  volume disk-afr
  type cluster/afr
  subvolumes TSU-1.localdomain-disk TSU-2.localdomain-disk
  option favorite-child TSU-1.localdomain-disk
  end-volume
  volume writeback-disk
  type performance/write-behind
  option aggregate-size 131072
  subvolumes disk-afr
  end-volume
  volume readahead-disk
  type performance/read-ahead
  option page-size 65536
  option page-count 16
  subvolumes writeback-disk
  end-volume
the server has the following configuration:
# Volume #
  volume local-disk
  type storage/posix
  option directory /glusterfs/shared
  end-volume
  volume disk
  type features/posix-locks
  subvolumes local-disk
  end-volume
# Access Control #
  volume server
  type protocol/server
  option transport-type tcp/server
  subvolumes disk
  option auth.ip.disk.allow *
  end-volume
Is there a way to avoid this behaviour?
Thanks
Maurizio
-- next part --
An HTML attachment was scrubbed...
URL: 

--
___
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
End of Gluster-users Digest, Vol 14, Issue 34
*
___
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users


Re: [Gluster-users] Dubious write performance on simple "nfs" setup

2009-06-24 Thread Vikas Gorur

- "Peter Gervai"  wrote:


> However I cannot seem to be able to raise block performance below 64k
> (especially around 4k) higher than 2-3MB/s (or 9-10MB/s without WB);
> it basically doesn't change if I try to remove other translators.
> 
> CPU and network load seems to be low on both sides.
> 
> Local fuse test gives 70+MB/s for any IO.

You can try setting the option "cache-size" for write-behind to a high
value such as 1 MB or so.
--
Engineer - http://gluster.com/

A: Because it messes up the way people read text.
Q: Why is a top-posting such a bad thing?
--

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


Re: [Gluster-users] mirroring problems with replicate Please Help!

2009-06-24 Thread Vikas Gorur

- "Phillip Walsh"  wrote:

> Hello,
> 
> I'm having problems with 2 server setup using replicate to create a 2
> system mirror for small HA setup. It seems like a locking issue or
> something. The below configuration was based on a tutorial and seemed
> solid when testing, however some file operations such as PHP BB3
> caching and SVN are causing file corruption. I am pretty new with
> glusterfs so please let me know if there is something I can change in
> my configuration to fix this. Thank you!

Can you narrow it down to a sequence of operations that causes corruption?
If not, can you describe the corruption in more detail? Anything you
can tell us about it will help.

Vikas
--
Engineer - http://gluster.com/

A: Because it messes up the way people read text.
Q: Why is a top-posting such a bad thing?
--

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