<div dir="ltr">I checked the machine.<div><br></div><div>Here is the df -hT output</div><div><div>[jenkins@slave29 ~]$ cat /etc/fstab </div><div># Accessible filesystems, by reference, are maintained under '/dev/disk'</div><div># See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info</div><div>#</div><div>/dev/xvda1 / ext3 defaults,noatime,barrier=0 1 1</div><div>tmpfs /dev/shm tmpfs defaults 0 0</div><div>devpts /dev/pts devpts gid=5,mode=620 0 0</div><div>sysfs /sys sysfs defaults 0 0</div><div>proc /proc proc defaults 0 0</div><div>#/dev/xvdc1 none swap sw 0 0</div><div><br></div><div><br></div><div>We don't see a xfs device mounted at /d and / is of type ext3 which does not support fallocate. The uptime of the machine is 73 days though. I don't know how the /d xfs partition vanished.</div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 12, 2016 at 4:54 PM, Atin Mukherjee <span dir="ltr"><<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><a href="https://build.gluster.org/job/rackspace-regression-2GB-triggered/22156/consoleFull" target="_blank">https://build.gluster.org/job/rackspace-regression-2GB-triggered/22156/consoleFull</a> - another failure<br></div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Tue, Jul 12, 2016 at 4:42 PM, Atin Mukherjee <span dir="ltr"><<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Tue, Jul 12, 2016 at 4:36 PM, Avra Sengupta <span dir="ltr"><<a href="mailto:asengupt@redhat.com" target="_blank">asengupt@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Hi Atin,<br>
<br>
Please check the testcase result in the console. It clearly states
the reason of the failure. A quick search of 30815, as shown in
the testcase shows that the error that is generated is a thinp
issue, and we can see fallocate failing and lvm not properly being
setup in the environment.<br></div></div></blockquote><div><br></div></span><div>While this is valid for my docker containers, I am just wondering why did this happen in jenkins slave?<br><br></div><div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><div>
<br>
Regards,<br>
Avra<br>
<br>
P.S Here are the logs from the console stating so.<br>
<br>
<pre><span><b>02:50:34</b> </span>[09:50:34] Running tests in file ./tests/basic/op_errnos.t
<span><b>02:50:41</b> </span>fallocate: /d/backends/patchy_snap_vhd: fallocate failed: Operation not supported
<span><b>02:50:41</b> </span>losetup: /d/backends/patchy_snap_vhd: warning: file smaller than 512 bytes, the loop device maybe be useless or invisible for system tools.
<span><b>02:50:41</b> </span> Device /d/backends/patchy_snap_loop not found (or ignored by filtering).
<span><b>02:50:41</b> </span> Device /d/backends/patchy_snap_loop not found (or ignored by filtering).
<span><b>02:50:41</b> </span> Unable to add physical volume '/d/backends/patchy_snap_loop' to volume group 'patchy_snap_vg_1'.
<span><b>02:50:41</b> </span> Volume group "patchy_snap_vg_1" not found
<span><b>02:50:41</b> </span> Cannot process volume group patchy_snap_vg_1
<span><b>02:50:42</b> </span> Volume group "patchy_snap_vg_1" not found
<span><b>02:50:42</b> </span> Cannot process volume group patchy_snap_vg_1
<span><b>02:50:42</b> </span>/dev/patchy_snap_vg_1/brick_lvm: No such file or directory
<span><b>02:50:42</b> </span>Usage: mkfs.xfs
<span><b>02:50:42</b> </span>/* blocksize */                [-b log=n|size=num]
<span><b>02:50:42</b> </span>/* data subvol */        [-d agcount=n,agsize=n,file,name=xxx,size=num,
<span><b>02:50:42</b> </span>                         (sunit=value,swidth=value|su=num,sw=num),
<span><b>02:50:42</b> </span>                         sectlog=n|sectsize=num
<span><b>02:50:42</b> </span>/* inode size */        [-i log=n|perblock=n|size=num,maxpct=n,attr=0|1|2,
<span><b>02:50:42</b> </span>                         projid32bit=0|1]
<span><b>02:50:42</b> </span>/* log subvol */        [-l agnum=n,internal,size=num,logdev=xxx,version=n
<span><b>02:50:42</b> </span>                         sunit=value|su=num,sectlog=n|sectsize=num,
<span><b>02:50:42</b> </span>                         lazy-count=0|1]
<span><b>02:50:42</b> </span>/* label */                [-L label (maximum 12 characters)]
<span><b>02:50:42</b> </span>/* naming */                [-n log=n|size=num,version=2|ci]
<span><b>02:50:42</b> </span>/* prototype file */        [-p fname]
<span><b>02:50:42</b> </span>/* quiet */                [-q]
<span><b>02:50:42</b> </span>/* realtime subvol */        [-r extsize=num,size=num,rtdev=xxx]
<span><b>02:50:42</b> </span>/* sectorsize */        [-s log=n|size=num]
<span><b>02:50:42</b> </span>/* version */                [-V]
<span><b>02:50:42</b> </span>                        devicename
<span><b>02:50:42</b> </span><devicename> is required unless -d name=xxx is given.
<span><b>02:50:42</b> </span><num> is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB),
<span><b>02:50:42</b> </span> xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB).
<span><b>02:50:42</b> </span><value> is xxx (512 byte blocks).
<span><b>02:50:42</b> </span>mount: special device /dev/patchy_snap_vg_1/brick_lvm does not exist
<span><b>02:50:53</b> </span>./tests/basic/op_errnos.t ..
<span><b>02:50:53</b> </span>1..21
<span><b>02:50:53</b> </span>ok 1, LINENUM:12
<span><b>02:50:53</b> </span>ok 2, LINENUM:13
<span><b>02:50:53</b> </span>ok 3, LINENUM:14
<span><b>02:50:53</b> </span>ok 4, LINENUM:16
<span><b>02:50:53</b> </span>ok 5, LINENUM:18
<span><b>02:50:53</b> </span>ok 6, LINENUM:19
<span><b>02:50:53</b> </span>ok 7, LINENUM:20
</pre><div><div>
On 07/12/2016 03:47 PM, Atin Mukherjee wrote:<br>
</div></div></div><div><div>
<blockquote type="cite">
<div dir="ltr">Hi Avra,<br>
<br>
The above fails locally as well along with few regression
failures I observed and one of them are at [1]<br>
<br>
not ok 12 Got " 30807" instead of "30809", LINENUM:26<br>
FAILED COMMAND: 30809 get-op_errno-xml snapshot restore snap1<br>
<br>
not ok 17 Got " 30815" instead of "30812", LINENUM:31<br>
FAILED COMMAND: 30812 get-op_errno-xml snapshot create snap1
patchy no-timestamp<br>
<br>
[1] <a href="https://build.gluster.org/job/rackspace-regression-2GB-triggered/22154/console" target="_blank">https://build.gluster.org/job/rackspace-regression-2GB-triggered/22154/console</a><br>
<div>
<div>
<div>
<div data-smartmail="gmail_signature">
<div dir="ltr">
<div><br>
</div>
--Atin<br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div></div></div><span><font color="#888888"><br><br clear="all"><br>-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><br></div>--Atin<br></div></div>
</font></span></div></div>
</blockquote></div><br><br clear="all"><br></div></div><span class=""><font color="#888888">-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><br></div>--Atin<br></div></div>
</font></span></div>
<br>_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br></blockquote></div><br></div></div></div></div>