Skip to contentSkip to conversation

repating 208 failures

DISCUSSION Christoph Hellwig 2 participants 2 messages May 4, 2014

lore
Share & tools
lore
#0 lore raw

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.

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#1 lore raw
Quoted 9 lines · Christoph Hellwig

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.

Signature · 7 lines
Dave Chinner
[email protected]

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs