Jens Axboe writes:
> On 2012-09-28 17:02, Jeff Moyer wrote:
>> Jens Axboe writes:
>>
>>> On 2012-09-28 08:09, Dave Chinner wrote:
From: Dave Chinner
xfstests has always had random failures of tests due to loop devices
failing to be torn down and hence leaving filesytems tha
On 2012-09-28 16:38, Dave Jones wrote:
> 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 i
On 2012-09-28 17:02, Jeff Moyer wrote:
> Jens Axboe writes:
>
>> On 2012-09-28 08:09, Dave Chinner wrote:
>>> From: Dave Chinner
>>>
>>> xfstests has always had random failures of tests due to loop devices
>>> failing to be torn down and hence leaving filesytems that cannot be
>>> unmounted. Thi
Jens Axboe writes:
> On 2012-09-28 08:09, Dave Chinner wrote:
>> From: Dave Chinner
>>
>> xfstests has always had random failures of tests due to loop devices
>> failing to be torn down and hence leaving filesytems that cannot be
>> unmounted. This causes test runs to immediately stop.
>>
>> O
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
On 2012-09-28 08:09, Dave Chinner wrote:
> From: Dave Chinner
>
> xfstests has always had random failures of tests due to loop devices
> failing to be torn down and hence leaving filesytems that cannot be
> unmounted. This causes test runs to immediately stop.
>
> Over the past 6 or 7 years we'v
6 matches
Mail list logo