Recent content by bengtjonsson

Copied one "problem" vm to a PVE 7.2 cluster and "file restore" seems to work ok. Going to copy over two more vm's and do more testing.

Switching to krbd is out of scope due to the amount of vm's and all "unknowns" that will bring. Any plans for "finding out more"? /Bengt

Hmm, it certainly looks like it due to the test results. I currently do backups by; 1. fsfreeze 2. Create Ceph snapshot 3. fsthaw The Ceph snapshot is mountable with no problems either directly (map snapshot and mount) or doing a ceph image export/import. Any thoughts?

Tested, backup ok with "writeback" and RBD driver.

Hi, A new backup, of an always "failing" vm, with "no cache" on btrfs disks looks ok. Disk content is shown. Ceph is our main storage and will continue to be so, no other storage is available. /Bengt

proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 7.1-6 (running version: 7.1-6/4e61e21c) pve-kernel-5.13: 7.1-4 pve-kernel-helper: 7.1-4 pve-kernel-5.11: 7.0-10 pve-kernel-5.13.19-1-pve: 5.13.19-3 pve-kernel-5.11.22-7-pve: 5.11.22-12 pve-kernel-5.11.22-5-pve: 5.11.22-10...

Hypervisor storage is an external ceph cluster, version 16.2.6. Storage config: content images,rootdir krbd 0 pool abc VM config: agent: 1 bootdisk: scsi0 cores: 10 cpu: Broadwell hotplug: disk,network,usb,memory,cpu ide2: none,media=cdrom memory: 1033216 name...

We were able to manually recover /dev/sda2 (root) by "btrfs rescue chunk-recover" Same type of errors on /dev/sdd, tried "btrfs rescue chunk-recover " to recover from that but gave up after 5 attempts where "wanted" increased by one after each run. It's a test so no panic. BTRFS error (device...

Hi, Yes, we use guest agent to perform backups. We use hook script to perform database write suspend/resume. It seems to work ok but depending on db activity it can take some time. Restoring a backup where disk content is not shown in GUI: vm not booting due to btrfs errors, as if no fs-freeze...

If it fails, it fails for the whole lifetime of the snapshot. If it works, it works for the whole lifetime of the snapshot. And, as mentioned, I have vm's where all snapshots are ok, and I have at least one where no snapshots works. /Bengt

Any idèa, anyone?

Attached is two log files, one ok and one failing to list content of drive-scsi1. Note: mounting '/dev/vdc' succeeded, fstype: 'btrfs' vs. mount error on '/dev/vdc' (btrfs) - EIO: I/O error

The file system contains ca. 23 GB and the majority is static files. For this vm it varies in which backup the disk content is available. Sometimes the oldest, the newest or in between. Never seen more than one (7 days retention).

Same vm, other backup:

drive-scsi1.img.fidx is not possible to expand