From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nGvGPHzt_cV0 for ; Thu, 21 Feb 2013 23:08:57 +0100 (CET) Received: from awesome.dsw2k3.info (awesome.dsw2k3.info [IPv6:2a01:198:661:1f::3]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Thu, 21 Feb 2013 23:08:57 +0100 (CET) Date: Thu, 21 Feb 2013 23:08:52 +0100 From: Matthias Schniedermeyer Message-ID: <20130221220852.GA23353@citd.de> References: <20121129134313.GA14313@citd.de> <50B776CF.60501@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dm-crypt] force luksClose List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Benjamin Eberhardt Cc: dm-crypt@saout.de, Milan Broz On 21.02.2013 22:16, Benjamin Eberhardt wrote: > Hi all, > > the aboved mentioned problem happened to me again and this time i made sure > i would try to find every open file and close it first, then unmount the > partition but still luksClose did not work... > > The partition is unmounted but still i get this error: > > # cryptsetup luksClose sata_p1_2TBa > Device sata_p1_2TBa is busy. > > no open files on *sata* davice (both device and mountpoint are called the > same) >From my personal experience the things that DON'T show up in lsof are: mountpoints (and bind-mounts) nfs So if there is a mountpoint inside, you have to umount that first. If you have a NFS-export of the mountpoint or something inside the mountpoint you have to remove that export or stop NFS for the moment it takes to do the umount. There may be other things that don't show up in lsof, but i don't know about them. -- Matthias