Open GoogleCodeExporter opened 9 years ago
Can you give some more details about your system configuration? Especially:
zpool status -v
zpool get all _to_be_shared_pool_
zfs get all _to_be_shared_pool_
Also which version of MacZFS are you using?
Re zfs upgrade:
It is supposed to be a safe operation, but I highly doubt it would help in your
situation. Bottom line: For now I would advise against it.
Original comment by googlelogin@bjoern-kahl.de
on 29 Nov 2013 at 10:24
Hey! Thanks for your quick reply.
1. How do I check my ZFS version? I didn't find anything straight forward in
the command list like "zfs version" :/
Here are the things you requested:
zpool status -v
pool: DeltaRaidPi
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
DeltaRaidPi ONLINE 0 0 0
raidz1 ONLINE 0 0 0
disk3s2 ONLINE 0 0 0
disk5s2 ONLINE 0 0 0
disk4s2 ONLINE 0 0 0
errors: No known data errors
zpool get all DeltaRaidPi
NAME PROPERTY VALUE SOURCE
DeltaRaidPi bootfs - default
DeltaRaidPi autoreplace off default
DeltaRaidPi delegation off default
zfs get all DeltaRaidPi
NAME PROPERTY VALUE SOURCE
DeltaRaidPi type filesystem -
DeltaRaidPi creation Do Nov 15 0:07 2012 -
DeltaRaidPi used 3,10T -
DeltaRaidPi available 485G -
DeltaRaidPi referenced 3,10T -
DeltaRaidPi compressratio 1.00x -
DeltaRaidPi mounted yes -
DeltaRaidPi quota none default
DeltaRaidPi reservation none default
DeltaRaidPi recordsize 128K default
DeltaRaidPi mountpoint /Volumes/DeltaRaidPi default
DeltaRaidPi sharenfs off default
DeltaRaidPi checksum on default
DeltaRaidPi compression off default
DeltaRaidPi atime on default
DeltaRaidPi devices on default
DeltaRaidPi exec on default
DeltaRaidPi setuid on default
DeltaRaidPi readonly off default
DeltaRaidPi zoned off default
DeltaRaidPi snapdir hidden default
DeltaRaidPi aclmode groupmask default
DeltaRaidPi aclinherit secure default
DeltaRaidPi canmount on default
DeltaRaidPi shareiscsi off default
DeltaRaidPi xattr on default
DeltaRaidPi copies 1 default
DeltaRaidPi version 2 -
Original comment by sabel.ka...@gmail.com
on 29 Nov 2013 at 10:35
Determining the version is (was) indeed not straight forward. Here are some
things to try:
check the output of "kextstat", look for "zfs". E.g. on terminal do "kextstat |
grep -e zfs"
above line works only when ZFS is active.
Another option is to look into the kext's plist file: Open terminal, then do
"less /System/Library/Extensions/zfs.kext/Contents/Info.plist" and look for the
key "CFBundleShortVersionString". This is actually the most valuable one,
since it contains the build id which allows to pinpoint the exact source code
revision used to build the module.
Different question:
How do you try to share the pool? What is SMBup and are you using the Samba
version that comes with MacOSX (Does Maverick still include Samba? I don't
know.) or a 3rd party install?
Original comment by googlelogin@bjoern-kahl.de
on 30 Nov 2013 at 10:51
So the version:
kextstat | grep -e zfs
131 0 0xffffff7f82223000 0x69000 0x69000 com.bandlem.mac.zfs.fs (74.2.0) <7 5 4 1>
And Samba. I think Mavericks still has Samba but there are issues with it. Not
sure if everybody has them but my goal is to share my Zfs zpool so that I can
access it on my TV via XBMC.
With the standard os x file sharing protocoll I could sometimes see the zpool,
sometimes not and even files that were stored on my internal harddrive
wouldn't open and time out after a few minutes.
I read online that this was a common bug for people with Mavericks and
downloaded SMBUp (http://eduo.info/apps/smbup) to replace the OS X SMB service.
The funny thing is that it already worked the way I wanted until I accidentally
deleted the SMB config file :s
With SMBup I can see my computer on the network, I can even see the folder on
the computer but I get an Access Denied when I try to actually open the folder.
And this doesn't happen with folders that are shared on my local harddrive.
Hope this is enough information to help me? :/
Original comment by sabel.ka...@gmail.com
on 30 Nov 2013 at 11:55
Anyone?
Original comment by sabel.ka...@gmail.com
on 5 Jan 2014 at 7:26
Original issue reported on code.google.com by
sabel.ka...@gmail.com
on 29 Nov 2013 at 9:44