[Gluster-users] File uploaded to webDAV server on GlusterFS AFR - ends up without xattr!

[Krishna Srinivas]

Can you put "option debug on" in AFR vol definition and paste me the
log when you copy through webdav?
Start glusterfs with -L DEBUG

Thanks
Krishna

On Tue, Dec 9, 2008 at 5:56 PM, Lior Goikhburg <glior at hh.ru> wrote:
> Hello list.
>
> I'm testing GlusterFS AFR mode as a solution for implementing a highly
> available webDAV file storage for our production environment.
> Whlie doing performance tests I've notticed a strange behavior: the
> files which are uploaded via a webDAV server, end up without extended
> attributes, which removes the ability to self-heal.
> The set up is a simple testing environment with 2 servers and one AFR
> client which runs Nginx web server which accepts HTTP PUT requests from
> clients.
>
> I'm uploading with the following command:
> curl -0 -s -T /data/100399.crp http://localhost:8024/file/
>
>
> The AFR volume is mounted in /var/www/storage (is available to Nginx web
> server):
> glusterfs -f /etc/glusterfs/glusterfs-client.vol -n afr1 /var/www/storage/
>
> Nginx receives the file into a temp directory "client_body_temp_path"
> /var/www/storage/tmp2 (untill it receives the entire file) and then
> renames the file (with rename () function) to the destination dir:
> /var/www/storage/data
>
> The files that are being created/copied/moved/modified/etc manualy (via
> shell), has their xattrs set up fine:
> search101:/srv/export/files/data/file# getfattr  -d -m ".*" test
> # file: test
> trusted.glusterfs.createtime="1228825236"
> trusted.glusterfs.version="2"
>
> But not the ones uploaded via Nginx:
> search101:/srv/export/files/data/file# getfattr  -d -m ".*"
> 99/30/0/100399.crp