From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: repating 208 failures
Date: Mon, 5 May 2014 07:44:07 +1000 [thread overview]
Message-ID: <20140504214407.GO26353@dastard> (raw)
In-Reply-To: <20140504094218.GA2920@infradead.org>
On Sun, May 04, 2014 at 02:42:18AM -0700, Christoph Hellwig wrote:
> Did anyone see failure like:
>
> generic/208 201s ... 200s
> umount: /mnt/test: device is busy.
> (In some cases useful info about processes that use
> the device is found by lsof(8) or fuser(1))
>
> which then abort xfstests? I've seen them occasionally for a long time,
> but these days they seem to happen more than 50% of the time.
I see it occassionally. Most often on a single processor test VM,
but not regularly enough to debug. It's an AIO stress test, so
perhaps there's a problem with delayed AIO reference counts, because
a second attempt to unmount the device will succeed....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-05-04 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 9:42 repating 208 failures Christoph Hellwig
2014-05-04 21:44 ` Dave Chinner [this message]
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=20140504214407.GO26353@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.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