From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 2419A1382C5 for ; Tue, 15 Jun 2021 17:48:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CD93BE0872; Tue, 15 Jun 2021 17:48:28 +0000 (UTC) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 762D5E086A for ; Tue, 15 Jun 2021 17:48:28 +0000 (UTC) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1ltDAo-0004sz-Oy for gentoo-user@lists.gentoo.org; Tue, 15 Jun 2021 19:48:26 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Remy Blank Subject: [gentoo-user] Re: cryptsetup close and device in use when it is not Date: Tue, 15 Jun 2021 19:48:22 +0200 Message-ID: References: <70a1b488-c49e-6a94-a9a9-37eeb2ff4399@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20100305 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0 In-Reply-To: Content-Language: en-US X-Archives-Salt: 90d47a1e-4956-4aa2-bae6-e418bf685a07 X-Archives-Hash: cf057b48992c7466c59a54a87fc3523a Dale wrote on 15/06/2021 16:21: > Ramon Fischer wrote: >> Hello Dale, >> >> this also happens to me sometimes and the culprit was an open process >> still accessing the hard drive. Maybe you can solve it like this: >> >>    $ lsof /mnt/8tb >>    zsh       8390 root  cwd    DIR  253,2      4096 27787265 /mnt/8tb >>    $ kill 8390 >>    $ lsof /mnt/8tb >> >> After that, you should be able to close the drive via "cryptsetup". >> >> -Ramon >> > > I've tried lsof before, for both mount point and device, it shows > nothing open.  It's weird. When this happens here, it's because I accessed the drive over NFS. The NFS server sometimes keeps mount points active, and they don't show up in the output of lsof probably because the NFS server is in-kernel, so there are no processes associated with it. Restarting the NFS server allows unmounting. -- Remy