[Gluster-users] Gluster-users Digest, Vol 20, Issue 3
Todd Daugherty
todd at veryheavy.se
Mon Dec 7 16:41:54 UTC 2009
There. Hope this helps.
Todd
volume remote01
type protocol/client
option transport-type tcp
option remote-host flock01
option remote-subvolume brick03
end-volume
volume remote02
type protocol/client
option transport-type tcp
option remote-host flock01
option remote-subvolume brick04
end-volume
volume remote03
type protocol/client
option transport-type tcp
option remote-host flock03
option remote-subvolume brick03
end-volume
volume remote04
type protocol/client
option transport-type tcp
option remote-host flock03
option remote-subvolume brick04
end-volume
volume remote05
type protocol/client
option transport-type tcp
option remote-host flock04
option remote-subvolume brick03
end-volume
volume remote06
type protocol/client
option transport-type tcp
option remote-host flock04
option remote-subvolume brick04
end-volume
volume remote07
type protocol/client
option transport-type tcp
option remote-host flock08
option remote-subvolume brick03
end-volume
volume remote08
type protocol/client
option transport-type tcp
option remote-host flock08
option remote-subvolume brick04
end-volume
volume distribute
type cluster/distribute
subvolumes remote01 remote02 remote03 remote04 remote05 remote06
remote07 remote08
end-volume
volume writebehind
type performance/write-behind
option cache-size 16MB
option flush-behind on
subvolumes distribute
end-volume
volume cache01
type performance/io-cache
option cache-size 512MB
option cache-timeout 30
subvolumes writebehind
end-volume
volume readahead
type performance/read-ahead
option page-count 16 # 2 is default option
option force-atime-update off # default is off
subvolumes cache01
end-volume
volume posix01
type storage/posix
option directory /node01/storage
end-volume
volume locks01
type features/locks
subvolumes posix01
end-volume
volume brick01
type performance/io-threads
option thread-count 2
subvolumes locks01
end-volume
volume posix02
type storage/posix
option directory /node02/storage
end-volume
volume locks02
type features/locks
subvolumes posix02
end-volume
volume brick02
type performance/io-threads
option thread-count 2
subvolumes locks02
end-volume
volume posix03
type storage/posix
option directory /node03/storage
end-volume
volume locks03
type features/locks
subvolumes posix03
end-volume
volume brick03
type performance/io-threads
option thread-count 32
subvolumes locks03
end-volume
volume posix04
type storage/posix
option directory /node04/storage
end-volume
volume locks04
type features/locks
subvolumes posix04
end-volume
volume brick04
type performance/io-threads
option thread-count 32
subvolumes locks04
end-volume
volume server
type protocol/server
option transport-type ib-verbs/server
option auth.addr.brick01.allow *
option auth.addr.brick02.allow *
option auth.addr.brick03.allow *
option auth.addr.brick04.allow *
subvolumes brick01 brick02 brick03 brick04
end-volume
volume tcp_server
type protocol/server
option transport-type tcp/server
option transport.socket.nodelay on
option auth.addr.brick01.allow *
option auth.addr.brick02.allow *
option auth.addr.brick03.allow *
option auth.addr.brick04.allow *
subvolumes brick01 brick02 brick03 brick04
end-volume
On Fri, Dec 4, 2009 at 12:40 PM, lakshmi pathi <lakshmipathi.g at gmail.com> wrote:
> Todd,
>
> Could you please provide the glusterfs client and server volume files
> ? That will help us to look into the cpio issue.
>
> --
> Cheers,
> Lakshmipathi.G
> ------------------------------
>
>> Date: Thu, 3 Dec 2009 11:34:00 +0100
>> From: Todd Daugherty <todd at veryheavy.se>
>> Subject: [Gluster-users] GlusterFS and Visual Effects
>> To: gluster-users at gluster.org
>> Message-ID:
>> <6a44b16d0912030234p6e126626qcfd42f1ab414e758 at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> I have created a file via Houdini (http://www.sidefx.com/). To a
>> glusterfs cluster. (2.0.8) I created the same file to the local hard
>> drive. The file created to the local hard drive works. The file
>> created to the glusterfs cluster does not.
>>
>> The md5sum binary checksums of the files are different. The md5sum
>> ascii checksums are the the same.
>>
>> I have straces of both processes and I am interested in any feedback
>> that is possible on this topic. I have posted here before about other
>> Visual Effects tools having similar problems. (Rendermans PTFilter,
>> 3Dlights tdlmake) So there is something that this software is doing
>> that goes not work with glusterfs.
>>
>> When the Glusterfs volume is exported via NFS or CIFS this problem is
>> not present. It is only when using the GlusterFS native client.
>>
>> Todd
>>
>
More information about the Gluster-users
mailing list