Recent content by Petr.114

Hello, i am facing an issue with ZFS pool state. One of the drives in the pool was marked as faulted, but the state of the pool has been kept ONLINE, instead of changing to DEGRADED. The device of the pool failed previously that day and the pool correctly changed it's state to DEGRADED, but not...

There was no conclusion. Eventually the LXC was deleted and the issue did not occur with other LXCs.

Hi, the problem does not appear anymore, the next verify job did went successfully. Maybe it got fixed after garbage collector?

Sure, here is the whole log of the verification job and version of the software - it is the newest version of the 2.X from no-subscription repo. The verify job is running right now, so i will update after it ends.

Hello there, recently i had backup of LXC running (from ProxmoxVE) but it got interrupted by electricity outage. Now i cant see the backup anywhere, it does not existi in GUI, neither in filesystem directory, but it is getting verified for some reason, which leads to verification error. I...

Hi i just realized the same issue, the LXC is reporting same uptime as the hypervisor. pct shutdown/start wont help.

Here is system log 09:00-10:59

All disks completed the test without error. I have used command smartctl -t long /dev/sd[a-f] Right now, there is no issue, because since restart of the server, i have not made a rollbacke on that LXC.

Hello, previous week i faced the issue of process zfs unmount stuck while proceeding rollback of LXC. After that, also incoming replication got stuck (zfs receive). I though allright, its been long time since restart and there was new kernel and zfs installed but system was not rebooted. So i...

My bad, -r flag had to be in previous command zfs destroy -r rpool/data/vm-119-disk-0-old I'll edit it in my previous post, so people who find this will get it right. Yeah, snapshots were the same. Replication was not set up for this VM I think i got everything i needed. Thank you very much...

Well, i have used this command zfs send -Rp rpool/data/vm-172-disk-1 | zfs recv rpool/data/vm-172-disk-1-new but it didnt work, so i found out, that i need to create snapshot first and send the snapshot. Apparently there is not need for -o compression=on, because its already present on dataset...

Well i checked out how to use zfs send and zfs recv, but iam still not 100% sure and i really dont want to screw anything up. Is this procedure with -R option right? zfs send -R rpool/data/vm-172-disk-1 | zfs recv rpool/data/vm-172-disk-1-new zfs rename rpool/data/vm-172-disk-1...

Oh, good point. So i will set zfs set compression=on rpool/data on destination and if i get it right, i need to delete the replication and subvol-150-disk-0 dataset to start it freshly with compression enabled. Is there any possibility to compress other VM/CT datasets so i can prevent problems...

I did not do anything, pool is showing that i can upgrade for some time, but i did not proceed. The same thing happened on other proxmox server with different container so i tried to delete the replication (it destroyed CTs dataset too) and set it up again, but it did not helped and ended with...

Thank you for trying to help. Looks like there is planty of free space on the pool. root@backup:~$ zfs list -o space rpool NAME AVAIL USED USEDSNAP USEDDS USEDREFRESERV USEDCHILD rpool 4.23T 11.1T 0B 140K 0B 11.1T root@backup:~$ zpool list rpool NAME SIZE...