WTFover

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by WTFover

  1. So I had to rebuild my docker environment this morning due to what appears to be a corrupt docker.img. I was able to use all my templates and quickly brought everything back, however SickChill seems to have lost the ability to write files in the media directory. I have done the chmod -R 777 in the target directory. I can touch files with both the root and nobody account in this directory but it still fails to add new shows with the following as an example: 2020-07-17 13:01:53 WEBSERVER-ADDSHOWS :: [cddc3c8] Unable to create the folder /mnt/MAG_Pool/TV-Shows/Lost Speedways, can't add the show Does anyone have any ideas?
  2. Hey all, has anyone had any success with exporting NFS shares from a ZFS pool? I'm new to unraid but have been using ZFS via Freenas for many years. What I am trying to do: Export a directory from a mirrored SSD Pool to some ESX hosts in my lab. Pool and dataset to be exported: SSD_Pool/VM_Datastore, mounted at /mnt/SSD_Pool/VM_Datastore Here is a list of the dataset paramaters: SSD_Pool/VM_Datastore type filesystem - SSD_Pool/VM_Datastore creation Tue Feb 18 18:21 2020 - SSD_Pool/VM_Datastore used 24K - SSD_Pool/VM_Datastore available 1.58T - SSD_Pool/VM_Datastore referenced 24K - SSD_Pool/VM_Datastore compressratio 1.00x - SSD_Pool/VM_Datastore mounted yes - SSD_Pool/VM_Datastore quota none default SSD_Pool/VM_Datastore reservation none default SSD_Pool/VM_Datastore recordsize 128K default SSD_Pool/VM_Datastore mountpoint /mnt/SSD_Pool/VM_Datastore inherited from SSD_Pool SSD_Pool/VM_Datastore sharenfs [email protected]/24 local SSD_Pool/VM_Datastore checksum on default SSD_Pool/VM_Datastore compression lz4 inherited from SSD_Pool SSD_Pool/VM_Datastore atime off inherited from SSD_Pool SSD_Pool/VM_Datastore devices on default SSD_Pool/VM_Datastore exec on default SSD_Pool/VM_Datastore setuid on default SSD_Pool/VM_Datastore readonly off default SSD_Pool/VM_Datastore zoned off default SSD_Pool/VM_Datastore snapdir hidden default SSD_Pool/VM_Datastore aclinherit restricted default SSD_Pool/VM_Datastore createtxg 125 - SSD_Pool/VM_Datastore canmount on default SSD_Pool/VM_Datastore xattr on default SSD_Pool/VM_Datastore copies 1 default SSD_Pool/VM_Datastore version 5 - SSD_Pool/VM_Datastore utf8only off - SSD_Pool/VM_Datastore normalization none - SSD_Pool/VM_Datastore casesensitivity sensitive - SSD_Pool/VM_Datastore vscan off default SSD_Pool/VM_Datastore nbmand off default SSD_Pool/VM_Datastore sharesmb off default SSD_Pool/VM_Datastore refquota none default SSD_Pool/VM_Datastore refreservation none default SSD_Pool/VM_Datastore guid 7038295691283632036 - SSD_Pool/VM_Datastore primarycache all default SSD_Pool/VM_Datastore secondarycache all default SSD_Pool/VM_Datastore usedbysnapshots 0B - SSD_Pool/VM_Datastore usedbydataset 24K - SSD_Pool/VM_Datastore usedbychildren 0B - SSD_Pool/VM_Datastore usedbyrefreservation 0B - SSD_Pool/VM_Datastore logbias latency default SSD_Pool/VM_Datastore objsetid 71 - SSD_Pool/VM_Datastore dedup off default SSD_Pool/VM_Datastore mlslabel none default SSD_Pool/VM_Datastore sync standard default SSD_Pool/VM_Datastore dnodesize legacy default SSD_Pool/VM_Datastore refcompressratio 1.00x - SSD_Pool/VM_Datastore written 24K - SSD_Pool/VM_Datastore logicalused 12K - SSD_Pool/VM_Datastore logicalreferenced 12K - SSD_Pool/VM_Datastore volmode default default SSD_Pool/VM_Datastore filesystem_limit none default SSD_Pool/VM_Datastore snapshot_limit none default SSD_Pool/VM_Datastore filesystem_count none default SSD_Pool/VM_Datastore snapshot_count none default SSD_Pool/VM_Datastore snapdev hidden default SSD_Pool/VM_Datastore acltype off default SSD_Pool/VM_Datastore context none default SSD_Pool/VM_Datastore fscontext none default SSD_Pool/VM_Datastore defcontext none default SSD_Pool/VM_Datastore rootcontext none default SSD_Pool/VM_Datastore relatime off default SSD_Pool/VM_Datastore redundant_metadata all default SSD_Pool/VM_Datastore overlay off default SSD_Pool/VM_Datastore encryption off default SSD_Pool/VM_Datastore keylocation none default SSD_Pool/VM_Datastore keyformat none default SSD_Pool/VM_Datastore pbkdf2iters 0 default SSD_Pool/VM_Datastore special_small_blocks 0 default If I watch the log, I see the following (192.168.1.16 is one of the hosts trying to mount the export): Feb 26 08:03:17 JC-NAS rpcbind[14617]: connect from 192.168.1.16 to getport/addr(mountd) Feb 26 08:03:17 JC-NAS rpc.mountd[16277]: authenticated mount request from 192.168.1.16:693 for /mnt/SSD_Pool/VM_Datastore (/mnt/SSD_Pool/VM_Datastore) Feb 26 08:03:17 JC-NAS rpc.mountd[16277]: Cannot export /mnt/SSD_Pool/VM_Datastore, possibly unsupported filesystem or fsid= required I've tried creating and re -exporting via /etc/exports with fsid=0 (and a couple of other things like 1, or the dataset GUID). Has anyone had any success with this?