Closed Laski closed 3 years ago
Hi, is that on ubuntu 18.04 ?
I have these messages here too, I don't know, if bees does some work, it seem just to sit there.
I was experimenting with compression, I mounted compression-force=zstd:3 instead of compress=zstd:3 and then run btrfs filesystem defragment -czstd -v -r ./
on my data. Could this have some effect on this?
This filesystem is for nakivo repository in "incremental with full backups" format, i want to see, if it can deduplicate full backups.
If the stats file isn't showing much more than what's quoted above, then it's not working. Usually, it should be full of a lot of numbers for both "TOTAL" and "RATES". One problem may be a broken beeshash.dat
or a broken beescrawl.dat
in $BEESHOME
- probably the latter. Try to delete that latter file, if it still doesn't work, recreate the big hash file, too.
Ubuntu doesn't use standard kernel version numbering.
Ubuntu version Linux 5.4.0-54-generic contains the 5.4 regression a48b73eca4ce "btrfs: fix potential deadlock in the search ioctl" but not the fix 1c78544eaa46 "btrfs: fix wrong address when faulting in pages in the search ioctl".
Upgrade or downgrade the kernel. This particular kernel version will not work.
Yeah, i was trying to match ubuntu version to some real kernel version. Anyway, i have installed 5.4.0-55-generic from kernel-ppa, it seems to have this fixed, i cannot find detailed changelog anywhere (i have seen some changelog in git, but it seems to be kernel for raspberry).
But bees seems to be humming again. Thanks
Thanks for your help! Really appreciated.
For anyone interested, I downgraded to 5.4.0-53-generic and the problem seems to be there too. It will be fixed on upstream focal when https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896824 is released on the next SRU. Personally, I think I'll wait till then.
As this is not bees fault and a fix is already "available" I think it makes sense to close this.
Once in a while, the
crawl_master
logs:The other workers doesn't seem to be doing anything:
Perhaps this is normal and I'm misunderstanding something, but I looked also for closed issues and documentation and couldn't find any with this error.
I'm on the latest
master
commit (1b9b437c11dd858213c963b14fe7771ab630c2b8)