linux-ext4 - Re: xfstests: device busy when umount

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4DD286E5.8090105@redhat.com>
Date:	Tue, 17 May 2011 09:32:05 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Yongqiang Yang <xiaoqiangnk@...il.com>
CC:	Ext4 Developers List <linux-ext4@...r.kernel.org>,
	Amir Goldstein <amir73il@...il.com>, xfs-oss <xfs@....sgi.com>
Subject: Re: xfstests: device busy when umount

On 5/17/11 4:03 AM, Yongqiang Yang wrote:
> Hi,
> 
> I noticed that all tests which contain 'device busy' errors have
> falloc operations.  Does the error have something to do with falloc?
> 

cc'ing xfs list since xfs devs maintain xfstests.

What tests have "device busy" errors?  What do the usual investigative
steps such as "lsof" and "fuser" tell you when this happens?

Are there loop devices that didn't get cleaned up, or processes that
have not terminated?

What tests have these problems?

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html