From: Dave Chinner <david@fromorbit.com>
To: "Carlos E. R." <carlos.e.r@opensuse.org>
Cc: XFS mailing list <xfs@oss.sgi.com>
Subject: Re: handling device or resource busy errors.
Date: Thu, 10 Dec 2015 13:18:31 +1100 [thread overview]
Message-ID: <20151210021831.GJ19802@dastard> (raw)
In-Reply-To: <5668DDE0.7050203@opensuse.org>
On Thu, Dec 10, 2015 at 03:05:20AM +0100, Carlos E. R. wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 2015-12-10 01:25, Ed Peschko wrote:
> > All,
> >
> > we are 'getting device or resource busy' errors which we *know*
> > are spurious (lsof shows nothing, no multipath daemon, the
> > partition that we are trying to access was just created).
>
> I don't know if this is the case, but sometimes, when creating
> filesystems under a graphical desktop (like gnome or kde) automatic
> systems on those desktops would probe the new partition and try to
> find its type and mount it, without action on my part. Even in the
> middle of formatting!
Yup, mounts/probing triggered by udev and/or i/d/fanotify events are
a PITA to discover, especially when they are only active for a
short period (like blkid scanning). In general that is enoughtime
to make the command in the script after partitioning fail, but not
enough time to run any diagnostics that will capture the cause...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-12-10 2:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 0:25 handling device or resource busy errors Ed Peschko
2015-12-10 2:05 ` Carlos E. R.
2015-12-10 2:18 ` Dave Chinner [this message]
2015-12-10 2:13 ` Dave Chinner
2015-12-10 7:58 ` Ed Peschko
2015-12-10 22:35 ` Dave Chinner
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=20151210021831.GJ19802@dastard \
--to=david@fromorbit.com \
--cc=carlos.e.r@opensuse.org \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox