Add Storage to Jail "Create directory" Not Working

[Christopher Joyson]

HI just upgraded to 9.2.1.6 hoping that it would fix all the problems I've been having getting plug insto work. Rather than solving my problem another one ha popped up!!

When I go to Jails>My Jail>Storage>Add Storage I add the source athen add the Destination (/mnt/Nas_Volume/Media/Movies) and append /Movies onto the end of /media in my source I get:

tis is the Shell footer info since the lasst boot.

Ive done exactly the same as I did with 9.2.1.5.

Code:

Jul 11 19:00:21 freenas syslogd: kernel boot file is /boot/kernel/kernel
Jul 11 19:00:21 freenas kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done
Jul 11 19:00:21 freenas kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Jul 11 19:00:21 freenas kernel:
Jul 11 19:00:21 freenas kernel: Waiting (max 60 seconds) for system process `syncer' to stop...Syncing disks, vnodes remaining...2 1 1 1 0 0 0 0 done
Jul 11 19:00:21 freenas kernel: All buffers synced.
Jul 11 19:00:21 freenas kernel: Copyright (c) 1992-2013 The FreeBSD Project.
Jul 11 19:00:21 freenas kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Jul 11 19:00:21 freenas kernel: The Regents of the University of California. All rights reserved.
Jul 11 19:00:21 freenas kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Jul 11 19:00:21 freenas kernel: FreeBSD 9.2-RELEASE-p9 #0 r262572+cc525fe: Thu Jul  3 14:22:45 PDT 2014
Jul 11 19:00:21 freenas kernel: root@build3.ixsystems.com:/fusion/jenkins/9.2.1.6-RELEASE/os-base/amd64/fusion/jenkins/9.2.1.6-RELEASE/FreeBSD/src/sys/FREENAS.amd64 amd64
Jul 11 19:00:21 freenas kernel: gcc version 4.2.1 20070831 patched [FreeBSD]
Jul 11 19:00:21 freenas kernel: CPU: Intel(R) Pentium(R) CPU G3240 @ 3.10GHz (3092.90-MHz K8-class CPU)
Jul 11 19:00:21 freenas kernel: Origin = "GenuineIntel"  Id = 0x306c3  Family = 0x6  Model = 0x3c  Stepping = 3
Jul 11 19:00:21 freenas kernel: Features=0xbfebfbff
Jul 11 19:00:21 freenas kernel: Features2=0x4ddaebbf,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND>
Jul 11 19:00:21 freenas kernel: AMD Features=0x2c100800
Jul 11 19:00:21 freenas kernel: AMD Features2=0x21
Jul 11 19:00:21 freenas kernel: Standard Extended Features=0x2603
Jul 11 19:00:21 freenas kernel: TSC: P-state invariant, performance statistics
Jul 11 19:00:21 freenas kernel: real memory  = 17179869184 (16384 MB)
Jul 11 19:00:21 freenas kernel: avail memory = 16397893632 (15638 MB)
Jul 11 19:00:21 freenas kernel: Event timer "LAPIC" quality 600
Jul 11 19:00:21 freenas kernel: ACPI APIC Table:
Jul 11 19:00:21 freenas kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
Jul 11 19:00:21 freenas kernel: FreeBSD/SMP: 1 package(s) x 2 core(s)
Jul 11 19:00:21 freenas kernel: cpu0 (BSP): APIC ID:  0
Jul 11 19:00:21 freenas kernel: cpu1 (AP): APIC ID:  2
Jul 11 19:00:21 freenas kernel: WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
Jul 11 19:00:21 freenas kernel: ACPI Warning: FADT (revision 5) is longer than ACPI 2.0 version, truncating length 268 to 244 (20110527/tbfadt-320)
Jul 11 19:00:21 freenas kernel: ioapic0  irqs 0-23 on motherboard
Jul 11 19:00:21 freenas kernel: kbd1 at kbdmux0
Jul 11 19:00:21 freenas kernel: cryptosoft0:  on motherboard
Jul 11 19:00:21 freenas kernel: aesni0: No AESNI support.
Jul 11 19:00:21 freenas kernel: padlock0: No ACE support.
Jul 11 19:00:21 freenas kernel: acpi0:  on motherboard
Jul 11 19:00:21 freenas kernel: ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND (20110527/psargs-392)
Jul 11 19:00:21 freenas kernel: ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20110527/nsinit-380)
Jul 11 19:00:21 freenas kernel: acpi0: Power Button (fixed)
Jul 11 19:00:21 freenas kernel: acpi0: reservation of 67, 1 (4) failed
Jul 11 19:00:21 freenas kernel: cpu0:  on acpi0
Jul 11 19:00:21 freenas kernel: cpu1:  on acpi0
Jul 11 19:00:21 freenas kernel: hpet0:  iomem 0xfed00000-0xfed003ff on acpi0
Jul 11 19:00:21 freenas kernel: Timecounter "HPET" frequency 14318180 Hz quality 950
Jul 11 19:00:21 freenas kernel: Event timer "HPET" frequency 14318180 Hz quality 550
Jul 11 19:00:21 freenas kernel: Event timer "HPET1" frequency 14318180 Hz quality 440
Jul 11 19:00:21 freenas kernel: Event timer "HPET2" frequency 14318180 Hz quality 440
Jul 11 19:00:21 freenas kernel: Event timer "HPET3" frequency 14318180 Hz quality 440
Jul 11 19:00:21 freenas kernel: Event timer "HPET4" frequency 14318180 Hz quality 440
Jul 11 19:00:21 freenas kernel: Event timer "HPET5" frequency 14318180 Hz quality 440
Jul 11 19:00:21 freenas kernel: Event timer "HPET6" frequency 14318180 Hz quality 440
Jul 11 19:00:21 freenas kernel: atrtc0:  port 0x70-0x77 irq 8 on acpi0
Jul 11 19:00:21 freenas kernel: atrtc0: Warning: Couldn't map I/O.
Jul 11 19:00:21 freenas kernel: Event timer "RTC" frequency 32768 Hz quality 0
Jul 11 19:00:21 freenas kernel: attimer0:  port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Jul 11 19:00:21 freenas kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Jul 11 19:00:21 freenas kernel: Event timer "i8254" frequency 1193182 Hz quality 100
Jul 11 19:00:21 freenas kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Jul 11 19:00:21 freenas kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
Jul 11 19:00:21 freenas kernel: pcib0:  port 0xcf8-0xcff on acpi0
Jul 11 19:00:21 freenas kernel: pci0:  on pcib0
Jul 11 19:00:21 freenas kernel: pcib1:  irq 16 at device 1.0 on pci0
Jul 11 19:00:21 freenas kernel: pci1:  on pcib1
Jul 11 19:00:21 freenas kernel: vgapci0:  port 0xf000-0xf03f mem 0xf7800000-0xf7bfffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
Jul 11 19:00:21 freenas kernel: pci0:  at device 3.0 (no driver attached)
Jul 11 19:00:21 freenas kernel: pci0:  at device 20.0 (no driver attached)
Jul 11 19:00:21 freenas kernel: pci0:  at device 22.0 (no driver attached)
Jul 11 19:00:21 freenas kernel: em0:  port 0xf080-0xf09f mem 0xf7c00000-0xf7c1ffff,0xf7c3d000-0xf7c3dfff irq 20 at device 25.0 on pci0
Jul 11 19:00:21 freenas kernel: em0: Using an MSI interrupt
Jul 11 19:00:21 freenas kernel: em0: Ethernet address: 40:16:7e:28:27:a8
Jul 11 19:00:21 freenas kernel: ehci0:  mem 0xf7c3c000-0xf7c3c3ff irq 16 at device 26.0 on pci0
Jul 11 19:00:21 freenas kernel: usbus0: EHCI version 1.0
Jul 11 19:00:21 freenas kernel: usbus0 on ehci0
Jul 11 19:00:21 freenas kernel: pci0:  at device 27.0 (no driver attached)
Jul 11 19:00:21 freenas kernel: ehci1:  mem 0xf7c3b000-0xf7c3b3ff irq 23 at device 29.0 on pci0
Jul 11 19:00:21 freenas kernel: usbus1: EHCI version 1.0
Jul 11 19:00:21 freenas kernel: usbus1 on ehci1
Jul 11 19:00:21 freenas kernel: isab0:  at device 31.0 on pci0
Jul 11 19:00:21 freenas kernel: isa0:  on isab0
Jul 11 19:00:21 freenas kernel: ahci0:  port 0xf0d0-0xf0d7,0xf0c0-0xf0c3,0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf060-0xf07f mem 0xf7c3a000-0xf7c3a7ff irq 19 at device 31.2 on pci0
Jul 11 19:00:21 freenas kernel: ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
Jul 11 19:00:21 freenas kernel: ahcich0:  at channel 0 on ahci0
Jul 11 19:00:21 freenas kernel: ahcich1:  at channel 1 on ahci0
Jul 11 19:00:21 freenas kernel: pci0:  at device 31.3 (no driver attached)
Jul 11 19:00:21 freenas kernel: acpi_button0:  on acpi0
Jul 11 19:00:21 freenas kernel: acpi_tz0:  on acpi0
Jul 11 19:00:21 freenas kernel: acpi_tz1:  on acpi0
Jul 11 19:00:21 freenas kernel: sc0:  at flags 0x100 on isa0
Jul 11 19:00:21 freenas kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Jul 11 19:00:21 freenas kernel: vga0:  at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Jul 11 19:00:21 freenas kernel: atkbdc0:  at port 0x60,0x64 on isa0
Jul 11 19:00:21 freenas kernel: atkbd0:  irq 1 on atkbdc0
Jul 11 19:00:21 freenas kernel: kbd0 at atkbd0
Jul 11 19:00:21 freenas kernel: atkbd0: [GIANT-LOCKED]
Jul 11 19:00:21 freenas kernel: wbwd0: DevID 0xc8 DevRev 0x03, will not attach, please report this.
Jul 11 19:00:21 freenas kernel: coretemp0:  on cpu0
Jul 11 19:00:21 freenas kernel: est0:  on cpu0
Jul 11 19:00:21 freenas kernel: p4tcc0:  on cpu0
Jul 11 19:00:21 freenas kernel: coretemp1:  on cpu1
Jul 11 19:00:21 freenas kernel: est1:  on cpu1
Jul 11 19:00:21 freenas kernel: p4tcc1:  on cpu1
Jul 11 19:00:21 freenas kernel: Timecounters tick every 1.000 msec
Jul 11 19:00:21 freenas kernel: ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
Jul 11 19:00:21 freenas kernel: DUMMYNET 0xfffffe000631bc00 with IPv6 initialized (100409)
Jul 11 19:00:21 freenas kernel: load_dn_sched dn_sched RR loaded
Jul 11 19:00:21 freenas kernel: load_dn_sched dn_sched WF2Q+ loaded
Jul 11 19:00:21 freenas kernel: load_dn_sched dn_sched FIFO loaded
Jul 11 19:00:21 freenas kernel: load_dn_sched dn_sched PRIO loaded
Jul 11 19:00:21 freenas kernel: load_dn_sched dn_sched QFQ loaded
Jul 11 19:00:21 freenas kernel: usbus0: 480Mbps High Speed USB v2.0
Jul 11 19:00:21 freenas kernel: usbus1: 480Mbps High Speed USB v2.0
Jul 11 19:00:21 freenas kernel: ugen0.1:  at usbus0
Jul 11 19:00:21 freenas kernel: uhub0:  on usbus0
Jul 11 19:00:21 freenas kernel: ugen1.1:  at usbus1
Jul 11 19:00:21 freenas kernel: uhub1:  on usbus1
Jul 11 19:00:21 freenas kernel: ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
Jul 11 19:00:21 freenas kernel: ada0:  ATA-9 SATA 3.x device
Jul 11 19:00:21 freenas kernel: ada0: Serial Number WD-WMC4M3273774
Jul 11 19:00:21 freenas kernel: ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Jul 11 19:00:21 freenas kernel: ada0: Command Queueing enabled
Jul 11 19:00:21 freenas kernel: ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Jul 11 19:00:21 freenas kernel: ada0: quirks=0x1<4K>
Jul 11 19:00:21 freenas kernel: ada0: Previously was known as ad4
Jul 11 19:00:21 freenas kernel: ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
Jul 11 19:00:21 freenas kernel: ada1:  ATA-9 SATA 3.x device
Jul 11 19:00:21 freenas kernel: ada1: Serial Number WD-WMC4N1163779
Jul 11 19:00:21 freenas kernel: ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Jul 11 19:00:21 freenas kernel: ada1: Command Queueing enabled
Jul 11 19:00:21 freenas kernel: ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Jul 11 19:00:21 freenas kernel: ada1: quirks=0x1<4K>
Jul 11 19:00:21 freenas kernel: ada1: Previously was known as ad6
Jul 11 19:00:21 freenas kernel: SMP: AP CPU #1 Launched!
Jul 11 19:00:21 freenas kernel: Timecounter "TSC-low" frequency 1546451890 Hz quality 1000
Jul 11 19:00:21 freenas kernel: uhub0: 2 ports with 2 removable, self powered
Jul 11 19:00:21 freenas kernel: uhub1: 2 ports with 2 removable, self powered
Jul 11 19:00:21 freenas kernel: Root mount waiting for: usbus1 usbus0
Jul 11 19:00:21 freenas kernel: ugen0.2:  at usbus0
Jul 11 19:00:21 freenas kernel: uhub2:  on usbus0
Jul 11 19:00:21 freenas kernel: ugen1.2:  at usbus1
Jul 11 19:00:21 freenas kernel: uhub3:  on usbus1
Jul 11 19:00:21 freenas kernel: Root mount waiting for: usbus1 usbus0
Jul 11 19:00:21 freenas kernel: uhub2: 6 ports with 6 removable, self powered
Jul 11 19:00:21 freenas kernel: uhub3: 8 ports with 8 removable, self powered
Jul 11 19:00:21 freenas kernel: Root mount waiting for: usbus0
Jul 11 19:00:21 freenas kernel: ugen0.3:  at usbus0
Jul 11 19:00:21 freenas kernel: umass0:  on usbus0
Jul 11 19:00:21 freenas kernel: umass0:  SCSI over Bulk-Only; quirks = 0x0100
Jul 11 19:00:21 freenas kernel: umass0:3:0:-1: Attached to scbus3
Jul 11 19:00:21 freenas kernel: Trying to mount root from ufs:/dev/ufs/FreeNASs1a [ro]...
Jul 11 19:00:21 freenas kernel: mountroot: waiting for device /dev/ufs/FreeNASs1a ...
Jul 11 19:00:21 freenas kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
Jul 11 19:00:21 freenas kernel: da0:  Removable Direct Access SCSI-6 device
Jul 11 19:00:21 freenas kernel: da0: Serial Number 4C530006020406111223
Jul 11 19:00:21 freenas kernel: da0: 40.000MB/s transfers
Jul 11 19:00:21 freenas kernel: da0: 7633MB (15633408 512 byte sectors: 255H 63S/T 973C)
Jul 11 19:00:21 freenas kernel: da0: quirks=0x2
Jul 11 19:00:21 freenas kernel: GEOM_RAID5: Module loaded, version 1.1.20130907.44 (rev 5c6d2a159411)
Jul 11 19:00:21 freenas kernel: ZFS filesystem version: 5
Jul 11 19:00:21 freenas kernel: ZFS storage pool version: features support (5000)
Jul 11 19:00:21 freenas kernel: GEOM_ELI: Device ada0p1.eli created.
Jul 11 19:00:21 freenas kernel: GEOM_ELI: Encryption: AES-XTS 256
Jul 11 19:00:21 freenas kernel: GEOM_ELI:     Crypto: software
Jul 11 19:00:21 freenas kernel: GEOM_ELI: Device ada1p1.eli created.
Jul 11 19:00:21 freenas kernel: GEOM_ELI: Encryption: AES-XTS 256
Jul 11 19:00:21 freenas kernel: GEOM_ELI:     Crypto: software
Jul 11 19:00:21 freenas root: /etc/rc: WARNING: failed to start watchdogd
Jul 11 19:00:21 freenas root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Jul 11 19:00:21 freenas kernel: vboxdrv: fAsync=0 offMin=0x366 offMax=0xafa
Jul 11 19:00:21 freenas ntpd[1924]: ntpd 4.2.4p5-a (1)
Jul 11 19:00:21 freenas kernel: .
Jul 11 19:00:22 freenas kernel: .......................................+++
Jul 11 19:00:22 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Jul 11 19:00:22 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint,name
Jul 11 19:00:22 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint
Jul 11 19:00:22 freenas last message repeated 3 times
Jul 11 19:00:22 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpyFkz60 -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Jul 11 19:00:23 freenas nmbd[2187]: [2014/07/11 19:00:23.311089,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Jul 11 19:00:23 freenas winbindd[2193]: [2014/07/11 19:00:23.619435,  0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Jul 11 19:00:23 freenas winbindd[2193]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Jul 11 19:00:23 freenas winbindd[2193]: [2014/07/11 19:00:23.671756,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Jul 11 19:00:23 freenas smbd[2190]: [2014/07/11 19:00:23.773049,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Jul 11 19:00:23 freenas smbd[2190]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Jul 11 19:00:24 freenas smbd[2190]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Jul 11 19:00:25 freenas smbd[2190]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Jul 11 19:00:26 freenas smbd[2190]: dnssd_clientstub ConnectToServer: connect() failed Socket:32 Err:-1 Errno:2 No such file or directory
Jul 11 19:00:28 freenas kernel: done.
Jul 11 19:00:29 freenas kernel: bridge0: Ethernet address: 02:9b:ef:f7:10:00
Jul 11 19:00:29 freenas kernel: bridge0: link state changed to UP
Jul 11 19:00:29 freenas kernel: epair0a: Ethernet address: 02:b1:b7:00:07:0a
Jul 11 19:00:29 freenas kernel: epair0b: Ethernet address: 02:b1:b7:00:08:0b
Jul 11 19:00:29 freenas kernel: epair0a: link state changed to UP
Jul 11 19:00:29 freenas kernel: epair0b: link state changed to UP
Jul 11 19:00:29 freenas kernel: em0: link state changed to DOWN
Jul 11 19:00:29 freenas kernel: epair0a: promiscuous mode enabled
Jul 11 19:00:29 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Jul 11 19:00:32 freenas kernel: em0: link state changed to UP
Jul 11 19:00:31 freenas ntpd[1925]: time reset -1.345777 s
Jul 11 19:10:59 freenas manage.py: [middleware.exceptions:38] [MiddlewareError: The path could not be mounted /mnt/Nas_Volume/Media/Downloads: Mount failed (64) -> mount: /mnt/Nas_Volume/Programs/Plug-ins/media/mov: No such file or directory ]

 

[danb35]

https://bugs.freenas.org/issues/5349 It looks like they're planning to fix this in 9.3.

 

[Christopher Joyson]

Glad Someones listening.

 

[Yatti420]

I can confirm this is a bug in 9.2.1.6.

Sent from my SGH-I257M using Tapatalk 2

 

[Nick Howard]

Yup I'm getting the same thing happening. I notice in the bug report it is logged as being resolved? is this still been looked into? and if so do we have any idea when there could be a fix?

Thanks.

 

[cyberjock]

Yup I'm getting the same thing happening. I notice in the bug report it is logged as being resolved? is this still been looked into? and if so do we have any idea when there could be a fix?

Thanks.

Uh, it's resolved. And danb35 explained it above...

 

[Nick Howard]

So when will 9.3 be officially released? I've seen that there is the nightly beta releases but I'm not exactly confident enough to roll it out on my box. Am I right in thinking that when it's listed as being 'resolved' it means that is for the next release or does the current download get updated too? I ask because I only downloaded 6.2.1.6 four days ago, which is a week or so after it was supposedly resolved.

 

[Ericloewe]

So when will 9.3 be officially released? I've seen that there is the nightly beta releases but I'm not exactly confident enough to roll it out on my box. Am I right in thinking that when it's listed as being 'resolved' it means that is for the next release or does the current download get updated too? I ask because I only downloaded 6.2.1.6 four days ago, which is a week or so after it was supposedly resolved.

9.3 is at least six months away. The release notes for 9.2.1.6 RELEASE should mention the bug if it was fixed, though.

 

[Nick Howard]

9.3 is at least six months away. The release notes for 9.2.1.6 RELEASE should mention the bug if it was fixed, though.

No mention of it in the release notes and I can confirm it definitely isn't fixed. The link Dan provides above for bug 5349 has it as being resolved however?

 

[Christopher Joyson]

Uh, it's resolved. And danb35 explained it above...

So Cyberkock If its resolved what Version is it resolved in??

It certainly isn't resolved in 9.2.1.6

https://bugs.freenas.org/issues/5349 It looks like they're planning to fix this in 9.3.

contradicts what you said So is it just resolved for the update to Freenas 9.3 whch is six months away..or is there a specific Nightly build that has the fix?

To get away from bug this I reverted back to 9.2.1.5.

 

[Nick Howard]

So Cyberkock If its resolved what Version is it resolved in??

It certainly isn't resolved in 9.2.1.6



contradicts what you said So is it just resolved for the update to Freenas 9.3 whch is six months away..or is there a specific Nightly build that has the fix?

To get away from bug this I reverted back to 9.2.1.5.

It's confusing me too, bug 5349 is not listed in the release notes for 9.2.1.6. Yet when you click the link for bug 5349 it's been marked as resolved. There probably just been a mix up here, I'm guessing it could have been overlooked. I certainly can't wait 6 months for 9.3 if that is indeed the case, I'll be joining you back at 9.2.1.5.

 

[cyberjock]

It's fixed in the 9.3-beta... just like the ticket says. The 9.3 beta is available either by compiling it yourself or grabbing a nightly when/if iX posts one.

 

[Christopher Joyson]

So there's not going to be a Release with the fix then? if thats the case its only fixed for Beta testers then, I'll stick with my, finally, running 9.2.1.5 till I see that theres no furhter problems. It took two months worth of Trial and error to get the Jails to work at that.

 

[cyberjock]

Yeah... if only you could create the directory first.. then this wouldn't be a problem at all....

If only...

 

[Christopher Joyson]

Thats what I eventiuall did in 9.2.1.6 I shared my Dataset that woheld the Jails then Created the Directories and then The jail storage accepted it. but then I came accross another problem in that the permissions within the jail could not be changed. as mentioned in one of my other posts. that is why I went back to 9.2.1.5

Code:

12 10:33:51 freenas notifier: chmod: /mnt/Nas_Volume/Plug-In_Progs/.warden-template-pluginjail/usr/bin/ypchfn: Operation not permitted
Jul 12 10:33:51 freenas notifier: chmod: /mnt/Nas_Volume/Plug-In_Progs/.warden-template-pluginjail/usr/bin/chfn: Operation not permitted
Jul 12 10:33:51 freenas notifier: chmod: /mnt/Nas_Volume/Plug-In_Progs/.warden-template-pluginjail/usr/bin/passwd: Operation not permitted
Jul 12 10:33:51 freenas notifier: chmod: /mnt/Nas_Volume/Plug-In_Progs/.warden-template-pluginjail/usr/lib/librt.so.1: Operation not permitted

 

[cyberjock]

I can tell you exactly what caused that error. 9.2.1.6 uses the zfs property aclmode=restricted which prevents permissions changes with chmod/chroot/etc. if the requested changes cannot be properly exercised with ACLs. So my guess is that your jail's permissions are already fubared and you need to fix that to make 9.2.1.6 work properly. Keep in mind that aclmode=restricted is going to be the new default, and if I am right this also means that all future FreeNAS versions will not work as this new default prevents people from doing things that don't make sense with chmod.

I bet if you do a getfacl of one of those files you'll find permissions above and beyond what unix permissions are. ;) Care to post the output of one of them?

 

[Christopher Joyson]

I don't think that I will still be able to do that now I've downgraded back to 9.2.1.5 and used a different USB stick. Everythings running now.

I had started from scratch with the 9.2.1.6 install apart from auto-importing the actual Volumes, but these did not have any jails in them as always I delete then prior to a re-install.

 

[cyberjock]

Eh too bad.

I will say this though. If you have some permissions that is being inherited to the jails dataset that could still explain your condition. Of course, there's no way to know either way if this was the cause or not without actually testing and validating. ;)

 

[danb35]

So there's not going to be a Release with the fix then?

Yes, there's going to be a release--it's going to be fixed in 9.3. I'm not sure why this is (apparently) so difficult to understand.

I guess it's up to you how serious this is, but IMO it's hardly a show-stopper--just make the target directory in the jail before you set up the storage. That's all you have to do.

 

[Nick Howard]

Yes, there's going to be a release--it's going to be fixed in 9.3. I'm not sure why this is (apparently) so difficult to understand.

I guess it's up to you how serious this is, but IMO it's hardly a show-stopper--just make the target directory in the jail before you set up the storage. That's all you have to do.

I tried that and although I could mount the directories and Plex would see them when it came to actually adding a library in Plex it still wouldn't pull the files across. I've since found a fix however.

Before I was mounting my storage to say:

media/tvshows
media/movies

I've found that it works if I just mount the storage to a directory without creating a sub directory as I was doing above. So currently I have movies mounted to just /media and tv shows to just /tmp. I've also found things start to go wrong if you start messing with permissions for the jails.