When quota xlator is enabled, bricks get this:
[2014-10-12 07:56:03.090516] E [posix.c:4874:posix_fill_readdir]
0-patchy-posix: seekdir(-1154801456) failed on dir=0xb99cb250: Invalid
argument (offset reused from another DIR * structure?)
This means something either seekdir on a DIR * that was
Emmanuel Dreyfus m...@netbsd.org wrote:
This means something either seekdir on a DIR * that was not obtained by
opendir(), or that was closedir() and then opendir() again. Can someone
explain me what directory walks are introduced by quota, and where
opendir/readdir/closedir happen for that?
Emmanuel Dreyfus m...@netbsd.org wrote:
Erratum: it happens because it attempts to seekdir to the offset
obtained for last record. But I still have to find what code is sending
the request.
Here is the king of debug trace I have:
[quota.c:3959:quota_readdirp] 0-XXXmanu: fd = 0xbb242818,
Sorry, I'm a bit late on this. I quite like when you do a blog post
for the new releases, where you have a list of bugs squashed /
features added. You could do a blog post every week or two with a
summary of new / updated bugs, then post a link to the mailing list,
twitter, etc.
Regards,
Alan
Jeff Darcy jda...@redhat.com wrote:
More recently, a *completely separate* approach to
multi-threading - multi-threaded epoll - has been getting some
attention. Here's what I see as the pros and cons of this new approach.
You forgot:
CON: epoll is Linux specific and code using it is not
Emmanuel Dreyfus m...@netbsd.org wrote:
Erratum: it happens because it attempts to seekdir to the offset
obtained for last record. But I still have to find what code is sending
the request.
This is a find(1) probably forked by quota-crawld glusterd. In fact
running a find . in the fs is
On 10/13/2014 09:45 AM, Emmanuel Dreyfus wrote:
Emmanuel Dreyfus m...@netbsd.org wrote:
Erratum: it happens because it attempts to seekdir to the offset
obtained for last record. But I still have to find what code is sending
the request.
This is a find(1) probably forked by quota-crawld
