From: Ramon Fischer <Ramon_Fischer@hotmail.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] cryptsetup close and device in use when it is not
Date: Tue, 15 Jun 2021 21:04:01 +0200 [thread overview]
Message-ID: <AM6PR10MB24400D397A61BAA254F48C14EF309@AM6PR10MB2440.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <649753f7-5dcd-1842-875d-d637ef754b9f@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2353 bytes --]
If the "umount" command seems to be hanging next time, it is most likely
due to cache writebacks. You can monitor this like so:
$ watch "grep 'Dirty\|Writeback' /proc/meminfo"
-Ramon
On 15/06/2021 17:26, Dale wrote:
> Jack wrote:
>> On 6/15/21 10:21 AM, Dale wrote:
>>> 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
>>>>
>>>> On 14/06/2021 06:50, Dale wrote:
>>>>> root@fireball / # cryptsetup close 8tb
>>>>> Device 8tb is still in use.
>>>>> root@fireball / # mount | grep 8tb
>>>>> root@fireball / #
>>> I've tried lsof before, for both mount point and device, it shows
>>> nothing open. It's weird.
>>>
>>> When this happened last night, just before I posted, I let the drive sit
>>> there while I was doing updates. Later on, I tried to close it again
>>> and it closed just fine. I hadn't done anything except let it sit
>>> there. While I was glad it closed, I wonder why it did it. Did udev
>>> finally catch up to the state of the drive? Did some other device
>>> update and allow it to close?
>>>
>>> This is weird. Everything says it is ready to be closed but it thinks
>>> something is open. I'm not sure what to point too for the problem. Yet
>>> anyway.
>>>
>>> Thanks for the tip. It was worth mentioning.
>>>
>>> Dale
>> Is it possible it was still syncing cache out to the physical drive?
>> I wonder if iotop would show any activity for that drive if that's the
>> case?
>>
>> Jack
>>
>>
>>
>
> I may try that next time but the light had stopped blinking for several
> minutes. Since it is a SMR drive, I always leave it running until I
> can't feel the heads bumping around. I don't think it would be that
> but, it's worth a try. It may lead to something.
>
> Will update when it does it again.
>
> Thanks.
>
> Dale
>
> :-) :-)
>
--
GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-06-15 19:04 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 4:50 [gentoo-user] cryptsetup close and device in use when it is not Dale
2021-06-15 13:48 ` Ramon Fischer
2021-06-15 14:21 ` Dale
2021-06-15 14:52 ` Jack
2021-06-15 15:26 ` Dale
2021-06-15 19:04 ` Ramon Fischer [this message]
2021-06-21 4:18 ` Dale
2021-06-21 4:49 ` Dale
2021-06-21 5:41 ` Dale
2021-06-21 5:59 ` Dale
2021-06-28 3:35 ` Dale
2021-07-05 3:19 ` Dale
2021-07-06 18:40 ` Ramon Fischer
2021-07-06 19:43 ` Dale
2021-07-07 14:48 ` Dr Rainer Woitok
2021-07-07 18:08 ` Dale
2021-07-08 8:20 ` Ramon Fischer
2021-07-12 8:31 ` Dale
2021-07-12 13:14 ` Ramon Fischer
2021-08-02 13:33 ` Dale
2021-08-09 13:38 ` Ramon Fischer
2021-09-19 11:55 ` Dale
2021-07-25 20:29 ` Frank Steinmetzger
2021-07-25 23:10 ` Dale
2021-07-26 21:00 ` Frank Steinmetzger
2021-07-26 22:48 ` Dale
2021-07-29 16:46 ` Wols Lists
2021-07-29 20:55 ` [gentoo-user] [OT] SMR drives (WAS: cryptsetup close and device in use when it is not) Frank Steinmetzger
2021-07-29 21:31 ` Frank Steinmetzger
2021-07-30 12:48 ` Frank Steinmetzger
2021-07-30 5:14 ` William Kenworthy
2021-07-30 14:29 ` Rich Freeman
2021-07-30 16:50 ` antlists
2021-07-30 18:38 ` Rich Freeman
2021-07-31 3:14 ` William Kenworthy
2021-07-31 3:50 ` Wols Lists
2021-07-31 4:58 ` William Kenworthy
2021-07-31 12:12 ` Rich Freeman
2021-08-01 0:41 ` Frank Steinmetzger
2021-08-01 0:56 ` Rich Freeman
2021-07-31 16:38 ` antlists
2021-08-01 0:50 ` Frank Steinmetzger
2021-08-01 3:36 ` William Kenworthy
2021-08-01 3:46 ` William Kenworthy
2021-08-01 21:38 ` Frank Steinmetzger
2021-08-02 5:38 ` William Kenworthy
2021-08-02 21:52 ` Frank Steinmetzger
2021-08-02 23:10 ` William Kenworthy
2021-08-03 8:18 ` Frank Steinmetzger
2021-08-05 20:40 ` Frank Steinmetzger
2021-08-06 7:22 ` William Kenworthy
2021-08-01 21:55 ` Frank Steinmetzger
2021-08-02 6:12 ` William Kenworthy
2021-08-02 22:03 ` Frank Steinmetzger
2021-08-02 23:35 ` William Kenworthy
2021-08-01 3:41 ` William Kenworthy
2021-08-01 21:41 ` Frank Steinmetzger
2021-07-31 12:21 ` Rich Freeman
2021-07-31 12:59 ` William Kenworthy
2021-07-31 13:30 ` Rich Freeman
2021-08-01 3:05 ` William Kenworthy
2021-08-01 11:37 ` Rich Freeman
2021-07-31 5:23 ` William Kenworthy
2021-06-15 17:48 ` [gentoo-user] Re: cryptsetup close and device in use when it is not Remy Blank
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM6PR10MB24400D397A61BAA254F48C14EF309@AM6PR10MB2440.EURPRD10.PROD.OUTLOOK.COM \
--to=ramon_fischer@hotmail.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox