Now where do we go?

Moderators: jhartley, MSR734, nola

Re: Now where do we go?

Post by grahamperrin » Thu Jun 06, 2013 12:21 am

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.)
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Re: Now where do we go?

Post by ilovezfs » Thu Jun 06, 2013 2:21 am

grahamperrin wrote:Wonder whether the messing around with chown – with or without ZEVO driving – involved any snapshot.

Not unless it was created by magic. This was a very very simple test pool created on the physical computer by ZEVO, and then transferred back and forth between the physical computer running ZEVO and a virtual machine running MacZFS dev version.
ilovezfs Online


 
Posts: 249
Joined: Sun Feb 10, 2013 9:02 am

Re: Now where do we go?

Post by BjoKa » Sun Jun 16, 2013 8:06 am

Just to clarify this ...

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.


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!

-- Björn
BjoKa Offline


 
Posts: 14
Joined: Sat Feb 02, 2013 3:18 pm
Location: Germany

Re: Now where do we go?

Post by ilovezfs » Sun Jun 16, 2013 8:22 am

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!

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?
ilovezfs Online


 
Posts: 249
Joined: Sun Feb 10, 2013 9:02 am

Re: Now where do we go?

Post by BjoKa » Sun Jun 16, 2013 8:48 am

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?


No, Maverick refuses to load the kext, as far as I know (I don't have Maverick from testing, Lundman has and I may not have the latest information).
BjoKa Offline


 
Posts: 14
Joined: Sat Feb 02, 2013 3:18 pm
Location: Germany

IRC

Post by grahamperrin » Sun Jun 16, 2013 3:02 pm

Now where do I go?

To IRC. For a a chat with BjoKa and/or Lundman. See you there …
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Re: Now where do we go?

Post by lundman » Sun Jun 16, 2013 7:10 pm

I have tested osx.zfs with Maverick - it behaves as it should. There was a load time panic (vget) which I fixed last week, and SpotLight will hold a directory open so you can't unmount it. The latter I am working on now. (It is easy to deny SpotLight access though).
lundman Offline


 
Posts: 11
Joined: Sun Nov 25, 2012 9:54 pm

Parallels ZEVO success

Post by ilovezfs » Mon Jul 15, 2013 1:53 pm

Unlike VMware Fusion (as of version 5.0.3), Parallels Desktop 8.0.18494 has USB 3.0 support for OS X guest virtual machines. I tested ZEVO with a physical USB 3.0 drive passed directly through to the VM and it works. So that's at least one high-performance path forward for ZEVO as we transition to Mavericks.
ilovezfs Online


 
Posts: 249
Joined: Sun Feb 10, 2013 9:02 am

Re: Now where do we go?

Post by ylluminate » Thu Jul 18, 2013 12:42 pm

Yes Don is gone from GreenBytes and has been for some time.
ylluminate Offline


 
Posts: 18
Joined: Sat Oct 13, 2012 1:37 am

Re: Now where do we go?

Post by claunia » Fri Jul 19, 2013 8:11 pm

I can confirm as of Mac OS X 10.9 DP3, ZEVO is not working.
claunia Offline


 
Posts: 1
Joined: Mon Sep 17, 2012 10:01 pm

PreviousNext

Return to General Discussion

Who is online

Users browsing this forum: ilovezfs and 3 guests

cron