Jaster

Thanks, that solves it for me

Hi Guys, this keeps happening with different VMs Randomly, trying to start a VM this message pops up. If I restart some running VMs I can start also the one which would not start before and the issue is gone. Super annoying and keeps happening

Corruption can occur any time, so my questions is how to overcome it. Full backup of the drive, sure... However if this is the risky part about BTRFS, I'd like to cover this with a little bit less effort (hardware wise). So... would it be possible to create a backup or an "external" RAID just for the file system? E.g. Having the array with all HDDs protected by parity, while the file system resides on a RAID 5/10 Pool of SSDs. Or just have a job that back ups the file system on an hourly/daily basis?

I'm not talking about an empty file system. The data is protected by the parity. The Filesystem is not - so why not back it up?

Sorry if it sounds silly, but is there a way to backup/replicate the filesystem without the actual data?

Lets say I run into a filesystem corruption, can I just restore the whole disk with paraties in place?

So the increased risk is losing the filesystem on a disk, but this can be recovered by the usual parity rebuild? If I want to backup something from another pool, I need to create an entry point based on a disk instead of a share, right? Anything else I do not see? Is there something like a "save procedure" to migrate from xfs to btrfs?

How does Parity interact with this? Can I still lose a disk and restore it? Shares will not work across disks, but I rather have to create share by disk?...

I saw it is possible to run the Array with BTRFS drives. As I'm using more BTRFS features (snapshots for backups, etc) I'd like to know if it is a viable option and if there is any risk involved migrating from XFS? Right now I'm running an array with two paraties (XFS), a nvme raid 0 (BTRFS), another SSD raid 10 (BTRFS) and a backup raid 10 (BTRFS) with HDDs. My Idea would be to integrate the backup raid into the array and perform backups to the array rather then to a separate instance. Further I could stripe the SSDs to get more space there and have also backups inside the array.

Basicly, even if I change the location back to where it was, the VM won't boot anymore..?!

I've been trying to move some vm images (windows 10) to a btrfs snapshot folder, but it apprears they don't boot anymore. What did I do wrong here?

Starting VMs takes way longer than it used to be on 6.8.3. It takes about ~7Minutes to get my VMs with passthrough up and running. The Docker and Apps tab are loading for about ~30 seconds on every refresh. In general it feels like VM's are slower over all - I'm running on an XFS Cache right now.

New Issue: I can't unpin CPUs from dockers. When I do so in pinning and I press apply, everything seems fine. After entering the pinning settings, everything is back to "as it was". If I go into the container settings for the docker and change settings there, it persists.

knowlage-diagnostics-20201026-2051.zip Hi guys, I see tons of unexpected GSO type: 0x0, gso_size 35, hdr_len 89 Messages - I attached the diagnostics. Anything I can/should do about it?

Seems like that does the job, but I don't feel very 'save' running a beta. Any way to include the driver into a stable build?