1 |
Dale wrote: |
2 |
> Dale wrote: |
3 |
>> Dale wrote: |
4 |
>>> Jack wrote: |
5 |
>>>> Is it possible it was still syncing cache out to the physical drive? |
6 |
>>>> I wonder if iotop would show any activity for that drive if that's the |
7 |
>>>> case? |
8 |
>>>> |
9 |
>>>> Jack |
10 |
>>>> |
11 |
>>>> |
12 |
>>>> |
13 |
>>> I may try that next time but the light had stopped blinking for several |
14 |
>>> minutes. Since it is a SMR drive, I always leave it running until I |
15 |
>>> can't feel the heads bumping around. I don't think it would be that |
16 |
>>> but, it's worth a try. It may lead to something. |
17 |
>>> |
18 |
>>> Will update when it does it again. |
19 |
>>> |
20 |
>>> Thanks. |
21 |
>>> |
22 |
>>> Dale |
23 |
>>> |
24 |
>>> :-) :-) |
25 |
>>> |
26 |
>> I had to wait until I was doing backups again to try anything. The 6TB |
27 |
>> drive did fine. The 8TB drive is giving the in use error. The drive is |
28 |
>> unmounted but iotop didn't show anything and the light isn't blinking |
29 |
>> either. I'd think if it was flushing cache the light would flash and it |
30 |
>> would not umount. |
31 |
>> |
32 |
>> I tried the udev-trigger trick but it didn't work. I don't know how |
33 |
>> long it will stay 'in use' so if anyone has ideas, think and type fast. |
34 |
>> If not, may have to wait until next time to try again. |
35 |
>> |
36 |
>> Dale |
37 |
>> |
38 |
>> :-) :-) |
39 |
>> |
40 |
> |
41 |
> Some more info: |
42 |
> |
43 |
> |
44 |
> root@fireball / # lvs |
45 |
> LV VG Attr LSize Pool Origin Data% Meta% Move Log |
46 |
> Cpy%Sync Convert |
47 |
> Home2 Home2 -wi-ao---- |
48 |
> <12.74t |
49 |
> swap OS -wi-ao---- |
50 |
> 12.00g |
51 |
> usr OS -wi-ao---- |
52 |
> 35.00g |
53 |
> var OS -wi-ao---- |
54 |
> 52.00g |
55 |
> backup backup -wi-ao---- |
56 |
> 698.63g |
57 |
> root@fireball / # vgs |
58 |
> VG #PV #LV #SN Attr VSize VFree |
59 |
> Home2 2 1 0 wz--n- <12.74t 0 |
60 |
> OS 1 3 0 wz--n- <124.46g <25.46g |
61 |
> backup 1 1 0 wz--n- 698.63g 0 |
62 |
> root@fireball / # pvs |
63 |
> PV VG Fmt Attr PSize PFree |
64 |
> /dev/sda7 OS lvm2 a-- <124.46g <25.46g |
65 |
> /dev/sdb1 Home2 lvm2 a-- <5.46t 0 |
66 |
> /dev/sdc1 Home2 lvm2 a-- <7.28t 0 |
67 |
> /dev/sdd1 backup lvm2 a-- 698.63g 0 |
68 |
> root@fireball / # cryptsetup close 8tb |
69 |
> Device 8tb is still in use. |
70 |
> root@fireball / # |
71 |
> |
72 |
> |
73 |
> As you can see, lvm doesn't even show the device but it is still under |
74 |
> /dev as tho it is available. Weird. |
75 |
> |
76 |
> I found this but at the end, the command doesn't help me. I'm not sure |
77 |
> why. It does talk about using LUKS on top of LVM causing this problem. |
78 |
> Since the fix doesn't work, is this a different problem?? |
79 |
> |
80 |
> |
81 |
> https://linux-blog.anracom.com/tag/device-still-in-use/ |
82 |
> |
83 |
> |
84 |
> I've tried every command I can find and it still shows busy. I even |
85 |
> restarted udev and lvm. Still busy. |
86 |
> |
87 |
> Ideas? |
88 |
> |
89 |
> Dale |
90 |
> |
91 |
> :-) :-) |
92 |
> |
93 |
|
94 |
|
95 |
Found another tidbit of info that may shed some light on this problem. |
96 |
I'm not sure what it means tho. |
97 |
|
98 |
|
99 |
|
100 |
root@fireball / # lsblk |
101 |
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT |
102 |
<<<SNIP>>> |
103 |
sdj 8:144 1 7.3T 0 disk |
104 |
└─sdj1 8:145 1 7.3T 0 part |
105 |
└─8tb 254:5 0 7.3T 0 crypt /mnt/8tb |
106 |
sr0 11:0 1 1024M 0 rom |
107 |
root@fireball / # |
108 |
|
109 |
|
110 |
So, something called crypt seems to have it open. Now how do I tell it |
111 |
to go away? Hmmmm. Then I came up with this idea: |
112 |
|
113 |
|
114 |
root@fireball / # ps aux | grep crypt |
115 |
root 493 0.0 0.0 0 0 ? I< Jun13 0:00 [cryptd] |
116 |
root 11509 0.0 0.0 7728 2448 pts/2 S+ 00:30 0:00 grep |
117 |
--colour=auto crypt |
118 |
root 23667 0.0 0.0 0 0 ? I< Jun20 0:00 |
119 |
[kcryptd_io/254:] |
120 |
root 23668 0.0 0.0 0 0 ? I< Jun20 0:00 |
121 |
[kcryptd/254:5] |
122 |
root 23669 0.0 0.0 0 0 ? S Jun20 0:00 |
123 |
[dmcrypt_write/2] |
124 |
root@fireball / # |
125 |
|
126 |
|
127 |
So kcryptd is the offender it seems since it matches MAJ:MIN info. I |
128 |
assume that is kernel related not KDE. Can I just kill that process? |
129 |
Will it do damage if I kill it or is there a better way? |
130 |
|
131 |
Dale |
132 |
|
133 |
:-) :-) |