Are we sure it wasn't a problem with the file system that simply reformatting fixed? Maybe reformatting with ext4 again would have fixed it too. -- Benjamin Long On Thursday 18 March 2010 02:16:46 pm phil cryer wrote: > > The solution was quite simple. It turned out that it was because the > > server's data drive was formatted in ext4. Switched it to ext3 and the > > problems went away! > > Is this a known issue with Gluster 3.0.3? I've setup our cluster with > ext4 on Debian, but have not had any issues like this yet (but we're > not running live yet). Is this something to be concerned about? > Should we change everything back to ext3? > > P > > On Thu, Mar 18, 2010 at 8:48 AM, Lee Simpson <lee at leenix.co.uk> wrote: > > Hello, > > > > Just thought id share the experience i had with a gluster client error > > and the solution i found after much searching and chatting with some IRC > > guys. > > > > Im running a simple 2 server with multiple clients using > > cluster/replicate. Randomly newly created files produced the following > > error in the gluster client logs when accessed; > > > > "W [fuse-bridge.c:858:fuse_fd_cbk] glusterfs-fuse: 59480: OPEN() > > /data/randomfile-here => -1 (No such file or directory)" > > > > These files are created by apache or other scripts (such as awstats on a > > cron). Apache is then unable to read the file, and the above message > > appears in the gluster logs everytime you try. If i SSH into the apache > > server and cat the file it displays fine and then apache starts reading > > it fine. > > > > I upgraded the client and server to 3.03 and tried reducing my configs to > > the bare min without any performance volumes.. But the problem > > persisted... > > > > > > SOLUTION > > > > The solution was quite simple. It turned out that it was because the > > server's data drive was formatted in ext4. Switched it to ext3 and the > > problems went away! > > > > > > Hope that helps someone else who finds this. > > > > > > - Lee
