| 1 |
On 6/15/21 10:21 AM, Dale wrote: |
| 2 |
> Ramon Fischer wrote: |
| 3 |
>> Hello Dale, |
| 4 |
>> |
| 5 |
>> this also happens to me sometimes and the culprit was an open process |
| 6 |
>> still accessing the hard drive. Maybe you can solve it like this: |
| 7 |
>> |
| 8 |
>> $ lsof /mnt/8tb |
| 9 |
>> zsh 8390 root cwd DIR 253,2 4096 27787265 /mnt/8tb |
| 10 |
>> $ kill 8390 |
| 11 |
>> $ lsof /mnt/8tb |
| 12 |
>> |
| 13 |
>> After that, you should be able to close the drive via "cryptsetup". |
| 14 |
>> |
| 15 |
>> -Ramon |
| 16 |
>> |
| 17 |
>> On 14/06/2021 06:50, Dale wrote: |
| 18 |
>>> root@fireball / # cryptsetup close 8tb |
| 19 |
>>> Device 8tb is still in use. |
| 20 |
>>> root@fireball / # mount | grep 8tb |
| 21 |
>>> root@fireball / # |
| 22 |
> I've tried lsof before, for both mount point and device, it shows |
| 23 |
> nothing open. It's weird. |
| 24 |
> |
| 25 |
> When this happened last night, just before I posted, I let the drive sit |
| 26 |
> there while I was doing updates. Later on, I tried to close it again |
| 27 |
> and it closed just fine. I hadn't done anything except let it sit |
| 28 |
> there. While I was glad it closed, I wonder why it did it. Did udev |
| 29 |
> finally catch up to the state of the drive? Did some other device |
| 30 |
> update and allow it to close? |
| 31 |
> |
| 32 |
> This is weird. Everything says it is ready to be closed but it thinks |
| 33 |
> something is open. I'm not sure what to point too for the problem. Yet |
| 34 |
> anyway. |
| 35 |
> |
| 36 |
> Thanks for the tip. It was worth mentioning. |
| 37 |
> |
| 38 |
> Dale |
| 39 |
|
| 40 |
Is it possible it was still syncing cache out to the physical drive? I |
| 41 |
wonder if iotop would show any activity for that drive if that's the case? |
| 42 |
|
| 43 |
Jack |
Archives