On Tuesday 16 June 2015 02:19 AM, Emmanuel Dreyfus wrote:
Rajesh Joseph rjos...@redhat.com wrote:
Correct me if I am wrong, but I think interruptible is good with hard
mount. Which is good in real deployment scenario. Since we are talking
about test scripts, I thought soft mount along with
Vijay Bellur vbel...@redhat.com wrote:
We again hit this problem [1]. Can we use soft mount with some retries
and timeouts so that we don't need manual intervention to recover a hung VM?
Sure, but while there, I advise soft and interruptible mount (On NetBSD,
either mount -o soft,intr or mount
Emmanuel Dreyfus m...@netbsd.org wrote:
We again hit this problem [1]. Can we use soft mount with some retries and
timeouts so that we don't need manual intervention to recover a hung VM?
Um, looking at the current test scripts, we already do it.
A side note: It seems the hung case is
Emmanuel Dreyfus m...@netbsd.org wrote:
This means the dd process getting stuck in tstile because glusterfsd
died is probably a NetBSD kernel bug. I have to investigate.
I think I found the culprit, but fixing this will need some discussions
on NetBSD lists:
dd waits on a vnode lock owned by
Rajesh Joseph rjos...@redhat.com wrote:
Correct me if I am wrong, but I think interruptible is good with hard
mount. Which is good in real deployment scenario. Since we are talking
about test scripts, I thought soft mount along with timeout period can be
a good option to prevent hangs.
soft
Emmanuel,
I am not sure of the feasibility but just wanted to ask you. Do
you think there is a possibility to error out operations on the mount
when mount crashes instead of hanging? That would prevent a lot of
manual intervention even in future.
Pranith.
On 06/15/2015 01:35 PM, Niels
The hang we observe is not something specific to Gluster. I've
observed this kind of hangs when a filesystem which is in use goes
offline.
For example I've accidently shutdown machines which were being used
for mounting nfs, which lead to the client systems hanging completely
and required a hard
On Mon, Jun 15, 2015 at 04:38:54PM +0530, Pranith Kumar Karampuri wrote:
Emmanuel,
I am not sure of the feasibility but just wanted to ask you. Do you
think there is a possibility to error out operations on the mount when mount
crashes instead of hanging? That would prevent a lot of
On Monday 15 June 2015 05:21 PM, Kaushal M wrote:
The hang we observe is not something specific to Gluster. I've
observed this kind of hangs when a filesystem which is in use goes
offline.
For example I've accidently shutdown machines which were being used
for mounting nfs, which lead to the
On Mon, Jun 15, 2015 at 06:28:26PM +0530, Rajesh Joseph wrote:
For these test cases can't we use the nfs soft mount option to prevent the
hang?
soft mount will not be enough. I think you also need interruptible.
--
Emmanuel Dreyfus
m...@netbsd.org
On Monday 15 June 2015 06:34 PM, Emmanuel Dreyfus wrote:
On Mon, Jun 15, 2015 at 06:28:26PM +0530, Rajesh Joseph wrote:
For these test cases can't we use the nfs soft mount option to prevent the
hang?
soft mount will not be enough. I think you also need interruptible.
Correct me if I am
Hi,
sometimes the NetBSD regression tests hang with messages like this:
[12:29:07] ./tests/basic/mgmt_v3-locks.t
... ok79867 ms
No volumes present
mount_nfs: can't access /patchy: Permission denied
mount_nfs: can't access /patchy:
12 matches
Mail list logo
