Item too large for tree

[Scorg]

trafficstars

Basically title. Sorry for not much context, don't know what else to add.

[maharmstone]

It'd help if you pasted the console output here.

[Scorg]

Unfortunately I lost it, but it wasn't much. The program calculated checksums (stopped at 1600% completion) and the next line was just Item too large for tree. I also manually converted the drive so probably won't be able to reproduce 1 to 1.

Could you give some pointers as to why this can happen? I'm not very knowledgeable about btrfs and there is not much comments in the code.

Thanks

[FelicitusNeko]

Here's an output with this line:

Not using compression.
Using SHA256 for checksums.
\$RECYCLE.BIN\[snipped Windows user ID]\$R6RCKKF.png: Skipping compressed ADS :Zone.Identifier
\$RECYCLE.BIN\[snipped Windows user ID]\$RCMFLDY.png: Skipping compressed ADS :Zone.Identifier
\$RECYCLE.BIN\[snipped Windows user ID]\$RCNJ5R5.png: Skipping compressed ADS :Zone.Identifier
Processing inode 139414 / 139414 (100.0%)
Mapped 109453 inodes directly.
Rewrote 273 inodes.
Inlined 8702 inodes.
Updating directory sizes
Calculating checksums 537159476 / 537159476 (100.0%)
Item too large for tree.

The volume still shows as NTFS, even after disconnecting/reconnecting it.

[maharmstone]

Thanks @FelicitusNeko. Does this still happen if you choose CRC32 instead of SHA256?

[FelicitusNeko]

I'll have to give that a try. However, it's a decently large volume, and the process took almost 24 hours the first time around, so it might be a couple of days before I can start that up again.

[FelicitusNeko]

I have given it a try with CRC32C. The output was identical to above, except "Using CRC32C for checksums."

[FelicitusNeko]

I've tried a few things:

• Removing some of the largest files
• Removing some of the files with the longest path lengths
• Reducing the total number of files in general (mostly by deleting some redundant duplicates or compressing into 7z archives)
• Defragmenting and consolidating free space

Nothing has worked so far, and "Item too large for tree" is too ambiguous of an error message for me to even know if there's something I can do about it. :/