On Wed, Jul 24, 2019 at 11:46 AM Kirill Smelkov wrote:
>
> Miklos,
>
> I was sending this patch for ~1.5 month without any feedback from you[1,2,3].
> The patch was tested by Sander Eikelenboom (original GlusterFS problem
> reporter)[4], and you said that it will be ok to retry for next
>
On Tue, Jun 11, 2019 at 10:28 PM Kirill Smelkov wrote:
> Miklos, would 4K -> `sizeof(fuse_in_header) + sizeof(fuse_write_in)` for
> header room change be accepted?
Yes, next cycle. For 4.2 I'll just push the revert.
Thanks,
Miklos
On Tue, Jun 11, 2019 at 1:03 PM Sander Eikelenboom wrote:
>
> L.S.,
>
> While testing a linux 5.2 kernel I noticed it fails to mount my glusterfs
> volumes.
>
> It repeatedly fails with:
>[2019-06-11 09:15:27.106946] W [fuse-bridge.c:4993:fuse_thread_proc]
> 0-glusterfs-fuse: read from
On Wed, Sep 10, 2014 at 6:14 PM, Anand Avati av...@gluster.org wrote:
This is something beyond the libfuse API. Unless the kernel/user ABI is
modified to present the entire 128bits with each call (i.e, both nodeID +
generation instead of just nodeID) we are still bound to provide unique
On Thu, Sep 4, 2014 at 5:42 PM, Goswin von Brederlow goswin-...@web.de wrote:
On Tue, Sep 02, 2014 at 08:20:35AM -0700, Anand Avati wrote:
On Mon, Sep 1, 2014 at 6:07 AM, Vimal A R arvi...@yahoo.in wrote:
Hello fuse-devel / fs-cache / gluster-devel lists,
I would like to propose the idea
On Fri, Jun 27, 2014 at 9:59 AM, Niels de Vos nde...@redhat.com wrote:
On Thu, Jun 26, 2014 at 08:21:57PM -0400, Anand Avati wrote:
The following test case demonstrates the bug:
sh# mount -t glusterfs localhost:meta-test /mnt/one
sh# mount -t glusterfs localhost:meta-test /mnt/two
