Zygo

> > bees won't recompress data for you > Doesn't bees create compressed temporary files to place dedupe extents? Only for partially duplicate extents where it can't find a duplicate...

> > It turned out to be not too painful to add compatibility code for older headers, similar to what bees already does for btrfs, so I pushed a fix...

> > 1. Only a subset of btrfs configurations can use the optimization. Any single-device filesystem, or any filesystem using raid0, raid10, raid5, or raid6, can't usefully do parallel reads...

> `exception type std::system_error: BTRFS_IOC_INO_LOOKUP: /var/lib/bees/8ff943b5-fbd2-4ea8-ad47-404a5961112c/beeshash.dat at fs.cc:488: Inappropriate ioctl for device` Yeah, that error should be captured and ignored. It's trying to find `beeshash.dat`'s subvol and inode numbers so...

Can confirm the ETA function is terrible. I had a 35-week ETA for 128K extents abruptly finish a few days ago. When I examined the logs in detail, I found...

> I'm just wondering why bees is talking this long to finish it's initial run for me for this new version. Can you post your progress table and your kernel...

> There seems to be some problems with the kernel 6.13. Tomorrow I will check on 6.12 to see if this is the cause of the problem. > > ```...

> I still get some usual output from startup thru “beesd[189647]: bees version v0.11-rc3-9-g85aba7b” up to “bees[189647]: Starting bees main loop...” and then the Great Silence. Check the status files...

> I've actualy saved multiple copies of my status files so here they are, I post the full status file in case anything in the could be useful. My Kernel...

A striped profile for data is not a good choice for this arrangement of drives. A striped profile like raid0 will try to fill the smallest drives first, leaving no...