From: Nick Alcock <nick.alcock@oracle.com>
To: Eugene Loh via DTrace-devel <dtrace-devel@oss.oracle.com>
Cc: dtrace@lists.linux.dev, Eugene Loh <eugene.loh@oracle.com>
Subject: Re: [DTrace-devel] [PATCH] test: Retry umount if necessary
Date: Wed, 04 Dec 2024 00:08:12 +0000 [thread overview]
Message-ID: <87mshcwbrn.fsf@esperi.org.uk> (raw)
In-Reply-To: <1517ff3b-34e8-3654-a249-ec7164b66cce@oracle.com> (Eugene Loh via DTrace-devel's message of "Tue, 3 Dec 2024 16:06:04 -0500")
On 3 Dec 2024, Eugene Loh via DTrace-devel uttered the following:
> On 12/3/24 15:31, Nick Alcock wrote:
>
>> On 3 Dec 2024, eugene loh said:
>>
>>> From: Eugene Loh <eugene.loh@oracle.com>
>>>
>>> The io tests tst.local.sh and tst.wait.sh fail with some frequency,
>>> with error messages like "umount: $iodir: target is busy."
>> Can you just do a umount -l, then? The only caveat is that while this
>> will disconnect the mount from the mount tree immediately, the *actual
>> umount* might happen arbitrarily later -- is that a problem?
>
> Maybe? In test/triggers/doio.sh, you can see what's going on. In essence, we want to flush operations out. A lazy umount might
> not do that? I'm not sure.
No, it wouldn't. A simple sync should, though: once it returns, the bios
should have got all the way through the stack, IIRC.
--
NULL && (void)
next prev parent reply other threads:[~2024-12-04 0:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 20:16 [PATCH] test: Retry umount if necessary eugene.loh
2024-12-03 20:31 ` [DTrace-devel] " Nick Alcock
2024-12-03 21:06 ` Eugene Loh
2024-12-04 0:08 ` Nick Alcock [this message]
2025-01-06 20:50 ` Kris Van Hees
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mshcwbrn.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.