| 1 |
If the "umount" command seems to be hanging next time, it is most likely |
| 2 |
due to cache writebacks. You can monitor this like so: |
| 3 |
|
| 4 |
$ watch "grep 'Dirty\|Writeback' /proc/meminfo" |
| 5 |
|
| 6 |
-Ramon |
| 7 |
|
| 8 |
On 15/06/2021 17:26, Dale wrote: |
| 9 |
> Jack wrote: |
| 10 |
>> On 6/15/21 10:21 AM, Dale wrote: |
| 11 |
>>> Ramon Fischer wrote: |
| 12 |
>>>> Hello Dale, |
| 13 |
>>>> |
| 14 |
>>>> this also happens to me sometimes and the culprit was an open process |
| 15 |
>>>> still accessing the hard drive. Maybe you can solve it like this: |
| 16 |
>>>> |
| 17 |
>>>> $ lsof /mnt/8tb |
| 18 |
>>>> zsh 8390 root cwd DIR 253,2 4096 27787265 /mnt/8tb |
| 19 |
>>>> $ kill 8390 |
| 20 |
>>>> $ lsof /mnt/8tb |
| 21 |
>>>> |
| 22 |
>>>> After that, you should be able to close the drive via "cryptsetup". |
| 23 |
>>>> |
| 24 |
>>>> -Ramon |
| 25 |
>>>> |
| 26 |
>>>> On 14/06/2021 06:50, Dale wrote: |
| 27 |
>>>>> root@fireball / # cryptsetup close 8tb |
| 28 |
>>>>> Device 8tb is still in use. |
| 29 |
>>>>> root@fireball / # mount | grep 8tb |
| 30 |
>>>>> root@fireball / # |
| 31 |
>>> I've tried lsof before, for both mount point and device, it shows |
| 32 |
>>> nothing open. It's weird. |
| 33 |
>>> |
| 34 |
>>> When this happened last night, just before I posted, I let the drive sit |
| 35 |
>>> there while I was doing updates. Later on, I tried to close it again |
| 36 |
>>> and it closed just fine. I hadn't done anything except let it sit |
| 37 |
>>> there. While I was glad it closed, I wonder why it did it. Did udev |
| 38 |
>>> finally catch up to the state of the drive? Did some other device |
| 39 |
>>> update and allow it to close? |
| 40 |
>>> |
| 41 |
>>> This is weird. Everything says it is ready to be closed but it thinks |
| 42 |
>>> something is open. I'm not sure what to point too for the problem. Yet |
| 43 |
>>> anyway. |
| 44 |
>>> |
| 45 |
>>> Thanks for the tip. It was worth mentioning. |
| 46 |
>>> |
| 47 |
>>> Dale |
| 48 |
>> Is it possible it was still syncing cache out to the physical drive? |
| 49 |
>> I wonder if iotop would show any activity for that drive if that's the |
| 50 |
>> case? |
| 51 |
>> |
| 52 |
>> Jack |
| 53 |
>> |
| 54 |
>> |
| 55 |
>> |
| 56 |
> |
| 57 |
> I may try that next time but the light had stopped blinking for several |
| 58 |
> minutes. Since it is a SMR drive, I always leave it running until I |
| 59 |
> can't feel the heads bumping around. I don't think it would be that |
| 60 |
> but, it's worth a try. It may lead to something. |
| 61 |
> |
| 62 |
> Will update when it does it again. |
| 63 |
> |
| 64 |
> Thanks. |
| 65 |
> |
| 66 |
> Dale |
| 67 |
> |
| 68 |
> :-) :-) |
| 69 |
> |
| 70 |
|
| 71 |
-- |
| 72 |
GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF |
Archives