[Gluster-users] "UNLINK [...] returned NULL inode" message in client log
Daniel Maher
dma+gluster at witbe.net
Fri Dec 5 09:53:40 UTC 2008
Daniel Maher wrote:
> Hello all,
>
> Lately i've been seeing the following messages over and over again in my
> client logs :
>
> 2008-11-17 01:52:51 E [fuse-bridge.c:1163:fuse_unlink] glusterfs-fuse:
> 143141519: UNLINK /directory/sub-directory/file.ext (fuse_loc_fill()
> returned NULL inode)
Hello once again :)
I posted this in November, but did not receive any responses at the
time. With all the talk of mixing 32 and 64-bit systems, it occurred to
me that perhaps there's a link between word size (and the exceeding
thereof), and this error.
Is it possible that my 64-bit clients are trying to assign file
attributes which are too large for my 32-bit servers to deal with, and
if so, could that result in the error noted above ?
--
Daniel Maher <dma+gluster AT witbe DOT net>
More information about the Gluster-users
mailing list