On Tue, Apr 03, 2018 at 07:57:14AM -0500, Eric Blake wrote: > On 04/02/2018 11:37 PM, Jeff Cody wrote: > > In commit 223a23c198787328ae75bc65d84edf5fde33c0b6, we implemented a > > workaround in the gluster driver to handle invalid values returned for > > SEEK_DATA or SEEK_HOLE. > > > > In some instances, these same invalid values can be seen in the posix > > file handler as well - for example, it has been reported on FUSE gluster > > mounts. > > Yuck - that should be reported to the FUSE and gluster folks, as it does > not scale to have everyone else work around their bug. But in the > meantime, working around it here is acceptable. >
Yes - there is a bug report on gluster still open for the lseek issue, I'll make sure to add on it that it affects FUSE as well, so that they are aware. -Jeff
