CDebarry

Thank for the advice! I'll move everything to the nvme cache poll tonight. I don't know whats trying to connect to the server from my PC.. I usually have only one browser opened. Is there any way to figure this out? Thanks again!!

Here you go. New diagnostics. I guess everything is working fine. One thing that bothers me are those lines on log: Jun 29 09:19:51 VEYRON nginx: 2022/06/29 09:19:51 [error] 1572#1572: *605973 limiting requests, excess: 20.587 by zone "authlimit", client: 192.168.1.99, server: , request: "PROPFIND /login HTTP/1.1", host: "192.168.1.174" Jun 29 09:19:51 VEYRON nginx: 2022/06/29 09:19:51 [error] 1572#1572: *605975 limiting requests, excess: 20.571 by zone "authlimit", client: 192.168.1.99, server: , request: "PROPFIND /login HTTP/1.1", host: "192.168.1.174" Jun 29 09:19:51 VEYRON nginx: 2022/06/29 09:19:51 [error] 1572#1572: *605977 limiting requests, excess: 20.557 by zone "authlimit", client: 192.168.1.99, server: , request: "PROPFIND /login HTTP/1.1", host: "192.168.1.174" .99 machine is mine. Should I worry about them? veyron-diagnostics-20220629-1242.zip

Thank you!!!!!!!!!!!! It worked! Now, I have two pools. One, the nvme drive, will be used only for VMs and the other (ssd) will be used for temporary cache for the array on some shares.

Hi everyone, Thanks for the reply. Yesterday I wrote a reply but it got lost... sorry. The parity rebuild just finished. Data seams to be safe now! Great news. Data on cache drive does not get transferred to the array when mover runs. It doesn't recognize it as part of data from shared drives on the array. I can SSH into the cache drive and copy all data (VMs and some folders). So all cache data is safe now. I'm moving VMs to another box so I can test it. I'm also going to keep it as live backup or alternative to the main server. After copying all data how can I clear the array and start over? Is it possible to use the second drive as additional space to the array? Any options on GUI that I can use? I'm kindda of a newbie on linux. Thanks again!

Below syslog attached. Thank you guys!! veyron-syslog-20220627-1944.zip

Hi Guys, Hope you're doing fine! I found a problema that I cant solve on my own. Need help! I recently added one more disk to my cache pool so I could get more free space but I started having many problems that I cant solve... I had a 2Tb nvme as cache drive so I can run my VMs of of it but it got full. VMs begun pausing and causing issues to my users. To add some free space I added a 500Gb SSD drive to the pool. Took a while but it finished. When the processes finished I started obvserving really weird stuff on my VMs and logs as cache drive seemed to be read only... At this point VMs were locking and I started observing BTRFS erros on log. In addition to that (at the same time, of course) my USB stick failed (bad luck, I guess?). Got a new one, replaced the key. Data was safe! Nothing was lost, for what I can tell for now. BUT I see a lot of these on my logs: Jun 27 11:52:33 VEYRON kernel: blk_update_request: I/O error, dev loop2, sector 78080 op 0x1:(WRITE) flags 0x1800 phys_seg 16 prio class 0 Jun 27 11:52:33 VEYRON kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Jun 27 11:52:33 VEYRON kernel: blk_update_request: I/O error, dev loop2, sector 602368 op 0x1:(WRITE) flags 0x1800 phys_seg 16 prio class 0 Jun 27 11:52:33 VEYRON kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 Jun 27 11:52:33 VEYRON kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2438: errno=-5 IO failure (Error while writing out transaction) Jun 27 11:52:33 VEYRON kernel: BTRFS info (device loop2): forced readonly Jun 27 11:52:33 VEYRON kernel: BTRFS warning (device loop2): Skipping commit of aborted transaction. Jun 27 11:52:33 VEYRON kernel: BTRFS: error (device loop2) in cleanup_transaction:2011: errno=-5 IO failure Jun 27 11:52:33 VEYRON kernel: BTRFS error (device loop2): commit super ret -5 Any advice to how can I stop this erros? I guess cache is still in read only. Thank you! veyron-diagnostics-20220627-1634.zip