Hi List,
Sorry for the crude english !
we have an 3 Nodes gluster Installation.
Since start of this gluster we have problems like this:
[2010-12-10 07:14:57.210627] E [posix.c:437:posix_lookup] posix: lstat
on /backup/mail8-node2/yesteryesterday_root.tgz failed: No data available
[2010-12-10 08:14:57.778585] E [posix.c:1084:posix_mknod] posix: mknod
on /backup/mysql2/yesterday_root.tgz failed: File exists
[2010-12-10 08:14:57.813334] E [posix.c:437:posix_lookup] posix: lstat
on /backup/mysql2/yesterday_root.tgz failed: No data available
I read tons of old maillinglist entry's and some suggest to get the
latest version of glusterfs.
Since 18.11.2010 we have 3.1.0 in use and the errors continues.
Sometimes the problem can be solved for an longer time if unexport and
restart all gluster processes.
I just have no (more) idea were to search for an solution. But I guess
that this should be an trivial Problems since others have obviously
running gluster in production.
The Hardware was selected to be reliable ( Areca Raid6 Drives, Dual Xeon
CPU, Server Mainboards, Server NIC`s) and has continuous data rates if
tested with bonnie.
The Config:
----
volume posix
type storage/posix
option directory /raid/cluster
end-volume
volume locks
type features/locks
subvolumes posix
end-volume
volume brick
type performance/io-threads
option thread-count 8
subvolumes locks
end-volume
volume server
type protocol/server
option transport-type tcp
option auth.addr.brick.allow IPRANGE.*
subvolumes brick
end-volume
---
volume remote1
type protocol/client
option transport-type tcp
option remote-host IP1
option remote-subvolume brick
end-volume
volume remote2
type protocol/client
option transport-type tcp
option remote-host IP2
option remote-subvolume brick
end-volume
volume remote3
type protocol/client
option transport-type tcp
option remote-host IP3
option remote-subvolume brick
end-volume
volume distribute
type cluster/distribute
option lookup-unhashed yes
subvolumes remote1 remote2 remote3
end-volume
volume writebehind
type performance/write-behind
option window-size 1MB
subvolumes distribute
end-volume
volume cache
type performance/io-cache
option cache-size 512MB
subvolumes writebehind
end-volume
