Thanks for compiling a new version.
Ok, I've done it.
All went well. Creating, copying data on it, deleting data, export, import.
Made 2 datasets (with xattr=dir and xattr=sa) and all was good. I could copy Mail.app and Libreoffice.app (and other files) with no sudden reboot.
But...
As I mentioned in an earlier post here, I had now again the problem with a pdf that I edited with skim.app (to highlight parts of the text). When I copy it with finder, rsync or cp from hfs to "xattr=sa" it transfered only a fraction of the xattr where skim.app saves the highlighted text, and there are no highlights anymore in skim.app. Copying to "dir" works.
From 149 xattr entries the copy process transfered only 33.
- Code: Select all
$ xattr /Volumes/WD2TB/Personal\ Development/Tony\ Robbins/Re-Awaken_the_Giant_Within_Highres.pdf | wc -l
149
$ xattr /Volumes/zfs/sa/Re-Awaken_the_Giant_Within_Highres.pdf | wc -l
33
I tested another file that has no connection to skim.app, just a file with almost the same amount of xattr contents. And the xattr are the same after copying it to the dataset with "xattr=sa".
The main difference to the pdf is that it has only 2 xattr entries, com.apple.FinderInfo and com.apple.ResourceFork.
The complete amount of contents of both files (number of lines, words and bytes) is almost the same but the amount of xattr entries is different (149 vs 2).
- Code: Select all
$ xattr -l /Volumes/WD2TB/Personal\ Development/Tony\ Robbins/Re-Awaken_the_Giant_Within_Highres.pdf | wc
18730 333304 1448653
$ xattr -l "/Users/arne/AddressBook (4)" | wc
18050 326190 1407634
My conclusion till now is
- there might be a limit of the numbers of xattr entries (only 33 of the pdf where transfered)
- or the skim.app makes something weird with the entries cause the other file was copied with all xattr
Thinking about not using "sa" in the future, so when I finally switch to 2.1.6 I copy all data to the new pool with "xattr=dir".
I use "sa" on 1.9.4 cause it seems a little faster than "dir" out of less overhead when writing and reading the xattr.
I wish I could find out if it is really only skim that makes those problems with "sa".