Search results

Hello, I experience a problem with LXC containers. When I shutdown one of them and attempt to start it again, it stucks and node statistics freeze (question marks in GUI, hanging lxc-info processes in htop). Debug start log file looks like this: PVE versions are these: And container config...

Nothing upgraded with dist-upgrade: root@prox1:~# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Hello, I am experiencing a problem with newest kernel available in pve-no-subscription repository, that's 4.15.18-10-pve. I've upgraded my system with apt update and apt upgrade, current versions are: root@prox1:~# pveversion -v proxmox-ve: 5.3-1 (running kernel: 4.15.18-10-pve) pve-manager...

What exactly can be HW problem?

Hello, please, do you have any other ideas? That Proxmox instance we were talking about behaves very unstable (random freezes etc.), I would be thankful for any ideas that might solve that problem by successfully moving broken data away. Thanks a lot David

I have ECC RAMs (non-ECC was reason of the initial corruption) now. Yes, it is. I've done scrub multiple times.

I have: disabled swap set arc_min to 4GB set arc_max to 8GB set zfs_compressed_arc_enabled to 0 And the system freezed completely (IO delay 90%). This was logged into dmesg: [ 7629.092954] Buffer I/O error on dev zd64, logical block 28727886, async page read [ 7629.095030] Buffer I/O error...

Disabling ARC cache compression isn't going to help?

That looks possible. So, how can I workaround that problem please?

I have some weird ARC cache problems longer time. It swaps a bit and arcstat says it usually uses max. 1GB of RAM (shortly after boot a lot is used, but then it drops in one second to around 1GB) out of 32GB. My /sys/module/zfs/parameters/zfs_arc_min and zfs_arc_max equals zero. Swap is on ZFS.

I ran this: dd if=/dev/zvol/rpool/data/vm-101-disk-1 bs=4096 | pv | dd bs=4096 of=/dev/null And got this: 109GiB 1:24:06 [21.7MiB/s] [...

Tried it too - it fails, sometimes even with kernel panic (saying something with VERIFY3()).

I've tried it without parameters and it failed again: root@prox2:~# zfs send rpool/data/vm-101-disk-1@actual | pv | zfs recv rpool/data/offload2-vm-101-disk-1 113GiB 1:07:52 [28.5MiB/s] [ <=> ] internal error: Invalid...

Exactly same result as in previous attempt.

Found out this: "The 'Invalid exchange' error you're seeing is EBADE which was what ZFS uses internally to report a checksum error." (here) - what doesn't make sense, because cat /sys/module/zfs/parameters/zfs_send_corrupt_data still gives 1. It again looks to me that code seen here doesn't...

Unfortunately, issued following command: zfs send rpool/data/vm-101-disk-1 > ./vm-191-disk-1-zfs-send and ended up with this: internal error: Invalid exchange Aborted Any other tip?

Sorry :) for being arrogant. I haven't got a lot of experiences with ZFS. I will try what you are suggesting with sending zfs send into file and tell you the result.

Look at line 895 in dmu_send.c https://github.com/zfsonlinux/zfs/blob/master/module/zfs/dmu_send.c#L895 - when IO error occurs, it decides using mentioned tunable. When the tunable is set to true, EIO error is not thrown, problematic data are just overwritten in zfs send stream.

It's exactly this code in ZFS:https://github.com/zfsonlinux/zfs/commit/fd8febbd1e6ff3d3eec6b9d395ab65400769da19. @fabian is the code used for building current Proxmox ZFS the same?

@Nemesiz I don't understand. What I understand from https://github.com/zfsonlinux/zfs/blob/master/module/zfs/dmu_send.c, when zfs send arrives to some data that issue IO error, it: a) fails, when /sys/modules/zfs/parameters/zfs_send_corrupt_data is set on 0 b) otherwise, it replaces invalid data...