Hi,
I forgot to say: A
# umount -f /scratch; umount /scratch; mount /scratch
resolves the problems. No need to reload fuse.
Fred
On 25.11.2008, at 13:42, Joe Landman wrote:
Fred Hucht wrote:
Hi!
The glusterfsd.log on all nodes are virtually empty, the only entry
on 2008-11-25 reads
2008-11-25 03:13:48 E [io-threads.c:273:iot_flush] sc1-ioth: fd
context is NULL, returning EBADFD
on all nodes. I don't think that this is related to our problems.
Regards,
Fred
Hi Fred
Could you post complete /var/log/messages file on pastebin? I have
seen something like this before when fuse crashes. Fuse crashing
could be due to a bug in fuse, the kernel, etc. Also could be
hardware that is failing.
Does an unmount/remount fix the problem?
Joe
--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics LLC,
email: landman@xxxxxxxxxxxxxxxxxxxxxxx
web : http://www.scalableinformatics.com
http://jackrabbit.scalableinformatics.com
phone: +1 734 786 8423 x121
fax : +1 866 888 3112
cell : +1 734 612 4615
Dr. Fred Hucht <fred@xxxxxxxxxxxxxx>
Institute for Theoretical Physics
University of Duisburg-Essen, 47048 Duisburg, Germany
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
