2015-10-16 17:49 GMT+02:00 Rainer Gerhards <[email protected]>: > 2015-10-16 17:44 GMT+02:00 Kendall Green <[email protected]>: >> The bug doesn't seem to be the file system driver, because the fuse-dfs >> mount reports the error as random write operation. The error message is >> from the driver library which validates sequential writes are used, but is >> caused from rsyslog changing from sequential to random write operations. >> >> When rsyslog first writes file output is sequential, then at the point when >> some other process writes to a different file, or simply ls the directory >> rsyslog is writing to, then rsyslog starts attempting unsupported write >> operations > > No - as I already said, we do purely sequential writes.
too fast... you might want to do an strace to convince me that rsyslog does anything other than that... That could also possibly bring some insight into which calls actually fail. > > Rainer >> and process batch deletion as if write error retry was >> successful when it is not. >> _______________________________________________ >> rsyslog mailing list >> http://lists.adiscon.net/mailman/listinfo/rsyslog >> http://www.rsyslog.com/professional-services/ >> What's up with rsyslog? Follow https://twitter.com/rgerhards >> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of >> sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T >> LIKE THAT. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
