Looks like some OS issue. To be on the safe side I recommend opening a bug. On Thu, Mar 10, 2011 at 3:17 AM, Daniel M?ller <mueller at tropenklinik.de> wrote: > This is the error in ?mnt-glusterfs.log > W [fuse-bridge.c:405:fuse_attr_cbk] glusterfs-fuse: 20480: FSTAT() > /windows/test/start.xlsx => -1 (File descriptor in bad state) > > ----------------------------------------------- > EDV Daniel M?ller > > Leitung EDV > Tropenklinik Paul-Lechler-Krankenhaus > Paul-Lechler-Str. 24 > 72076 T?bingen > > Tel.: 07071/206-463, Fax: 07071/206-499 > eMail: mueller at tropenklinik.de > Internet: www.tropenklinik.de > ----------------------------------------------- > > -----Urspr?ngliche Nachricht----- > Von: Mohit Anchlia [mailto:mohitanchlia at gmail.com] > Gesendet: Mittwoch, 9. M?rz 2011 20:10 > An: mueller at tropenklinik.de; gluster-users at gluster.org > Betreff: Re: Strange behaviour glusterd 3.1 > > If it's a problem can you please enable the debug on that volume and > then see what gets logged in the logs. > > I suggest creating a bug since it sounds critical. What if it was production > :) > > On Wed, Mar 9, 2011 at 10:42 AM, Daniel M?ller <mueller at tropenklinik.de> > wrote: >> >> >> did set gluster volume set samba-vol performance.quick-read off . >> >> vim >> a new file on node1. ssh node2 . ls new file -----> read error, file not >> found. >> >> did set gluster volume set samba-vol performance.quick-read on. >> >> >> I can ls, change content one time. Then the same again. No >> solution!!!!!!!!!!! >> >> Should I delete the VOl? and build a new one? >> >> I am >> glad that it is no production environment. It would be a mess. >> >> On Wed, 09 >> Mar 2011 23:10:21 +0530, Vijay Bellur ?wrote: On Wednesday 09 March 2011 >> 04:00 PM, Daniel M?ller wrote: >> /mnt/glusterfs ist he mount point of the >> client where the samba-vol (backend:/glusterfs/export) is mounted on. >> So it >> should work. And it did work until last week. >> >> ?Can you please check by >> disabling quick-read translator in your setup via the following >> command: >> >> #gluster volume set performance.quick-read off >> >> You may be >> hitting bug 2027 with 3.1.0 >> >> Thanks, >> Vijay >> >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >> >> > >
