William J. Franck
William J. Franck
JFYI, I did same test to check on my MB / Catalina. ProductName: Mac OS X ProductVersion: 10.15.7 BuildVersion: 19H1217 zfs-macOS-2.0.1-1 zfs-kmod-2.0.1-1 Result is OK "Unmount successful for /Volumes/foo/bar" (no...
Did same check on another MB-Air 2012 with BigSur ProductName: macOS ProductVersion: 11.4 BuildVersion: 20F71 zfs-macOS-2.0.1-1 zfs-kmod-2.0.1-1 Indeed, same issue $ sudo zfs unmount foo/bar >Unmount failed for /Volumes/foo/bar >umount:...
On BigSur ``` $ diskutil list disk2 disk3 ``` >/dev/disk2 (disk image): > #: TYPE NAME SIZE IDENTIFIER > 0: GUID_partition_scheme +655.4 MB disk2 > 1: ZFS foo 644.9 MB...
No, Panic occurred only once (for now, after about 10 days). Since the panic occurence, I did some intensive `zfs send`; `zfs receive` without trouble.
One zpool `Bay` is build on 4 external 4TB disks in a HD-Enclosure attached through eSata (+ eSata PCIe Controller Card) (about 150 MB/sec) One zpool `LaCie` is on external...
OK I will set `nvram boot-args="-v keepsyms=1"` Thank you for this.
Hello JMoVS, Thanks for the follow-up :-) * Typo `APFS` corrected in description * MountPoint : (with `com.apple.devdisk=poolonly` * yes, directory was empty. I did several tests, with 2 different...
(sorry bad manoeuvre has closed this issue !!)
* Terminal.app was already in _Full disk access_ * some more testing with `cmpxat` v2 from [The Eclectic Light Company](https://eclecticlight.co/extended-attributes-xattrs) on some real Mail.app file `7.emlx` * `xattr -lv 7.emlx`...
Some clue : While I was trying to do some more test cases, with copy of /Users/_myUser_ to a ZFS zvol with APFS format, say ` sudo cp -a /Users/rover-yachts.5...