| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: repating 208 failures |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Mon, 5 May 2014 07:44:07 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20140504094218.GA2920@xxxxxxxxxxxxx> |
| References: | <20140504094218.GA2920@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_iflush_int: Bad inode, xfs_do_force_shutdown from xfs_inode.c during file copy, Dave Chinner |
|---|---|
| Next by Date: | Re: [PATCH] common: use a relative path to fsstress, Dave Chinner |
| Previous by Thread: | repating 208 failures, Christoph Hellwig |
| Next by Thread: | [PATCH] common: use a relative path to fsstress, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |