Haravikk

Is it actually necessary to have access to a Mac to test this? If HFS compressed data is just an extended attribute then can it not be compared between a...

> For example if compression on HFS+ files was enabled with afsctool -c -l9 /Volumes/1/ and you decided to rsync -alhcuXD --info=progress2,stats /Volumes/1/ /Volumes/2/ This command should cause the files...

Thanks so much for working on this! Just wanted to clarify; if a special device is removed or fails (with no redundancy), does the feature flag remain enabled? It sounds...

I would maybe also add to that list: 8. The contents of the `special` device are a lot more predictable – if properly sized and configured, and added at creation...

> You could then do the normal `zpool replace` to replace a bad special disks. Just to confirm, does this mean that zfs will repopulate the replacement `special` disk(s) with...

> If I only want (all) metadata to be read from my SSD, which one should I use? `CACHE` + `secondarycache=metadata` + `l2arc_rebuild_enabled=1` (+ `l2arc_noprefetch=0` + `l2arc_headroom=0`) or `SPECIAL` +...

> So what would be the use case for 1024B filenames if it's not supported by Linux? Does it work in FreeBSD? IIRC the limit might be 255 characters, including...

I haven't encountered any issues with specific characters; APFS and HFS are supposed to support all character except `NUL`. macOS does allow colons in file names which might cause possible...

> What's not allowed on Linux? (and is it file-system specific as well?) Ultimately the restrictions are file-system specific, and in theory it shouldn't matter if you transfer a file...

Do we know yet, what the actual impact of importing a dataset with truly longer (no xattr) file-names on a system that doesn't support them would be? Obviously if it...