On Fri, Sep 28, 2012 at 10:41:50AM +0200, Jens Axboe wrote:
> > Turns out that blkid is running simultaneously with losetup -d, and
> > so it sees an elevated reference count and returns EBUSY. But why
> > is blkid running? It's obvious, isn't it? udev has decided to try
> > and find out what is on the block device as a result of a creation
> > notification. And it is racing with mkfs, so might still be scanning
> > the device when mkfs finishes and we try to tear it down.
> >
> I hear that %^#@#! blkid behavior, it is such a pain in the neck. I
> don't know how many times I've had to explain that behaviour to people
> who run write testing with tracing, wonder wtf there are reads in the
> trace.
Could this problem explain this bug too ?
https://bugzilla.redhat.com/show_bug.cgi?id=853674
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
