[Gluster-infra] [Bug 1359879] Cleanup hanging on NetBSD machines

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1359879

Nigel Babu  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |DUPLICATE
Last Closed||2016-08-23 07:31:21



--- Comment #3 from Nigel Babu  ---
This is a dupe of bug 1368441, which is now fixed. The issues that's causing
umount to hang is being resolved in bug 1369401

*** This bug has been marked as a duplicate of bug 1368441 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=MF9RPaaXZ7=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1359879] Cleanup hanging on NetBSD machines

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1359879



--- Comment #2 from Nigel Babu  ---
Fun fact, the regression.sh on NetBSD machines is a bit different from our
normal ones and already has pkill to kill errant gluster processes.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=niUQqrk60d=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1359879] Cleanup hanging on NetBSD machines

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1359879

Kaleb KEITHLEY  changed:

   What|Removed |Added

   Keywords||Triaged
   Assignee|b...@gluster.org|nig...@redhat.com



-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=guFM5HeaP8=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1359879] Cleanup hanging on NetBSD machines

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1359879

Nigel Babu  changed:

   What|Removed |Added

 CC||nig...@redhat.com



--- Comment #1 from Nigel Babu  ---
As much as I hate to do this, I've added a `pkill gluster` to the start of the
netbsd regression runs so we avoid this.

I suspect this maybe my fault. I changed the default timeout for netbsd
regression to 200 minutes the other day. If a job was killed mid regression
run, it may have left the machine in an inconsistent state.

I would much rather our regression.sh wrote a PID file and we kill only if the
PID file pointed to a non-existent process.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=X3DbcE8gu1=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra