Wonder whether the messing around with chown – with or without ZEVO driving – involved any snapshot.
Another hint, please: to the MacZFS areas for discussion of issues where MacZFS is driving. (I do follow things there.)
Moderators: jhartley, MSR734, nola
grahamperrin wrote:Wonder whether the messing around with chown – with or without ZEVO driving – involved any snapshot.
ilovezfs wrote:lundman wrote:Oh, I see. Everything I said about crashes and panics was based on my own testing for the last several hours with a ZEVO file vdev imported into MacZFS dev version. I could go into detail about each of them, but mostly they seem to be obviously known issues revolving around the lack of basic components like xattr. Many may not be ZEVO specific. As they say in the README: "Test this with the expectation of a kernel panic."
Oh ah, I didn't think of making sure it works with ZEVO. I was just sitting around looking for something to do. I'll do this next. Please feel free to create github issues if you find them, makes us look like a real project!
Edit:
Having just tried it, the ZEVO import itself seems fine, no panics or such issues. Clearly it is missing xattr though, but is fully usable in my simple test case.
Yes it imports fine, as I had said. But try messing around with chown. In my tests the command always hung necessitating a forced export via reboot and upon reimporting the pool, the original owner would still own the file.
ilovezfs wrote:My favorite bug (I doubt ZEVO specific) was that using "mv" to move a file from the pool to the HFS+ root filesystem would actually create a 0 sized file with the same name on the HFS+ filesystem and delete the original from the zfs pool. Awesome! That one definitely merits a github write up. For your tests are you in 10.8.2 or 10.8.3? I was in VMware with 10.8.3.
BjoKa wrote:This was actually caused by an internal, not-yet-ported function erroneously returning SUCCESS instead of ENOTSUPPORTED, confusing VFS. The missing function (and many more) have been ported by Lundman by now.ilovezfs wrote:My favorite bug (I doubt ZEVO specific) was that using "mv" to move a file from the pool to the HFS+ root filesystem would actually create a 0 sized file with the same name on the HFS+ filesystem and delete the original from the zfs pool. Awesome! That one definitely merits a github write up. For your tests are you in 10.8.2 or 10.8.3? I was in VMware with 10.8.3.
Hmm, that one is new.
May I ask you to try again with the latest source, and file a bug report for the "mv creates empty file" case at our GitHub tracker, if it still exists? If you do so, please include the full output of "sudo dtruss -n mv" while running the "mv" command. Many thanks!
ilovezfs wrote:Thanks for the update, Björn! I will happily test the latest source for the mv bug. Any chance you've done any general testing on Mavericks yet?
Users browsing this forum: ilovezfs and 3 guests