Kai Krakow
Kai Krakow
@lilydjwg This should probably be discussed in #260: kernel 6.6.28, I'm running only LTS versions. Do you know what 6.8 changed that may have improved it?
> For many years it was the opposite--create/fsync/rename would trigger bugs in btrfs A lot of software uses that pattern without issues. Maybe that has been a problem only when...
I'm not sure if the DB overfilling is really such a big issue. In the end, it's okay to push out older hashes and keep the hashes for big blocks,...
`beesd` ;-)
Did you install it or run it from the source directory?
I think you did not install the build, or installed to a completely different directory, so the service file won't be in an expected location.
Try using `chattr +m` on your fileIO backend storage directory. It will disable compression for newly created files, so you'd need to re-create the files (not just move, but copy,...
Then I suggest creating a subvol for the images: `btrfs sub create /mnt/point/tobtrfs/images`, then `chattr +m` that image directory. Now, you can `rsync -av *.img images/ --remove-source-files` to copy all...
> I discovered that the image file itself already has the m attribute. Wouldn't this mean that compression is already disabled? Okay, so your iSCSI tools already take care of...
If you suffer performance problems, you should consider a kernel patch to put btrfs meta-data on a dedicated SSD, also maybe use bcache to cache IO reads and writes. I...