Re: [Gluster-users] [3.0.2] booster + unfsd failed

2010-03-03 Thread Tejas N. Bhise 
Hello Kpkim,

In our 3.0.0 release, launched December 2009, we added a native FUSE
mount/translator.  As a result, with this and later releases, we see
significant performance improvements that matches, or is better than,
that provided by booster.  The FUSE based interface also provides a
more seamless operation of the Gluster client.  

Given these factors, we now recommend using native FUSE
mount instead.   We don't actively maintain booster now and 
Booster may be deprecated in a future release.

Regards,
Tejas Bhise.


- Original Message -
From: "hgichon" 
To: gluster-users@gluster.org
Sent: Thursday, March 4, 2010 10:38:52 AM GMT +05:30 Chennai, Kolkata, Mumbai, 
New Delhi
Subject: [Gluster-users] [3.0.2] booster + unfsd failed

Hi list.

I have been testing with glusterfs-3.0.2.
glusterfs mount works well.
unfsd on glusterfs mount point works well too.

When using booster, unfsd realpath check failed.
But ls util works well.
I tried 3.0.0-git head source build but result was same.

My System is Ubuntu 9.10 and using unfsd source from official gluster
download site.
Any comment appreciated!!

- kpkim



r...@ccc1:~/gluster/unfs3-0.9.23booster0.5#
LD_PRELOAD=/usr/local/lib/glusterfs/libglusterfs-booster.so unfsd -d -e
/etc/unfs3exports
UNFS3 unfsd 0.9.23 (C) 2009, Pascal Schmidt 
realpath for /nfs/NAS failed
syntax error in '/etc/unfs3exports', exporting nothing

r...@ccc1:~/gluster/unfs3-0.9.23booster0.5# cat
/usr/local/etc/glusterfs/glusterfsd.vol
## file auto generated by /usr/local/bin/glusterfs-volgen (export.vol)
# Cmd line:
# $ /usr/local/bin/glusterfs-volgen -n NAS 192.168.1.127:/export
192.168.1.128:/export --nfs --cifs

volume posix1
  type storage/posix
  option directory /export
end-volume

volume locks1
type features/locks
subvolumes posix1
end-volume

volume brick1
type performance/io-threads
option thread-count 8
subvolumes locks1
end-volume

volume server-tcp
type protocol/server
option transport-type tcp
option auth.addr.brick1.allow *
option transport.socket.listen-port 6996
option transport.socket.nodelay on
subvolumes brick1
end-volume

r...@ccc1:~/gluster/unfs3-0.9.23booster0.5# cat
/usr/local/etc/glusterfs/glusterfs.vol
## file auto generated by /usr/local/bin/glusterfs-volgen (mount.vol)
# Cmd line:
# $ /usr/local/bin/glusterfs-volgen -n NAS 192.168.1.127:/export
192.168.1.128:/export --nfs --cifs

# TRANSPORT-TYPE tcp
volume 192.168.1.128-1
type protocol/client
option transport-type tcp
option remote-host 192.168.1.128
option transport.socket.nodelay on
option transport.remote-port 6996
option remote-subvolume brick1
end-volume

volume 192.168.1.127-1
type protocol/client
option transport-type tcp
option remote-host 192.168.1.127
option transport.socket.nodelay on
option transport.remote-port 6996
option remote-subvolume brick1
end-volume

volume distribute
type cluster/distribute
subvolumes 192.168.1.127-1 192.168.1.128-1
end-volume

volume writebehind
type performance/write-behind
option cache-size 4MB
subvolumes distribute
end-volume

volume readahead
type performance/read-ahead
option page-count 4
subvolumes writebehind
end-volume

volume iocache
type performance/io-cache
option cache-size 128MB
option cache-timeout 1
subvolumes readahead
end-volume

volume quickread
type performance/quick-read
option cache-timeout 1
option max-file-size 64kB
subvolumes iocache
end-volume

volume statprefetch
type performance/stat-prefetch
subvolumes quickread
end-volume

r...@ccc1:~/gluster/unfs3-0.9.23booster0.5# cat /etc/booster.fstab
/usr/local/etc/glusterfs/glusterfs.vol  /nfs/NAS/ glusterfs
logfile=/var/log/glusterfs/NAS-nfs.log,loglevel=DEBUG,attr_timeout=0

r...@ccc1:~/gluster/unfs3-0.9.23booster0.5# cat /etc/unfs3exports
/nfs/NAS0.0.0.0/0(rw,no_root_squash)


-- booster log

[2010-03-04 13:48:16] N [client-protocol.c:6246:client_setvolume_cbk]
192.168.1.127-1: Connected to 192.168.1.127:6996, attached to remote
volume 'brick1'.
[2010-03-04 13:48:16] N [client-protocol.c:6246:client_setvolume_cbk]
192.168.1.127-1: Connected to 192.168.1.127:6996, attached to remote
volume 'brick1'.
[2010-03-04 13:48:16] N [client-protocol.c:6246:client_setvolume_cbk]
192.168.1.128-1: Connected to 192.168.1.128:6996, attached to remote
volume 'brick1'.
[2010-03-04 13:48:16] N [client-protocol.c:6246:client_setvolume_cbk]
192.168.1.128-1: Connected to 192.168.1.128:6996, attached to remote
volume 'brick1'.
[2010-03-04 13:48:16] D [dht-diskusage.c:71:dht_du_info_cbk] distribute:
on subvolume '192.168.1.127-1': avail_percent is: 96.00 and avail_space
is: 66246918144
[2010-03-04 13:48:16] D [dht-diskusage.c:71:dht_du_info_cbk] distribute:
on subvolume '192.168.1.128-1': avail_percent is: 97.00 and avail_space
is: 67548491776
[2010-03-04 13:48:16] D [dht-disk

[Gluster-users] [3.0.2] booster + unfsd failed

2010-03-03 Thread hgichon 
Hi list.

I have been testing with glusterfs-3.0.2.
glusterfs mount works well.
unfsd on glusterfs mount point works well too.

When using booster, unfsd realpath check failed.
But ls util works well.
I tried 3.0.0-git head source build but result was same.

My System is Ubuntu 9.10 and using unfsd source from official gluster
download site.
Any comment appreciated!!

- kpkim



r...@ccc1:~/gluster/unfs3-0.9.23booster0.5#
LD_PRELOAD=/usr/local/lib/glusterfs/libglusterfs-booster.so unfsd -d -e
/etc/unfs3exports
UNFS3 unfsd 0.9.23 (C) 2009, Pascal Schmidt 
realpath for /nfs/NAS failed
syntax error in '/etc/unfs3exports', exporting nothing

r...@ccc1:~/gluster/unfs3-0.9.23booster0.5# cat
/usr/local/etc/glusterfs/glusterfsd.vol
## file auto generated by /usr/local/bin/glusterfs-volgen (export.vol)
# Cmd line:
# $ /usr/local/bin/glusterfs-volgen -n NAS 192.168.1.127:/export
192.168.1.128:/export --nfs --cifs

volume posix1
  type storage/posix
  option directory /export
end-volume

volume locks1
type features/locks
subvolumes posix1
end-volume

volume brick1
type performance/io-threads
option thread-count 8
subvolumes locks1
end-volume

volume server-tcp
type protocol/server
option transport-type tcp
option auth.addr.brick1.allow *
option transport.socket.listen-port 6996
option transport.socket.nodelay on
subvolumes brick1
end-volume

r...@ccc1:~/gluster/unfs3-0.9.23booster0.5# cat
/usr/local/etc/glusterfs/glusterfs.vol
## file auto generated by /usr/local/bin/glusterfs-volgen (mount.vol)
# Cmd line:
# $ /usr/local/bin/glusterfs-volgen -n NAS 192.168.1.127:/export
192.168.1.128:/export --nfs --cifs

# TRANSPORT-TYPE tcp
volume 192.168.1.128-1
type protocol/client
option transport-type tcp
option remote-host 192.168.1.128
option transport.socket.nodelay on
option transport.remote-port 6996
option remote-subvolume brick1
end-volume

volume 192.168.1.127-1
type protocol/client
option transport-type tcp
option remote-host 192.168.1.127
option transport.socket.nodelay on
option transport.remote-port 6996
option remote-subvolume brick1
end-volume

volume distribute
type cluster/distribute
subvolumes 192.168.1.127-1 192.168.1.128-1
end-volume

volume writebehind
type performance/write-behind
option cache-size 4MB
subvolumes distribute
end-volume

volume readahead
type performance/read-ahead
option page-count 4
subvolumes writebehind
end-volume

volume iocache
type performance/io-cache
option cache-size 128MB
option cache-timeout 1
subvolumes readahead
end-volume

volume quickread
type performance/quick-read
option cache-timeout 1
option max-file-size 64kB
subvolumes iocache
end-volume

volume statprefetch
type performance/stat-prefetch
subvolumes quickread
end-volume

r...@ccc1:~/gluster/unfs3-0.9.23booster0.5# cat /etc/booster.fstab
/usr/local/etc/glusterfs/glusterfs.vol  /nfs/NAS/ glusterfs
logfile=/var/log/glusterfs/NAS-nfs.log,loglevel=DEBUG,attr_timeout=0

r...@ccc1:~/gluster/unfs3-0.9.23booster0.5# cat /etc/unfs3exports
/nfs/NAS0.0.0.0/0(rw,no_root_squash)


-- booster log

[2010-03-04 13:48:16] N [client-protocol.c:6246:client_setvolume_cbk]
192.168.1.127-1: Connected to 192.168.1.127:6996, attached to remote
volume 'brick1'.
[2010-03-04 13:48:16] N [client-protocol.c:6246:client_setvolume_cbk]
192.168.1.127-1: Connected to 192.168.1.127:6996, attached to remote
volume 'brick1'.
[2010-03-04 13:48:16] N [client-protocol.c:6246:client_setvolume_cbk]
192.168.1.128-1: Connected to 192.168.1.128:6996, attached to remote
volume 'brick1'.
[2010-03-04 13:48:16] N [client-protocol.c:6246:client_setvolume_cbk]
192.168.1.128-1: Connected to 192.168.1.128:6996, attached to remote
volume 'brick1'.
[2010-03-04 13:48:16] D [dht-diskusage.c:71:dht_du_info_cbk] distribute:
on subvolume '192.168.1.127-1': avail_percent is: 96.00 and avail_space
is: 66246918144
[2010-03-04 13:48:16] D [dht-diskusage.c:71:dht_du_info_cbk] distribute:
on subvolume '192.168.1.128-1': avail_percent is: 97.00 and avail_space
is: 67548491776
[2010-03-04 13:48:16] D [dht-diskusage.c:71:dht_du_info_cbk] distribute:
on subvolume '192.168.1.127-1': avail_percent is: 96.00 and avail_space
is: 66246918144
[2010-03-04 13:48:16] D [dht-diskusage.c:71:dht_du_info_cbk] distribute:
on subvolume '192.168.1.128-1': avail_percent is: 97.00 and avail_space
is: 67548491776
[2010-03-04 13:48:16] D
[libglusterfsclient.c:1744:libgf_vmp_map_ghandle] libglusterfsclient:
New Entry: /nfs/NAS
[2010-03-04 13:48:16] D [libglusterfsclient.c:1487:libgf_init_vmpentry]
libglusterfsclient: New VMP entry: /nfs/NAS
[2010-03-04 13:48:16] D
[libglusterfsclient.c:1755:libgf_vmp_map_ghandle] libglusterfsclient:
Empty list
[2010-03-04 13:48:16] D [booster.c:1252:booster_init] booster: booster
is inited
[2010-03-04 13:48:16] D
[libglusterfsclient.c:1

Re: [Gluster-users] Can gluster export be nfs exported too?

2010-03-03 Thread Tejas N. Bhise 
Jeremy,

Exporting of same (local or locally mounted ) volume/filesystem using two 
different protocols is possible in theory but very difficult to implement. Each 
exporter usually has some housekeeping information on the data it exports and 
in most implementations two exporter do not share this information. This is 
what makes it difficult, though not impossible. Look up ctdb and SAMBA and you 
will understand what I am trying to say.

Regards,
Tejas.

- Original Message -
From: "Jeremy Enos" 
To: "Raghavendra G" 
Cc: gluster-users@gluster.org
Sent: Wednesday, March 3, 2010 1:16:18 PM GMT +05:30 Chennai, Kolkata, Mumbai, 
New Delhi
Subject: Re: [Gluster-users] Can gluster export be nfs exported too?

Second question:
Even if it's not supported, is it theoretically feasible?

 Jeremy

On 3/2/2010 10:16 PM, Raghavendra G wrote:
> No, its not supported to export glusterfs backend directories using NFS.
>
> On Tue, Mar 2, 2010 at 8:43 AM, Jeremy Enos  > wrote:
>
> If I have a single system exporting gluster, can I also export
> that same directory via NFS w/o Gluster in the loop, or is it
> different somehow?  I assume I definitely can't do that on any
> striped setup for obvious reasons.  (I realize I could NFS export
> the gluster mounted volume, but I'm talking about the gluster
> export volume here)
> thx-
>
>Jeremy
>
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org 
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>
>
>
>
> -- 
> Raghavendra G
>

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