Shyam, Thank you for pointing this out. I've updated the logs for bug-990028.t test. On Wed, Jul 18, 2018 at 8:40 PM Shyam Ranganathan <srangana@xxxxxxxxxx> wrote: > > On 07/18/2018 10:51 AM, Shyam Ranganathan wrote: > > On 07/18/2018 05:42 AM, Deepshikha Khandelwal wrote: > >> Hi all, > >> > >> There are tests which have been constantly failing for distributed > >> regression framework[1]. I would like to draw the maintainer's > >> attention to look at these two bugs[2]&[3] and help us to attain the > >> RCA for such failures. > >> > >> Until then, we're disabling these two blocking tests. > >> > >> [1] https://build.gluster.org/job/distributed-regression/ > >> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1602282 > >> [3] https://bugzilla.redhat.com/show_bug.cgi?id=1602262 > > > > Bug updated with current progress: > > https://bugzilla.redhat.com/show_bug.cgi?id=1602262#c1 > > > > Pasting it here for others to chime in based on past experience if any. > > > > <snip> > > This fails as follows, > > ========================= > > TEST 52 (line 37): ln /mnt/glusterfs/0/file1 /mnt/glusterfs/0/file44 > > ln: failed to create hard link ‘/mnt/glusterfs/0/file44’: No space left > > on device > > RESULT 52: 1 > > ========================= > > (continues till the last file) IOW, file44-file50 fail creation > > ========================= > > TEST 58 (line 37): ln /mnt/glusterfs/0/file1 /mnt/glusterfs/0/file50 > > ln: failed to create hard link ‘/mnt/glusterfs/0/file50’: No space left > > on device > > RESULT 58: 1 > > ========================= > > > > Post this the failures are due to attempts to inspect these files for > > metadata and attrs and such, so the failures are due to the above. > > > > At first I suspected max-hardlink setting, but this is at a default of > > 100, and we do not use any specific site.h or tuning when running in the > > distributed environment (as far as I can tell). > > > > Also, the test, when it fails, has only created 1 empty file and 42 > > links to the same, this should not cause the bricks to run out of space. > > > > The Gluster logs till now did not throw up any surprises, or causes. > > Just realized that logs attached to the bug are not from this test > failure, requesting the right logs, so that we can possibly find the > root cause. > > > </snip> > > > >> > >> Thanks, > >> Deepshikha Khandelwal > >> _______________________________________________ > >> Gluster-devel mailing list > >> Gluster-devel@xxxxxxxxxxx > >> https://lists.gluster.org/mailman/listinfo/gluster-devel > >> > > _______________________________________________ > > Gluster-devel mailing list > > Gluster-devel@xxxxxxxxxxx > > https://lists.gluster.org/mailman/listinfo/gluster-devel > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > https://lists.gluster.org/mailman/listinfo/gluster-devel _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
