__group__,ticket,summary,component,version,milestone,type,owner,status,created,_changetime,_description,_reporter Active Tickets,2117,"Adding a cron, rsync or replication job\task causes traceback error",Backend,,9.1.0-RELEASE,defect,william,accepted,2013-04-09T05:24:46Z,2013-05-12T05:05:35Z,"Hi guys, I'm running the 4-02-13 alpha (FreeNAS-9.1.0-ALPHA-c86e8f4-x64) and whenever I try to add a cron, rsync or replication task\job I get a traceback message. All 3 ""add"" attempts seem to point to the same ""line 347"". Here is the brief form of the error: Exception Type: NameError Exception Value: global name 'group' is not defined Exception Location: /usr/local/www/freenasUI/../freenasUI/common/freenasusers.py in __new__, line 347 I can certainly post the full text of the traceback error if the above isn't enough to isolate & correct the issue. -Will",survive Active Tickets,493,Hotswapping SATA disk in RAIDZ fails,FreeBSD,8.0.1-BETA3,,defect,,new,2011-07-02T17:47:14Z,2012-12-30T02:48:09Z,"Hello, I built a dedicated FreeNAS 8.0.1-BETA3-amd64 box with three 2TB SATA-III hard drives and ZFS RAIDZ volume on top. Before I dare copying the data from my current fileserver to it I wanted to do a stresstest: I unplugged the third of the three drives to simulate a drive failure. Expected outcome: 1. Test data on RAIDZ volume still accessible and correct. 2. Receive e-mail notification from NAS on failure. 3. After replugging the drive the RAIDZ volume is either automatically or manually repaired. 4. GUI shows state of volume (degraded / functional). Please correct me if my expectations are not in accordance with what FreeNAS is intended to do. Observed outcome: 1. Test data on RAIDZ volume still accessible and correct. 2. No e-mail notification received. (e-mail in general works) 3. Unable to automatically or manually repair the volume. 4. No clues in the GUI what is going on. ad 3.: after unplugging the drive, I get the message {{{ nas kernel: (ada2:ahcich2:0:0:0): lost device }}} The GUI (Storage | volume1 | View Disk) still shows three entries but only ada0 and ada1 are named whereas the name of the third disk (previously ada2) is blank. I then replug the drive and use the GUI (Storage | volume1 | View Disk | Replace) to replace the disk. I receive the following python traceback: {{{ #!python Environment: Request Method: GET Request URL: https://nas/storage/volume/1/disk-replacement/3/ Django Version: 1.3 Python Version: 2.7.1 Installed Applications: ['django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.staticfiles', 'freeadmin', 'south', 'dojango', 'account', 'system', 'network', 'storage', 'sharing', 'services'] Installed Middleware: ('django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'freenasUI.freeadmin.middleware.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'freenasUI.freeadmin.middleware.RequireLoginMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'dojango.middleware.DojoCollector') Traceback: File ""/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py"" in get_response 105. response = middleware_method(request, callback, callback_args, callback_kwargs) File ""/usr/local/www/freenasUI/freeadmin/middleware.py"" in process_view 49. return login_required(view_func)(request,*view_args,**view_kwargs) File ""/usr/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py"" in _wrapped_view 23. return view_func(request, *args, **kwargs) File ""/usr/local/www/freenasUI/storage/views.py"" in disk_replacement 527. form = forms.DiskReplacementForm(disk=fromdisk) File ""/usr/local/www/freenasUI/storage/forms.py"" in __init__ 935. self.fields['volume_disks'].choices = self._populate_disk_choices() File ""/usr/local/www/freenasUI/storage/forms.py"" in _populate_disk_choices 945. disks = notifier().get_disks() File ""/usr/local/www/freenasUI/middleware/notifier.py"" in get_disks 1223. 'capacity': info[2] Exception Type: IndexError at /storage/volume/1/disk-replacement/3/ Exception Value: list index out of range }}} Using the command line it seems that /dev/ada2 does not come back. In other words, the operating system did not recognize the hotplugging the third disk. After a reboot, everything is fine again.",neubert Active Tickets,1011,"Failed CD upgrade hoses system, requiring complete reinstall",Backend,8.0.2-RELEASE,,defect,,assigned,2011-11-15T06:37:51Z,2012-04-14T00:58:19Z,"Recovering from a failed CD-based upgrade isn't possible today because the upgrade overwrites the entire disk instead of just the inactive partition when upgrading the install. So when it tries to reboot into the old image, boot(8) gets lost. The pc-sysinstall config needs to be modified to use the 'a' partition on the inactive partition instead of just wiping out the entire disk. Procedure: 1. Install a proper image. 2. Crack open the image. 3. Insert a syntax error into manage.py . 4. Repack the image. 5. Upgrade using the bogus image. Expected result: - The migration should fail. The active bit for the partition should be switched over to the valid partition. Actual result: - The migration fails. The active bit is set to the other partition, but the other partition is blank and thus FreeBSD gets lost.",gcooper Active Tickets,1160,smbd process in state zilog,Backend,8.2.0-RELEASE,,defect,,new,2012-01-10T09:13:32Z,2012-09-18T01:31:42Z,"hi, This ticket is a continuation of http://forums.freenas.org/showthread.php?4945-samba-process-spawn-runaway I saw that samba had been updated in the 8.0.3 release (FreeNAS-8.0.3-RELEASE-x64 (9395)) so i updated my server to that version. Unfortunately my problem with smbd processes remain. After a night of backups I have about 1000 smbd processes reported. I did however notice that all the smbd processes were in state 'zilog' when i did a ps in the terminal. {{{ 20239 root 1 47 0 49972K 10664K zilog- 1 0:00 0.00% smbd 18914 root 1 49 0 49580K 10488K zilog- 1 0:00 0.00% smbd 19981 root 1 49 0 49972K 10656K zilog- 1 0:00 0.00% smbd 20315 root 1 48 0 50104K 10816K zilog- 1 0:00 0.00% smbd 19956 root 1 48 0 49972K 10780K zilog- 1 0:00 0.00% smbd 19803 root 1 48 0 49972K 10648K zilog- 1 0:00 0.00% smbd 20062 root 1 49 0 49972K 10656K zilog- 1 0:00 0.00% smbd 19905 root 1 49 0 49972K 10692K zilog- 1 0:00 0.00% smbd 19739 root 1 48 0 49972K 10660K zilog- 1 0:00 0.00% smbd }}} and so on.. which makes me think that this might be more of a zfs problem than an smbd problem? Or perhaps the combination of writing large files (30-60 GB) to the nas, stressing both samba and zfs. Am I the only one experiencing this problem? It is very reproducible since it happens every night my backups run. ",fransm Active Tickets,1850,Realtek 8111F fails at high traffic 're0 Watchdog Timeout Error',FreeBSD,8.3.1-RELEASE-p1,,defect,,new,2012-10-21T14:10:56Z,2013-05-14T08:09:11Z,"When using a ASUS C60M1-I motherboard with a Realtek 8111F interface and copy alot of data via NFS, I looses connection after +/-20 minutes. The console prints: {{{ ""re0 Watchdog Timeout Error"" }}} When I start a shell from the console, I can't ping anything except my loopback interface. Before the permanent timeout occurs, it looses connection for a short time but continues after 4 seconds. When this happens, a 're0: watchdog timeout' is also printed to the console. At the short and permanent timeout, messages show this: /var/log/messages {{{ Oct 21 15:39:37 stor kernel: re0: watchdog timeout Oct 21 15:39:37 stor kernel: re0: link state changed to DOWN Oct 21 15:39:41 stor kernel: re0: link state changed to UP Oct 21 15:43:37 stor kernel: re0: watchdog timeout Oct 21 15:43:37 stor kernel: re0: link state changed to DOWN Oct 21 15:43:41 stor kernel: re0: link state changed to UP Oct 21 15:43:46 stor kernel: re0: watchdog timeout Oct 21 15:43:46 stor kernel: re0: link state changed to DOWN Oct 21 15:43:50 stor kernel: re0: link state changed to UP Oct 21 15:45:07 stor kernel: re0: watchdog timeout Oct 21 15:45:07 stor kernel: re0: link state changed to DOWN Oct 21 15:45:11 stor kernel: re0: link state changed to UP }}} This is what happens with the connection a few times before it becomes permanently lost: {{{ 64 bytes from 192.168.1.2: icmp_req=1536 ttl=64 time=0.118 ms 64 bytes from 192.168.1.2: icmp_req=1537 ttl=64 time=7998 ms 64 bytes from 192.168.1.2: icmp_req=1538 ttl=64 time=6989 ms 64 bytes from 192.168.1.2: icmp_req=1539 ttl=64 time=5989 ms 64 bytes from 192.168.1.2: icmp_req=1540 ttl=64 time=4989 ms 64 bytes from 192.168.1.2: icmp_req=1544 ttl=64 time=989 ms 64 bytes from 192.168.1.2: icmp_req=1545 ttl=64 time=0.249 ms }}} Eventually it looses connection {{{ 64 bytes from 192.168.1.2: icmp_req=2144 ttl=64 time=0.121 ms From 192.168.1.92 icmp_seq=2235 Destination Host Unreachable }}} ifconfig re0 down, ifconfig re0 up has no effect. tcpdump capture 0 packets on re0 after it looses connection. When I reboot, the connection is restored. I have ""Enable autotune"" off in my configuration and have not added any ""Tuneables"". I have recreated this 4 times.",owling Active Tickets,1876,"some WebGUI crash when adding multipath FC and can't see ""view multipath"" menu",GUI,8.2.0-RELEASE-p1,,defect,,new,2012-10-29T07:47:22Z,2013-04-18T08:49:49Z," I'm using FreeNAS-8.2.0-RELEASE-p1-x64 (r11950), connected to a FUJITSU ENTERNUS 4000 via 1 fiber channel qlogic cards (multipath).It was a single LUN, 10GB. It's a fresh installation of freenas, not an upgrade. Witch the command ""camcontrol rescan all"",I see two san disks:da0 and da1. And I create a multipath disk ""fujitsu01"": gmultipath label -v fujitsu01 /dev/da0 /dev/da1 And all succeed,i can use this volume. But when I choose ""View Disks"" i get the error ""Sorry, an error occured"" And I can't find the ""View Multipaths"" menu.",wuyisheng Active Tickets,2123,Can't rsync to my own NAS,Backend,8.3.1-RELEASE-p1,,defect,,new,2013-04-11T11:06:05Z,2013-04-11T11:06:05Z,"My NAS can rsync to FreeNAS,but when rsync to my NAS,will always shows ""password mismatch"", and I check the /usr/local/etc/ and there is no ""rsyncd.secrets"" file, I add the file manually and change the rsyncd.conf, it still go ""password mismatch""",cray Active Tickets,698,Need GUI to monitor AD cache,GUI,8.0.1-RC1,,enhancement,,new,2011-08-31T22:51:08Z,2011-09-29T21:22:20Z,"The Active Directory cache FreeNAS maintains lacks a status and monitoring GUI so users can ascertain its status. There is a reset button, but this is insufficient to debug all issues. Large domains could take seconds to minutes to build the cache. The only diagnostic currently available is that if the cache is still populating or is broken the user/group dialogs will not populate. Things that should be displayed in the monitoring panel: * Current cache state (missing, initializing, synchronizing, synchronized, stale, damaged) * Last synchronization date/time * Last synchronization result (success, failure) * If failure, a detailed diagnostic for the failure cause (cannot reach domain controller, invalid computer account, time desynchronization, etc.) * Total # of entries processed (if delta to last sync operation) * Total # of entries in cache (to compare if all appropriate accounts were transferred) ",dwhite Active Tickets,1403,Active Directory admin password is stored in the config database,Backend,8.0.4-RC1,8.2.0-RELEASE,defect,,new,2012-03-15T16:28:58Z,2013-01-04T20:02:03Z,"After joining an Active Directory (AD) domain, the admin password entered in the web gui form is stored in the config database (/data/freenas-v1.db) in plaintext. {{{ [root@zbox0] ~# /usr/local/bin/sqlite3 /data/freenas-v1.db SQLite version 3.7.7.1 2011-06-28 17:39:05 Enter "".help"" for instructions Enter SQL statements terminated with a "";"" sqlite> select ad_domainname, ad_adminpw from services_activedirectory; domain.com|DOMAIN_ADMIN_PASSWORD sqlite> }}} This could lead to a major security incident: An attacker successfully compromising the local root account of FreeNAS will also gain admin access to the AD, using the stored password. Additionally, in deployments where AD is centrally and FreeNAS locally administered, it means that in order to enable AD authentication on FreeNAS the AD administrator will have to yield the AD admin password to all FreeNAS administrators. This would be simply unacceptable in most cases. This problem can be fixed by serializing and storing the host credential files (secrets.tdb et al) in the database. This way the AD administrator password won't have to be stored. Note: The serialization (base64 encoding) and storing of files in the database has already been implemented by ssh for making /etc/ssh/ssh_host_* files pesistent. It can be found in /etc/rc.d/sshd. ",m000 Active Tickets,321,Freenas 8.0 Release not booting on USB stick after install on Dell Server,Build System,8.2.0-BETA4,,defect,,reopened,2011-05-05T09:33:11Z,2013-03-14T18:55:23Z,"Hi, I successfully installed FreeNAS 8.0 on an USB stick. When rebooted the server, it displayed boot menu : F1 FreeBSD F2 FreeBSD F5 Drive0 F6 PXE and restart without booting anything. I tried F2 or F5 and it displayed ############ continuously without booting. I googled and saw some people with similar problem on different Dell server with FreeNAS 8 RC5.",quick691fr Active Tickets,384,freenas 8.0.1 remote replication volume size,Backend,8.0.1-BETA1,,defect,,new,2011-06-02T19:37:19Z,2011-08-25T00:06:49Z,"was thining about sending data back and forth and thought about what if the remote system volume is too small for the transfer... cause you would end up w/ a data end stream in zfs send :). pool full not sure if it would say anything about it being full.",dw5304 Active Tickets,424,Intermittant network transfer pattern with ~5GB files from PC to FreeNAS 8.0.1-Beta 2,Backend,8.0.1-BETA1,,defect,,new,2011-06-12T17:35:49Z,2012-04-04T12:50:47Z,"Images posted: http://forums.freenas.org/showthread.php?362-quot-Bumpy-quot-Network-transfer-Large-files-from-Win7-to-FreeNAS-8.0.1-Beta2&p=1385#post1385 I had noticed that video playback from FreeNAS to PC was having periodic pauses. I upgraded to a gigabit NIC and tested a transfer from PC to FreeNAS. Average data transfer was about 26 MB/sec but the image shows a pulsatile pattern, with a large wave followed by 3 small waves. There was a similar pulsatile pattern when I transferred from my Promise SmartStor NS4300, although the maximum data transfer rate was slower. I had originally thought it might have been the Promise box or the 100 MB/s NIC but now I suspect my FreeNaS box. MyNAS hardware appears adequate: Hitachi 2TB ""slow"" drives in ZFS/Z2 configuration 4 onboard SATA2 2 PCI SATA2 cards PCI-express Gigabit NIC 4GB DDR2 ram Dual core processor 64 bit build",esamett Active Tickets,515,Replication requires CLI action to configure & monitor,GUI,8.0.1-BETA3,,defect,delphij,accepted,2011-07-12T01:54:42Z,2012-04-05T03:14:23Z,"The replication feature requires actions in the CLI to monitor & configure and this should not be necessary. In addition there are some missing features & configuration fields. Permission given to split this ticket into defects & enhancements accordingly. * The replication authentication public key should be visible from the GUI so it can be copied to and installed in the replicants. * The GUI should have a function to install public keys for the purposes of receiving replication streams (for situations where FreeNAS is serving as a replicant). * The /etc/ssh/ssh_known_hosts file is generated with the improper format, rendering it non-functional. Users must still open a root shell, make root writable, then run 'ssh -i /data/ssh/replication replicant' in order to capture the replicant's host key. * The ssh_known_hosts file seems to contain all host keys ever configured, even if not an active replicant, which is a security vulnerability (or would be if it worked). Compromised host keys cannot be deleted/revoked from the GUI and thus MITM attacks are possible. * There should be a way to test that the master can communicate successfully with the replicant(s). This test should also verify if the replicant can receive ZFS snapshot streams from the master (i.e., check the stream version). * The GUI should allow the user to configure what user to log in as on the replicant instead of only using 'root'. * The GUI should display the last successfully replicated snapshot for each configured replication stream, including the date/time. There is a column for this in the view that is not currently populated. * Replication configurations should have an !Enable/Disable checkbox so replication can be stopped without deconfiguring it (i.e. for replicant maintenance). * FreeNAS remembers the last snapshot replicated on a particular mountpoint/dataset across replication config deletion, even if the replicant is wiped of all snapshots, which is a POLA violation. FreeNAS should implement either behave consistently on replication creation (i.e., only replicate the latest snap) or provide the user with options as to handle initial replication.",dwhite Active Tickets,560,ZFS Replication - Restore from snapshot,Backend,8.0.1-BETA4,,defect,,new,2011-07-28T08:10:36Z,2012-04-05T05:00:36Z,"When restoring from active ZFS replication you can't delete the current snapshot to rollback to a previous. The message displayed is ""Held by replication system"" I'm not sure if you are required to break the replication task for to roll back. Current settings for replication Recursive: true Lifetime: 2 weeks Times: 7AM - 9PM Mon - Sat ZFS - Replication Recursively remove stale snapshots: true",daxroc Active Tickets,611,Verify the sanity of ownership/perms at service start,Backend,8.0.1-BETA4,,defect,,assigned,2011-08-15T21:59:39Z,2012-04-14T00:58:04Z,"if you change ownership of a(n afp) share directory (lets say /mnt/Tank/foo) to something other than root:wheel, you'll get errors... even if the directory permissions are 777. No specific error indicates this to be the problem. I don't think it's unreasonable to expect the share to be owned by root:wheel, but services which expect this should verify the ownership is as it's expected at service startup... If perms/ownership is incorrect, an error can be raised at that point informing the user of their issue, or at least a warning that this configuration is out of standard and issues can arise..",loiosh Active Tickets,786,"Smartd can not cope with SSD's that will not report temperature, fix included",Backend,8.0.1-RC1,,defect,,new,2011-09-15T23:41:33Z,2011-10-25T21:15:55Z,"{{{ Sep 15 16:39:35 freenas smartd[7740]: Device: /dev/da18 [SAT], can't monitor Temperature, ignoring -W Directive Sep 15 16:39:35 freenas smartd[7740]: Unable to register ATA device /dev/da18 [SAT] at line 19 of file /usr/local/etc/smartd.conf Sep 15 16:39:35 freenas smartd[7740]: Unable to register device /dev/da18 [SAT] (no Directive -d removable). Exiting. Sep 15 16:39:35 freenas root: /usr/local/etc/rc.d/smartd: WARNING: failed to start smartd Sep 15 16:39:35 freenas freenas: /usr/local/etc/rc.d/smartd: WARNING: failed to start smartd }}} ",nabbebx Active Tickets,793,GUI fails to wipe disks prior to creation of UFS volume,GUI,8.0.1-RC1,,defect,,new,2011-09-17T19:19:43Z,2011-09-17T19:19:43Z,"I am posting this on behalf of a forum user. This post is the reference: [http://forums.freenas.org/showthread.php?2270-Hard-Disk-Not-Visible&p=9720&viewfull=1#post9720] User tries to create UFS volume and fails with errors while trying to do 'dd' to wipe the disk. Freenas freenas[1719]: Executing: dd if=/dev/zero of=/dev/ada2 bs=1m count=1 Sep 15 01:50:15 Freenas freenas: dd: /dev/ada2: Operation not permitted Sep 15 01:50:15 Freenas freenas[1719]: Executing: dd if=/dev/zero of=/dev/ada2 bs=1m oseek=`diskinfo ada2 | awk '{print int($3 / (1024*1024)) - 4;}'` Sep 15 01:50:15 Freenas freenas: dd: /dev/ada2: Operation not permitted",protosd Active Tickets,820,problem with network interface with freenas 8.0.1rc2,FreeBSD,8.0.4-RELEASE,,defect,,reopened,2011-09-24T05:45:00Z,2012-03-30T02:50:24Z,"I have installed freenas 8.0.1rc2 on intel atom d410pt board with network a Realtek RTL8103E chipset (100mbps). freenas recognized the interface but dhcp doesnt work not does manually setting the ip. for dhcp i see in router log that dchpoffer is sent but freenas doesnt discover that and times out saying no dhcpoffers received and with manually setting the ip ifconfig shows status as active but i cant ping any of the nodes in the same subnet",nirvanaguy19 Active Tickets,823,"Active Volumes shows ""Size"" as available space, not actual Volume Size",GUI,8.0.1-RC2,,defect,,new,2011-09-24T15:32:19Z,2011-09-24T15:32:19Z,"It should probably either show, in order of preference: 1) The quota size, if set... 2) The size of the zpool the dataset is part of. Or, change the columns to reflect the fact that zfs list can only show the existing available space, not the total space of the dataset. ",kuruption Active Tickets,859,iSCSI authentication needs prepriming with certain initiators,Backend,8.0.1-RELEASE,,defect,,new,2011-09-30T23:15:36Z,2011-09-30T23:15:36Z,"Some customers have had issues with VMware where you have to enable / disable CHAP (or vice versa) in order to get iSCSI to work with FreeNAS. So far it's just believed to be VMware, but more exposure to VirtualBox, Windows, and Xen is required.",gcooper Active Tickets,885,NFS timesout from some linux clients.,Backend,8.0.1-RELEASE,,defect,,new,2011-10-05T09:31:26Z,2011-10-06T09:55:07Z,"I'm not convinced this is a freenas bug. When I try to connect from a linux server to nfs share I get timeouts but if I retry 2,3 times in quick succession I will eventually connect? Ubuntu Ver: 11.04 I've attached the tcpdump of x failed attempts to the successful one. The command I'm using to connect 192.168.130.1:/mnt/Storage/Mediafiles /mnt/files nfs rsize=8192,wsize=8192,timeo=15,vers=3,intr,bg ",daxroc Active Tickets,914,RAID1 volume shown as independent disks (Intel Embedded Server RAID II),FreeBSD,8.0.1-RELEASE,,defect,,new,2011-10-11T15:05:02Z,2011-10-12T06:09:57Z,A RAID1 volume on an Intel Embedded Server RAID II controller is shown as independend disks instead.,Christoph_vW Active Tickets,922,"ZFS Replication, Date and time",Backend,8.0.1-RELEASE,,defect,,new,2011-10-13T08:28:06Z,2011-10-18T22:16:54Z,I've run into the situation where replication failed after 2 days and narrowed down the bug to the two servers time being out of sync. It might be beneficial to compare the two servers date time settings and log a warning syslog if there out of sync? ,daxroc Active Tickets,927,NFS lockd locks up and hoses clients too,Backend,8.0.1-RELEASE,,defect,,new,2011-10-15T13:10:32Z,2012-03-14T18:21:05Z,"I'm running across a problem that seems very similar to http://lists.freebsd.org/pipermail/freebsd-net/2009-July/022443.html rpc.lockd appears to be getting stuck. When this happens, all other NFS clients basically go to hell eventually when they try a lock. On the FreeNAS side, the problem is characterized by rpc.lockd being stuck in ""rpcrec"", and a stream of kernel messages. % ps agxlww | grep lockd 0 1619 1 0 44 0 7956 804 rpcrec Ds ?? 0:02.45 /usr/sbin/rpc.lockd % dmesg NLM: failed to contact remote rpcbind, stat = 5, port = 28416 NLM: failed to contact remote rpcbind, stat = 5, port = 28416 NLM: failed to contact remote rpcbind, stat = 5, port = 28416 NLM: failed to contact remote rpcbind, stat = 5, port = 28416 NLM: failed to contact remote rpcbind, stat = 5, port = 28416 NLM: failed to contact remote rpcbind, stat = 5, port = 28416 NLM: failed to contact remote rpcbind, stat = 5, port = 28416 NLM: failed to contact remote rpcbind, stat = 5, port = 28416 etc On the client side, it's a stream of ""nfs server $foo:$mnt: lockd not responding"" The rpc.lockd process is not killable via kill -9; a reboot momentarily clears the condition. If you simultaneously reboot the client that apparently triggered the condition, then it sometimes goes away. Rebooting both the server and client fixes it, until the client tries it again. The client that is causing this is Apple OS X, and it seems to have been brought on by trying to share our photo archive and letting iPhoto create its library on the NFS share. I realize that this is not strictly a FreeNAS problem and is most likely FreeBSD's lockd implementation. However, I'm reporting it here because it's happening to me on FreeNAS and it's more likely to impact FreeNAS users.",jgreco Active Tickets,938,Manual means to execute smart tests from the smart test GUI,GUI,8.0.2-RELEASE,,defect,,new,2011-10-20T01:25:51Z,2011-10-20T01:25:51Z,There should be a manual means to run SMART tests from the GUI.,gcooper Active Tickets,943,crash when adding vlan interface to parent lagg0,Backend,8.3.0-BETA2,,defect,,reopened,2011-10-20T21:01:16Z,2012-09-11T13:52:21Z,"After defining an lagg0 interface consisting of 2 members, mxge0 and mxge1, this lagg0 interface is not selectable to create a vlan interface on until a reboot. When creating a vlan interface on lagg0, the system crashes: Fatel trap 12: page fault while in kernel mode cpuid = 9; apic id = 11 fault virtual address = 0x308 fault code = supervisor read data, page not present insruction pointer = 0x20:0xffffffff80535cee stack pointer = 0x28:0xffffff90e72ca960 frame pointer = 0x28:0xffffff90e72ca980 code segment = base 0x0, limit 0xfffff, type ox1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 12 (irq257: mxge0) trap number = 12 panic: page fault cpuid = 9 Uptime: 50m9s Cannot dump. Device not defined or unavailable. Manually it does work: ifconfig lagg0.1210 create ifconfig lagg0.1210 192.168.210.24/25 This does not result in a crash. Card: 10G-PCIE2-8B2-2S Firmware: 1.4.50 Regards, Marc",guardi Active Tickets,946,group tab does not allow gid change,Backend,8.0.1-RELEASE,,defect,,assigned,2011-10-21T19:15:34Z,2011-11-22T12:26:45Z,I tried to harmonize my uid and gid accross machines. It turned out modify groups does not allow gid change.,ikke Active Tickets,951,"""An error occurred while labeling the disk"" on importing existing NTFS drives",Backend,8.0.2-RELEASE,,defect,,reopened,2011-10-24T16:25:32Z,2012-12-08T21:46:40Z,"I 'migrated' from Windows 2008 R2 to Freenas. I have two existing NTFS array's which I want to import. When I import the array, the following message appears: ""An error occurred while labeling the disk"", and I'm not able to import the array..",Polyphemus Active Tickets,971,UTF-8 NetBIOS names problem with avahi,Backend,8.0.2-RELEASE,,defect,,new,2011-11-01T20:08:13Z,2011-11-08T19:16:54Z,"Avahi needs to be fixed for NetBIOS names that contain UTF-8 characters. Otherwise /var/log/messages fills in with messages like these: {{{ Oct 31 13:51:46 xxx avahi-daemon[14003]: avahi_normalize_name() failed. Oct 31 13:51:46 xxx avahi-daemon[14003]: server.c: Packet too short or invalid while reading question key. (Maybe a UTF-8 problem?) Oct 31 13:51:46 xxx avahi-daemon[14003]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?) }}} An example post that comments on this issue can be found here: http://forum.parallels.com/showthread.php?t=95030 .",gcooper Active Tickets,989,notifier 'restart' hammer needs fixing,Backend,8.0.2-RELEASE,,defect,,new,2011-11-08T01:13:31Z,2011-11-08T02:09:14Z,"Today, when someone toggles a service via the GUI it restarts the service: {{{ else: started = notifier().restart(changing_service) }}} This is not intelligent by any means as it increases the likelihood of service startup failure, and it adds to the service startup / teardown time unnecessarily, and quite frankly makes FreeNAS look like a slow solution to many users.",gcooper Active Tickets,993,Middleware doesn't check for configuration database compatibilty before migrating,Backend,8.0.2-RELEASE,,defect,,new,2011-11-08T17:03:27Z,2011-11-08T17:03:27Z,"The FreeNAS middleware and install goo doesn't track the configuration database version to ensure that a newer database isn't loaded on an older version of software. In most cases this should be benign as there will be additional tables, but this could also break FreeNAS when it tries to migrate or load the configuration.",gcooper Active Tickets,1015,"""Volumes"" and ""ZFS Volumes"" are overloaded terms; needs to be changed",Backend,8.0.2-RELEASE,,defect,,new,2011-11-15T23:37:43Z,2011-12-03T20:20:35Z,"It confuses people new to our software and those who may or may not be aware of some ZFS internals. Multiple people (users, customers, docs folks, me) have been screaming about this overly confusing naming scheme for a while now. Please.. fix this in the next major version (9.x) release.",gcooper Active Tickets,1059,ix-cache (cachetool.py) failures need to alert the user,Backend,8.0.2-RELEASE,,defect,,new,2011-11-30T19:09:54Z,2011-11-30T19:09:54Z,"If the cachetool fails to regenerate information properly, the user should be notified immediately that there's an issue that needs to be rectified. Otherwise it can create confusing scenarios where either the cache is empty or stale, and thus confuse the user.",gcooper Active Tickets,1071,Add GUI to display output for last SMART run,Backend,8.0.2-RELEASE,,defect,william,accepted,2011-12-06T01:13:40Z,2012-01-04T12:57:24Z,"Customer has requested that we add a way in the GUI to look at the last SMART run. There's a lot of data that gets output from smartctl; ultimately we need to just say pass/fail based on the following output: {{{ # smartctl -l xselftest /dev/ada0 smartctl 5.42 2011-10-20 r3458 [FreeBSD 9.0-RC2 amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 14392 - }}} smartctl -a prints out way too much output and a lot of it can be confusing to customers and home users.",gcooper Active Tickets,1089,istgt-20111008 Causing FS errors,Backend,,,defect,,new,2011-12-12T18:28:06Z,2012-11-29T11:07:58Z,"I apologize if this is the incorrect place for this, however, I could find no other area for reporting istgt issues outside of FreeNAS. I only use istgt. The current version and the previous version seem to be causing random FS errors. My setup is: FreeBSD 8.2-RELEASE exported zvols Linux open-iscsi initiator On Version 20111008 running normal mode I get the following errors on hosts with heavy IO. Dec 10 11:41:33 solman1 kernel: connection2:0: received itt 0 expected session age (b) Dec 10 11:41:33 solman1 kernel: connection2:0: detected conn error (1010) Dec 10 11:41:33 solman1 kernel: EXT3-fs error (device sdc1): ext3_lookup: unlinked inode 67504453 in dir #67471303 Dec 10 11:41:33 solman1 iscsid: Kernel reported iSCSI connection 2:0 error (1010) state (3) Dec 10 11:41:37 solman1 iscsid: connection2:0 is operational after recovery (1 attempts) These errors do not occur on 20110707 in normal mode. Switching to experimental mode will cause the same errors to start cropping up. This leads me to believe some code promoted to normal in 20111008 may be the issue. ",syshackmin Active Tickets,1101,Refreshing CIFS info kills off existing AFP shares,Backend,8.0.2-RELEASE,,defect,,new,2011-12-15T08:59:10Z,2011-12-15T11:25:32Z,"dbus is required by avahi-daemon and afpd. The problem is that reloading CIFS also kills off dbus, which in turn kills off afpd. This is wrong. FWIW, given that we're not modifying or generating dbus's config, we shouldn't stop and start dbus unnecessarily.",gcooper Active Tickets,1115,Failed upgrades due to lack of disk space aren't reported properly in the GUI/middleware,Backend,8.0.2-RELEASE,,defect,william,accepted,2011-12-20T23:44:54Z,2012-01-20T15:52:46Z,"If say, I fill up my volume and attempt to upgrade. What will happen is the GUI will get stuck indefinitely on the 'uploading' state. The problem is that the disk space requirement isn't determined up front and proper notification isn't sent to the user. All that happens is that lighttpd silently fails and nginx states (for example when I've seen it occur), that /var is full. My guess is the following code is at fault (on 8.0.3): {{{ filename = '/var/tmp/firmware/firmware.xz' fw = open(filename, 'wb+') if cleaned_data.get('firmware'): for c in cleaned_data['firmware'].chunks(): fw.write(c) fw.close() }}} or this code on trunk: {{{ filename = '/var/tmp/firmware/firmware.xz' if cleaned_data.get('firmware'): with open(filename, 'wb+') as fw: for c in cleaned_data['firmware'].chunks(): fw.write(c) }}} This logic should be pushed down into 'notifier' and sanitized so that it returns MiddlewareErrors on failure.",gcooper Active Tickets,1116,Scaling issues with /var and finding a more suitable resting place for scratch space,FreeBSD,8.0.2-RELEASE,,defect,,new,2011-12-21T02:35:16Z,2011-12-21T02:38:38Z,"We have a handful of services, like samba, nginx, etc that depend on /var to be sufficiently sized in order to continue operating. The tricky problem is that memory sizing doesn't suffice and services fall over at runtime (nmbd, smbd), unless sufficient space becomes available. The easy button was put in place in for r9244 and r9246 on FreeNAS which is going into 8.0.3 should stop the hemorrhaging, but we'll need to revisit some other choices, like creating specialized datasets, storage, the type of redundancy we might need for the data, what should occur if and when one needs to delete a volume/dataset/etc, and many more interesting scenarios, as the requirements will grow as the number of things people need to install grows as well. And unfortunately USB just doesn't cut it in terms of a quick and dirty scratch space, and in fact in many cases writing back to USB might wear level it to the point where it's no longer usable.",gcooper Active Tickets,1129,The logic for UFS + alternate mount points needs polishing,Backend,8.0.3-RC2,,defect,,new,2011-12-26T23:10:09Z,2011-12-26T23:10:09Z,"The following logic in gui/storage/forms.py needs work [in and fact should be moved to notifier as a grand, unified API, i.e. stage_mountpoint(self, src)]: {{{ if mp_path in ('/etc', '/var', '/usr'): device = '/dev/ufs/' + volume_name mp = '/mnt/' + volume_name if not access(mp, 0): mkdir(mp, 755) mount(device, mp) popen(""/usr/local/bin/rsync -avz '%s/*' '%s/'"" % (mp_path, mp)).close() umount(mp) if access(mp, 0): rmdir(mp) }}} It will most likely fail when unmounting /usr and /var as the disks are almost always in use, and depending on what is accessing /etc at the time, this can also fail in a transient manner. That and logic in the backend doesn't tidy up after memory disks (before reboot or after reboot), which just seems nasty as well because it unnecessarily wastes several GB of memory, and the contents on the USB backed storage will blast away any data that should persist on the UFS volumes. Any mount point outside of /mnt should be: 1. Mounted temporarily, 2. All files from the preexisting directory should be copied over to the new location. 3. The box should be rebooted. This is required to workaround the fact that the logic in our system doesn't work / capture errors in 100% of the cases.",gcooper Active Tickets,1136,ix-kinit needs to be run periodicly to ensure that kerberos tickets are fresh,Backend,8.0.3-RELEASE,,defect,,reopened,2011-12-30T23:21:10Z,2012-11-01T13:15:05Z,"Kerberos tickets have a short lifetime; the internal AD server we have at iX dolls out tickets good for 10 hours. What needs to occur is that ix-kinit needs to be rerun periodically (say every half hour) to determine whether or not the ticket is still valid and thus whether or not ix-kinit restart needs to be run -- otherwise the ticket will expire and bad things might happen when trying to connect to the AD/LDAP backend. Discovered in a debug session with ""bilbo"" on #freenas.",gcooper Active Tickets,1139,Some errors not caught/trickled up the stack when resolving records in rc.freenas,Backend,8.0.2-RELEASE,,defect,jhixson,new,2012-01-01T10:16:19Z,2012-01-01T10:16:19Z,"The following lines need to have error checking added to them: {{{ 413 dc=$(AD_get_domain_controller ""${domainname}"") # ... 419 gc=$(AD_get_global_catalog ""${domainname}"") }}} The following line needs to be split up to allow for error checking and post-processing (exit code lost in multiple pipes): {{{ 417 AD_set basedn=""$(AD_query_rootDSE|egrep '^defaultNamingContext'|cut -f2- -d:|xargs)"" }}}",gcooper Active Tickets,1150,Installer creates disk layout which prevents unused space being used,Build System,8.0.3-RC2,,defect,,new,2012-01-05T09:33:22Z,2012-01-06T01:19:15Z,"The installer creates an unusual disk layout, with 4 'freebsd' slices only 1 of which has any partitions in it - the others have filesystems created directly on the container. Due to this layout any extra space on a disk can't be used because all 4 MBR entries are used.",brucec Active Tickets,1151,GUI gets stuck when enumerating zpool if it's being scrubbed or when zpool or zfs blocks on zpool,Backend,8.0.2-RELEASE,,defect,,new,2012-01-06T01:41:16Z,2012-01-06T01:41:16Z,"This is primarily a documentation note for now, but what happened is one of the test machines at iX was doing data correction via a scrub on one of the drives that reported errors via a periodic scrub (unknown to me), and when I tried to view the volumes in the GUI it got stuck. The main takeaway from this is that we need to rethink how this should be done (cache the mountpoints periodically?), and/or fail gracefully/quickly if the zpool list command fails to return in a reasonable time frame -- otherwise it causes user confusion as to why certain things in the GUI don't respond, and could cause other commands that depend on zpool list, zfs list, etc to hang. zfs / zpool might need to be written to take a non-blocking option (and this might be the best overall solution to this problem).",gcooper Active Tickets,1158,samba and ldap wrong domain,Backend,8.0.3-RC2,,defect,,new,2012-01-09T09:05:32Z,2013-05-20T17:14:30Z,"while samba is setup with domain FOO and FOO also exists in ldap freenas uses FREENAS as domainname and writes it to ldap. /usr/local/etc/smb.conf uses FOO as domain, but authentication over ldap uses FREENAS, so no user is able to connect to her shares.",merlin81 Active Tickets,1182,Interface glue doesn't verify that settings actually stick after applying them,Backend,8.0.3-RELEASE,,defect,,new,2012-01-12T22:09:14Z,2012-07-25T12:26:56Z,"There are some cases where if I supply an invalid vlan, mtu, etc to an interface, the problem is that the middleware code that should be managing the interfaces and reporting failures do not actually verify that the operations succeeded, and thus the problem is that the user can be mislead with the settings input, which leads to unnecessarily support sessions chasing down what the issue was. As an example, take a machine or VM with a NIC hooked up to a network with an mtu of 1500 and add 'mtu 27000000' to the options field. Check the /var/log/messages and netif output and you'll see that the command was attempted, but failed. What makes this more painful is that depending on how the keywords are formulating in the ifconfig_* variable, this could fail to set important state information, such as whether or not the interface is up, down, etc.",gcooper Active Tickets,1193,"Consolidate GEOM, UFS, ZFS debug output into a single option",Backend,8.0.2-RELEASE,,defect,,new,2012-01-13T23:19:13Z,2012-01-13T23:19:13Z,"Similar to ticket 1192, GEOM, UFS, ZFS, etc could and should be consolidated into one output (Storage) option to be generic.",gcooper Active Tickets,1200,FreeNAS does not work with Hyper-V,Backend,8.0.3-RELEASE,,defect,,new,2012-01-17T22:02:08Z,2012-01-17T22:02:08Z,"When trying to run FreeNAS in a virtual environment under Microsoft Server 2008 R2 SP1 Hyper-V the network card will fail to work. Setting a static IP will result in loss of network connectivity. Setting to DHCP will only work after taking the NIC down and back up again via Shell commands. The workaround can be detailed here. http://forums.freenas.org/showthread.php?2146-Hyper-V-amp-Freenas-8 I'm assuming it is an issue with the virtual NIC ""Legacy Network Adapter"". Using the regular virtual NIC ""Network Adapter"" results in FreeNAS not even detecting a NIC. Adding support for the faster ""Network Adapter"" (as opposed to the Legacy version) is preferred.",warmace Active Tickets,1205,Problem with joining Win2003 Domain,Backend,8.0.3-RC2,,defect,,new,2012-01-19T15:30:37Z,2012-11-23T11:41:15Z,"When i try to join our domain i get an error that i can not understand! Here the output under /var/log/messages: '''Jan 19 07:06:37 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-kinit status Jan 19 07:06:54 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-kerberos quietstart Jan 19 07:07:00 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-nsswitch quietstart Jan 19 07:07:00 freenas1 freenas: Generating host.conf. Jan 19 07:07:00 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-pam quietstart Jan 19 07:07:00 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-samba quietstart Jan 19 07:07:00 freenas1 freenas: Importing account for root...ok Jan 19 07:07:06 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-kinit quietstart Jan 19 07:07:22 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-kinit status Jan 19 07:07:28 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-activedirectory quietstart Jan 19 07:07:42 freenas1 freenas: Using short domain name -- DUO Jan 19 07:07:42 freenas1 freenas: Joined 'FREENAS1' to realm 'direktundonline.de' Jan 19 07:07:55 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-activedirectory status Jan 19 07:08:03 freenas1 freenas[2072]: Executing: /usr/sbin/service samba forcestop Jan 19 07:08:03 freenas1 freenas: Stopping winbindd. Jan 19 07:08:03 freenas1 freenas: Waiting for PIDS: 5496. Jan 19 07:08:03 freenas1 freenas[2072]: Executing: /usr/bin/killall nmbd Jan 19 07:08:03 freenas1 freenas: No matching processes were found Jan 19 07:08:03 freenas1 freenas[2072]: Executing: /usr/bin/killall smbd Jan 19 07:08:03 freenas1 freenas: No matching processes were found Jan 19 07:08:03 freenas1 freenas[2072]: Executing: /usr/bin/killall winbindd Jan 19 07:08:03 freenas1 freenas: No matching processes were found Jan 19 07:08:03 freenas1 freenas[2072]: Executing: /usr/sbin/service samba quietstart Jan 19 07:08:03 freenas1 freenas: Removing stale Samba tdb files: .. done Jan 19 07:08:03 freenas1 freenas: Starting winbindd.''' up to this point everything is OK. The output ""of wbinfo -u"" give the List of the Domain-Users. Then it seems that the Service restarts and dies with the error ""No realm set, are we joined ?"" Here is the second part of the log: '''Jan 19 07:08:03 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-kinit status Jan 19 07:08:09 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-activedirectory status Jan 19 07:08:49 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-kerberos quietstart Jan 19 07:08:49 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-nsswitch quietstart Jan 19 07:08:49 freenas1 freenas: Generating host.conf. Jan 19 07:08:49 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-pam quietstart Jan 19 07:08:49 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-samba quietstart Jan 19 07:08:49 freenas1 freenas: Importing account for root...ok Jan 19 07:08:49 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-kinit forcestop Jan 19 07:08:49 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-activedirectory forcestop Jan 19 07:08:55 freenas1 freenas: No realm set, are we joined ? Jan 19 07:08:55 freenas1 freenas[2072]: Executing: /usr/sbin/service samba forcestop Jan 19 07:08:55 freenas1 freenas[2072]: Executing: /usr/bin/killall nmbd Jan 19 07:08:55 freenas1 freenas: No matching processes were found Jan 19 07:08:55 freenas1 freenas[2072]: Executing: /usr/bin/killall smbd Jan 19 07:08:55 freenas1 freenas: No matching processes were found Jan 19 07:08:55 freenas1 freenas[2072]: Executing: /usr/bin/killall winbindd Jan 19 07:08:55 freenas1 freenas[2072]: Executing: /usr/sbin/service samba quietstart Jan 19 07:08:55 freenas1 freenas: Removing stale Samba tdb files: .. done Jan 19 07:08:55 freenas1 freenas[2072]: Executing: /usr/sbin/service ix-kinit status''' What kan i doo to resolve it? Thanks Walter",wmar Active Tickets,1211,LDAP client authenticates successfully but fails at authorization stage,Backend,8.0.3-RELEASE,,defect,,new,2012-01-24T05:18:26Z,2012-11-26T15:47:05Z,"http://forums.freenas.org/showthread.php?5392-FreeNAS-LDAP-client-authenticates-successfully-but-fails-at-authorization-stage I've included detailed logs and description in the forum post",mmx Active Tickets,1220,AFP does not recognize AD Groups,Backend,8.0.3-RELEASE,,defect,,new,2012-01-27T17:37:54Z,2013-01-25T23:53:59Z,"With a install bound to Active Directory, AFP will obey permissions for a share's Owners but not for a share's group permissions when the group is set to an AD group. The system is able to query the groups from the CLI, and obey them for CIFS shares. ",jstillwa Active Tickets,1228,Traceback when /var is full when winbindd is still running,Backend,8.0.3-RELEASE-p1,,defect,,reopened,2012-02-01T02:54:38Z,2012-02-01T15:10:11Z,"Cranked up the samba noise this morning, and this is the traceback I got when opening up the CIFS settings. {{{ Environment: Software Version: FreeNAS-8.2.1-ALPHA-r9901-x64 Request Method: GET Request URL: http://dhcp-84/admin/app-services/CIFS/edit/1/ Traceback: File ""/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py"" in get_response 105. response = middleware_method(request, callback, callback_args, callback_kwargs) File ""/usr/local/www/freenasUI/freeadmin/middleware.py"" in process_view 69. return login_required(view_func)(request,*view_args,**view_kwargs) File ""/usr/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py"" in _wrapped_view 23. return view_func(request, *args, **kwargs) File ""/usr/local/www/freenasUI/freeadmin/views.py"" in generic_model_edit 648. mf = mf(instance=instance) File ""/usr/local/www/freenasUI/common/forms.py"" in __init__ 49. field._reroll() File ""/usr/local/www/freenasUI/freeadmin/forms.py"" in _reroll 88. if len(FreeNAS_Users(flags=FLAGS_DBINIT|FLAGS_CACHE_READ_USER|FLAGS_CACHE_WRITE_USER)) > 500: File ""/usr/local/www/freenasUI/common/freenasusers.py"" in __init__ 281. self.__users = FreeNAS_Directory_Users(**kwargs) File ""/usr/local/www/freenasUI/common/freenasldap.py"" in __new__ 1769. obj = FreeNAS_ActiveDirectory_Users(**kwargs) File ""/usr/local/www/freenasUI/common/freenasldap.py"" in __init__ 1633. self.__domains = self.get_domains() File ""/usr/local/www/freenasUI/common/freenasldap.py"" in get_domains 1243. root = self.get_root_domain() File ""/usr/local/www/freenasUI/common/freenasldap.py"" in get_root_domain 1200. rdnc = rootDSE[0][1]['rootDomainNamingContext'][0] Exception Type: TypeError at /admin/app-services/CIFS/edit/1/ Exception Value: 'NoneType' object is not subscriptable }}}",gcooper Active Tickets,1246,Inconsistent Naming conventions,GUI,8.0.3-RELEASE-p1,,defect,,new,2012-02-05T15:55:46Z,2012-02-06T09:22:13Z,"When saving changes in the UI the ""Apply"" button often have different names. '''Save OK''' This should be avoided. I think a ""Save"" ist good to tell a user what happen. ",bubulein Active Tickets,1262,'Inherit permissions' shouldn't be enabled [on share] when Windows ACLs are enabled,GUI,8.0.3-RELEASE-p1,,defect,,new,2012-02-08T00:21:12Z,2012-02-16T16:44:07Z,"There was a user reported issue where when 'inherit permissions' and 'Windows ACLs' were turned on and unfortunately the permissions of several directories were incorrectly setup to the point that we needed to backpedal the permissions settings and turn off that setting as well. Bottom line for this ticket is that that option ('inherit permissions') should not be enabled or hidden in the GUI if 'Windows ACLs' is set on the volume(s)/datasets.",gcooper Active Tickets,1267,Providing alternate mountpoints with UFS volumes doesn't work if mountpoint doesn't already exist,Backend,8.0.3-RELEASE-p1,,defect,,new,2012-02-12T03:31:44Z,2012-02-12T03:31:44Z,"One of the cases that a user in #freenas ran into is if he specified /jail for the mountpoint of a new UFS volume with 8.0.3-p1, the operation would silently fail and the volume/mountpoint entry would be created in the database. Every instance when he rebooted thereafter he was kicked into singleuser mode and had to [eventually] remove the entry from the database in order to generate a sane /erc/fstab and continue. In future versions (8.2.1-ALPHA) this isn't even possible; the GUI says, ""Path does not exist."" and bails. What needs to be done to improve this is one of the following items: 1. The path should be added to the base image 2. The path should be precreated on the base system in such a way that it's mounted at boot prior to mountcritlocal being run. This needs to be done for UFS primarily, but also for ZFS if we decide to add support for it to point elsewhere via altroot= . Specifying a directory in /tmp, /var, etc would be acceptable as well.. right now the requirements aren't documented and that needs to be remedied.",gcooper Active Tickets,1269,Add disk space check for service pack / firmware upgrades and plugin [jail] installs,Backend,8.0.2-RELEASE,,defect,,new,2012-02-12T04:24:09Z,2012-02-19T07:41:27Z,"Some of the issues that have occurred on the forums and #freenas with upgrade failures have been because there isn't enough space on the target volume to perform the firmware / service pack upgrades. Checking for at least 5GB of free space on the target media would probably be a good idea.",gcooper Active Tickets,1299,Unable to configure lagg interface with existing interfaces up and running,GUI,8.0.4-BETA1,,defect,,new,2012-02-26T16:27:15Z,2012-02-26T16:27:15Z,"On 8.0.4-RC1 it is impossible to configure a lagg device when the network interfaces you are trying to use are already assigned to the network. As much as I understand the technical concept behind that for an administrative perspective that makes things awkward. You should be able to still configure lagg on those devices. The physical NICs do not show up in the list of possible devices (see screen shot) {{{ ifconfig ale0: flags=8843 metric 0 mtu 1500 options=c319a ether 00:22:15:da:c2:ed inet6 fe80::222:15ff:feda:c2ed%ale0 prefixlen 64 scopeid 0x1 inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255 inet6 2001:470:1f15:120:222:15ff:feda:c2ed prefixlen 64 autoconf nd6 options=3 media: Ethernet autoselect (1000baseT ) status: active em0: flags=8843 metric 0 mtu 1500 options=209b ether 00:1b:21:2f:e4:11 inet6 fe80::21b:21ff:fe2f:e411%em0 prefixlen 64 scopeid 0x2 inet 192.168.1.40 netmask 0xffffff00 broadcast 192.168.1.255 inet6 2001:470:1f15:120:21b:21ff:fe2f:e411 prefixlen 64 autoconf nd6 options=3 media: Ethernet autoselect (1000baseT ) status: active lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 nd6 options=3 }}} ",dmalloc Active Tickets,1310,Processes hanging in zfsvfs state.,FreeBSD,8.0.3-RELEASE-p1,,defect,,new,2012-03-03T19:54:51Z,2013-03-30T22:39:36Z,"I was copying some files over to my nas via cifs when the copies suddenly stopped. If I ssh into the server, I can see many processes, including smbd, stuck in zfsvfs state. Doing an ls in /mnt/ or my zfs filesystem /mnt/storage causes the command to simply hang and not respond to ctrl+c. Top will show it sitting in the zfsvfs state. Trying to connect to the process with gdb* causes gdb to hang after the line ""Attaching to program: /bin/ls, process 59886"", top shows gdb to be sitting in the ""wait"" state. This is the second time I've experianced a lockup like this, tho I didn't collect enough debug info the first time to be completely certain it was the same problem. I don't know enough about kernel debugging to generate anything useful for it. I experimented with kgdb and ddb but wasn't able to figure out how to get anything useful out of them. I'm going to reboot it now since I want access to my data, I hope the info collected below is helpful. *gdb really should be including with freenas in order to provide backtraces, I had to download a copy from a normal FreeBSD server I have == Top output == {{{ last pid: 60051; load averages: 0.00, 0.02, 0.00 up 6+19:02:07 11:08:29 95 processes: 1 running, 94 sleeping CPU: % user, % nice, % system, % interrupt, % idle Mem: 75M Active, 135M Inact, 7034M Wired, 54M Cache, 203M Buf, 615M Free Swap: 5119M Total, 13M Used, 5106M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 2157 root 7 44 0 67092K 5904K ucond 2 18:05 0.00% collectd 1806 root 1 44 0 6772K 492K select 3 13:38 0.00% powerd 40652 root 4 44 0 32156K 5360K ucond 0 3:15 0.00% istgt 42082 root 1 76 0 51784K 6680K zfsvfs 2 1:19 0.00% smbd 2047 root 6 46 0 210M 80068K uwait 0 1:12 0.00% python 1798 root 1 44 0 11780K 1120K select 2 0:45 0.00% ntpd 2537 www 1 44 0 19328K 2236K kqread 2 0:29 0.00% lighttpd 2279 root 1 52 0 7832K 684K nanslp 0 0:17 0.00% cron 1635 root 1 44 0 39216K 2108K select 2 0:16 0.00% nmbd 1205 root 1 44 0 6904K 700K select 1 0:06 0.00% syslogd 1344 root 4 44 0 5684K 420K rpcsvc 0 0:06 0.00% nfsd 1639 root 1 44 0 46796K 2944K select 0 0:04 0.00% smbd 1372 root 1 76 0 7956K 456K rpcsvc 0 0:02 0.00% rpc.lockd 666 root 1 54 0 5684K 632K select 1 0:02 0.00% dhclient 1341 root 1 44 0 7964K 864K select 2 0:02 0.00% rpcbind 688 _dhcp 1 44 0 5684K 808K select 0 0:01 0.00% dhclient 1358 root 1 44 0 263M 496K select 0 0:01 0.00% rpc.statd 1557 root 1 44 0 13408K 1304K nanslp 2 0:01 0.00% smartd 1698 root 1 44 0 46796K 2408K select 3 0:00 0.00% smbd 2637 root 1 76 0 64100K 1888K ttyin 1 0:00 0.00% python 59876 root 1 50 0 33304K 4288K sbwait 0 0:00 0.00% sshd 59791 cstdenis 1 44 0 33304K 4212K select 1 0:00 0.00% sshd 59891 cstdenis 1 44 0 33304K 4292K select 0 0:00 0.00% sshd 59825 root 1 44 0 10172K 2564K pause 0 0:00 0.00% csh 59896 root 1 44 0 10172K 2652K pause 0 0:00 0.00% csh 59972 root 1 46 0 33304K 4300K sbwait 0 0:00 0.00% sshd 59879 cstdenis 1 44 0 10172K 2620K pause 2 0:00 0.00% csh 2461 root 1 44 0 6900K 1068K zfsvfs 0 0:00 0.00% mountd 59927 root 1 49 0 51280K 5516K zfsvfs 1 0:00 0.00% smbd 59804 root 1 49 0 51280K 5504K zfsvfs 0 0:00 0.00% smbd 59797 root 1 49 0 51280K 5500K zfsvfs 1 0:00 0.00% smbd 59792 cstdenis 1 44 0 10172K 2664K pause 2 0:00 0.00% csh 59969 root 1 48 0 51280K 5512K zfsvfs 0 0:00 0.00% smbd 60011 root 1 49 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd 59963 root 1 48 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd 60014 root 1 49 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd 60008 root 1 49 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd 60048 root 1 49 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd 59920 root 1 49 0 51280K 5512K zfsvfs 0 0:00 0.00% smbd 59966 root 1 48 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd 59840 root 1 48 0 51280K 5504K zfsvfs 1 0:00 0.00% smbd 59810 root 1 49 0 51280K 5500K zfsvfs 0 0:00 0.00% smbd 59882 root 1 48 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd 59975 cstdenis 1 44 0 10172K 2632K pause 0 0:00 0.00% csh 59780 root 1 45 0 51768K 5780K h->has 1 0:00 0.00% smbd 60038 root 1 46 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd 59902 root 1 47 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd 59945 root 1 47 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd 59837 root 1 47 0 51280K 5500K zfsvfs 1 0:00 0.00% smbd 59824 cstdenis 1 44 0 19368K 1592K wait 0 0:00 0.00% su 59974 cstdenis 1 44 0 33304K 4300K select 0 0:00 0.00% sshd 59892 cstdenis 1 44 0 10172K 2580K pause 0 0:00 0.00% csh 59781 root 1 44 0 33304K 4160K sbwait 2 0:00 0.00% sshd 59889 root 1 44 0 33304K 4292K sbwait 0 0:00 0.00% sshd 60005 root 1 45 0 51280K 5512K zfsvfs 0 0:00 0.00% smbd 1343 root 1 44 0 5684K 480K select 0 0:00 0.00% nfsd 59878 cstdenis 1 44 0 33304K 4288K select 1 0:00 0.00% sshd 2257 root 1 44 0 24976K 1396K select 1 0:00 0.00% sshd 59861 root 1 45 0 51280K 5504K zfsvfs 1 0:00 0.00% smbd 893 root 1 44 0 3204K 416K select 1 0:00 0.00% devd 59895 cstdenis 1 44 0 19368K 1592K wait 1 0:00 0.00% su 59894 root 1 44 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd 59834 root 1 44 0 51280K 5500K zfsvfs 0 0:00 0.00% smbd 60030 root 1 44 0 51280K 5512K zfsvfs 1 0:00 0.00% smbd }}} == Other info == Nothing interesting in dmesg or /var/log/messages == Server version == {{{ [cstdenis@Server] /> uname -a FreeBSD Server.local 8.2-RELEASE-p6 FreeBSD 8.2-RELEASE-p6 #0: Wed Jan 18 13:52:11 PST 2012 root@build.ixsystems.com:/build/home/gcooper/e2e-bld.Pp7kV0qa/obj.amd64/build/home/gcooper/e2e-bld.Pp7kV0qa/FreeBSD/src/sys/FREENAS.amd64 amd64 }}} FreeNAS-8.0.3-RELEASE-p1-x64 (9591) (I know I'm not running the latest FreeNAS version, but I didn't see anything in the release notes to suggest it's running a later kernel than this) == Hardware == * Supermicro motherboard with a Q6700 and 8GB ram. * 5 x 3TB WD green drives (WD30EZRS-00J99B0) running on the onboard sata controller (Intel ICH9 AHCI SATA controller) * OS running on a large USB stick == ZFS sysctl info == {{{ [cstdenis@Server] /> sysctl -a | grep zfs vfs.zfs.l2c_only_size: 0 vfs.zfs.mfu_ghost_data_lsize: 4402426880 vfs.zfs.mfu_ghost_metadata_lsize: 1229496832 vfs.zfs.mfu_ghost_size: 5631923712 vfs.zfs.mfu_data_lsize: 4096 vfs.zfs.mfu_metadata_lsize: 11196416 vfs.zfs.mfu_size: 50327552 vfs.zfs.mru_ghost_data_lsize: 247693312 vfs.zfs.mru_ghost_metadata_lsize: 265535488 vfs.zfs.mru_ghost_size: 513228800 vfs.zfs.mru_data_lsize: 3631169536 vfs.zfs.mru_metadata_lsize: 1221852160 vfs.zfs.mru_size: 4964967424 vfs.zfs.anon_data_lsize: 0 vfs.zfs.anon_metadata_lsize: 0 vfs.zfs.anon_size: 667207168 vfs.zfs.l2arc_norw: 1 vfs.zfs.l2arc_feed_again: 1 vfs.zfs.l2arc_noprefetch: 0 vfs.zfs.l2arc_feed_min_ms: 200 vfs.zfs.l2arc_feed_secs: 1 vfs.zfs.l2arc_headroom: 2 vfs.zfs.l2arc_write_boost: 8388608 vfs.zfs.l2arc_write_max: 8388608 vfs.zfs.arc_meta_limit: 1805965312 vfs.zfs.arc_meta_used: 1836742592 vfs.zfs.mdcomp_disable: 0 vfs.zfs.arc_min: 902982656 vfs.zfs.arc_max: 7223861248 vfs.zfs.zfetch.array_rd_sz: 1048576 vfs.zfs.zfetch.block_cap: 256 vfs.zfs.zfetch.min_sec_reap: 2 vfs.zfs.zfetch.max_streams: 8 vfs.zfs.prefetch_disable: 0 vfs.zfs.check_hostid: 1 vfs.zfs.recover: 0 vfs.zfs.txg.write_limit_override: 0 vfs.zfs.txg.synctime: 5 vfs.zfs.txg.timeout: 30 vfs.zfs.scrub_limit: 10 vfs.zfs.vdev.cache.bshift: 16 vfs.zfs.vdev.cache.size: 10485760 vfs.zfs.vdev.cache.max: 16384 vfs.zfs.vdev.aggregation_limit: 131072 vfs.zfs.vdev.ramp_rate: 2 vfs.zfs.vdev.time_shift: 6 vfs.zfs.vdev.min_pending: 4 vfs.zfs.vdev.max_pending: 10 vfs.zfs.cache_flush_disable: 0 vfs.zfs.zil_disable: 0 vfs.zfs.zio.use_uma: 0 vfs.zfs.version.zpl: 4 vfs.zfs.version.spa: 15 vfs.zfs.version.dmu_backup_stream: 1 vfs.zfs.version.dmu_backup_header: 2 vfs.zfs.version.acl: 1 vfs.zfs.debug: 0 vfs.zfs.super_owner: 0 kstat.zfs.misc.zfetchstats.hits: 97526871 kstat.zfs.misc.zfetchstats.misses: 4612176 kstat.zfs.misc.zfetchstats.colinear_hits: 4700 kstat.zfs.misc.zfetchstats.colinear_misses: 4607476 kstat.zfs.misc.zfetchstats.stride_hits: 91616862 kstat.zfs.misc.zfetchstats.stride_misses: 98578 kstat.zfs.misc.zfetchstats.reclaim_successes: 166308 kstat.zfs.misc.zfetchstats.reclaim_failures: 4441168 kstat.zfs.misc.zfetchstats.streams_resets: 7825 kstat.zfs.misc.zfetchstats.streams_noresets: 5900871 kstat.zfs.misc.zfetchstats.bogus_streams: 0 kstat.zfs.misc.arcstats.hits: 66930639 kstat.zfs.misc.arcstats.misses: 15885187 kstat.zfs.misc.arcstats.demand_data_hits: 50085315 kstat.zfs.misc.arcstats.demand_data_misses: 7599250 kstat.zfs.misc.arcstats.demand_metadata_hits: 11838784 kstat.zfs.misc.arcstats.demand_metadata_misses: 1075101 kstat.zfs.misc.arcstats.prefetch_data_hits: 4560367 kstat.zfs.misc.arcstats.prefetch_data_misses: 7190096 kstat.zfs.misc.arcstats.prefetch_metadata_hits: 446173 kstat.zfs.misc.arcstats.prefetch_metadata_misses: 20740 kstat.zfs.misc.arcstats.mru_hits: 31002381 kstat.zfs.misc.arcstats.mru_ghost_hits: 136498 kstat.zfs.misc.arcstats.mfu_hits: 31866944 kstat.zfs.misc.arcstats.mfu_ghost_hits: 331864 kstat.zfs.misc.arcstats.allocated: 124595293 kstat.zfs.misc.arcstats.deleted: 122545104 kstat.zfs.misc.arcstats.stolen: 92376383 kstat.zfs.misc.arcstats.recycle_miss: 491682 kstat.zfs.misc.arcstats.mutex_miss: 192510 kstat.zfs.misc.arcstats.evict_skip: 2764462 kstat.zfs.misc.arcstats.evict_l2_cached: 0 kstat.zfs.misc.arcstats.evict_l2_eligible: 1697641715712 kstat.zfs.misc.arcstats.evict_l2_ineligible: 107009837056 kstat.zfs.misc.arcstats.hash_elements: 772111 kstat.zfs.misc.arcstats.hash_elements_max: 1113404 kstat.zfs.misc.arcstats.hash_collisions: 129871451 kstat.zfs.misc.arcstats.hash_chains: 126546 kstat.zfs.misc.arcstats.hash_chain_max: 35 kstat.zfs.misc.arcstats.p: 5659465692 kstat.zfs.misc.arcstats.c: 6145300340 kstat.zfs.misc.arcstats.c_min: 902982656 kstat.zfs.misc.arcstats.c_max: 7223861248 kstat.zfs.misc.arcstats.size: 6134942656 kstat.zfs.misc.arcstats.hdr_size: 184806400 kstat.zfs.misc.arcstats.data_size: 5682502144 kstat.zfs.misc.arcstats.other_size: 267634112 kstat.zfs.misc.arcstats.l2_hits: 0 kstat.zfs.misc.arcstats.l2_misses: 0 kstat.zfs.misc.arcstats.l2_feeds: 0 kstat.zfs.misc.arcstats.l2_rw_clash: 0 kstat.zfs.misc.arcstats.l2_read_bytes: 0 kstat.zfs.misc.arcstats.l2_write_bytes: 0 kstat.zfs.misc.arcstats.l2_writes_sent: 0 kstat.zfs.misc.arcstats.l2_writes_done: 0 kstat.zfs.misc.arcstats.l2_writes_error: 0 kstat.zfs.misc.arcstats.l2_writes_hdr_miss: 0 kstat.zfs.misc.arcstats.l2_evict_lock_retry: 0 kstat.zfs.misc.arcstats.l2_evict_reading: 0 kstat.zfs.misc.arcstats.l2_free_on_write: 0 kstat.zfs.misc.arcstats.l2_abort_lowmem: 0 kstat.zfs.misc.arcstats.l2_cksum_bad: 0 kstat.zfs.misc.arcstats.l2_io_error: 0 kstat.zfs.misc.arcstats.l2_size: 0 kstat.zfs.misc.arcstats.l2_hdr_size: 0 kstat.zfs.misc.arcstats.memory_throttle_count: 0 kstat.zfs.misc.arcstats.l2_write_trylock_fail: 0 kstat.zfs.misc.arcstats.l2_write_passed_headroom: 0 kstat.zfs.misc.arcstats.l2_write_spa_mismatch: 0 kstat.zfs.misc.arcstats.l2_write_in_l2: 0 kstat.zfs.misc.arcstats.l2_write_io_in_progress: 0 kstat.zfs.misc.arcstats.l2_write_not_cacheable: 1307805 kstat.zfs.misc.arcstats.l2_write_full: 0 kstat.zfs.misc.arcstats.l2_write_buffer_iter: 0 kstat.zfs.misc.arcstats.l2_write_pios: 0 kstat.zfs.misc.arcstats.l2_write_buffer_bytes_scanned: 0 kstat.zfs.misc.arcstats.l2_write_buffer_list_iter: 0 kstat.zfs.misc.arcstats.l2_write_buffer_list_null_iter: 0 kstat.zfs.misc.vdev_cache_stats.delegations: 10557 kstat.zfs.misc.vdev_cache_stats.hits: 113126 kstat.zfs.misc.vdev_cache_stats.misses: 1923373 }}} == zpool status == {{{ [cstdenis@Server] /> zpool status pool: storage state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ada0p2 ONLINE 0 0 0 ada1p2 ONLINE 0 0 0 ada2p2 ONLINE 0 0 0 ada3p2 ONLINE 0 0 0 ada4p2 ONLINE 0 0 0 errors: No known data errors }}} == zfs get all == {{{ [cstdenis@Server] /> zfs get all NAME PROPERTY VALUE SOURCE storage type filesystem - storage creation Sat Feb 18 1:33 2012 - storage used 5.96T - storage available 4.75T - storage referenced 2.95T - storage compressratio 1.00x - storage mounted yes - storage quota none default storage reservation none default storage recordsize 128K default storage mountpoint /mnt/storage default storage sharenfs off default storage checksum on default storage compression off default storage atime off local storage devices on default storage exec on default storage setuid on default storage readonly off default storage jailed off default storage snapdir hidden default storage aclmode passthrough local storage aclinherit passthrough local storage canmount on default storage shareiscsi off default storage xattr off temporary storage copies 1 default (hangs after this point) }}} == zpool iostat -v 1 == {{{ [cstdenis@Server] /> zpool iostat -v 1 capacity operations bandwidth pool used avail read write read write ---------- ----- ----- ----- ----- ----- ----- storage 7.47T 6.16T 27 208 1.37M 1.81M raidz1 7.47T 6.16T 27 208 1.37M 1.81M ada0p2 - - 9 42 315K 547K ada1p2 - - 9 42 344K 547K ada2p2 - - 9 42 347K 547K ada3p2 - - 9 42 324K 547K ada4p2 - - 9 42 295K 547K ---------- ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool used avail read write read write ---------- ----- ----- ----- ----- ----- ----- storage 7.47T 6.16T 0 0 0 0 raidz1 7.47T 6.16T 0 0 0 0 ada0p2 - - 0 0 0 0 ada1p2 - - 0 0 0 0 ada2p2 - - 0 0 0 0 ada3p2 - - 0 0 0 0 ada4p2 - - 0 0 0 0 ---------- ----- ----- ----- ----- ----- ----- capacity operations bandwidth pool used avail read write read write ---------- ----- ----- ----- ----- ----- ----- storage 7.47T 6.16T 0 0 0 0 raidz1 7.47T 6.16T 0 0 0 0 ada0p2 - - 0 0 0 0 ada1p2 - - 0 0 0 0 ada2p2 - - 0 0 0 0 ada3p2 - - 0 0 0 0 ada4p2 - - 0 0 0 0 ---------- ----- ----- ----- ----- ----- ----- }}}",cstdenis Active Tickets,1312,[Rsync] Path length,Backend,8.2.0-BETA2,,defect,,new,2012-03-04T01:00:42Z,2013-02-12T00:54:31Z,"Hi, I can't synchronize long path with rsync. When i try, i get the error : freenas rsyncd[8782]: overflow: xflags=0x78 l1=255 l2=817 lastname=ECRYPTFS_FNEK_ENCRYPTED.FWb.3TSoMo3NJUZUkEMmZH86eF913qzhoGDH4nEuctEVT.c..... freenas rsyncd[8782]: ERROR: buffer overflow in recv_file_entry [generator] After some search, it seems that the MAXPATHLEN option in Rsync is set to 255. Thanks. ",NitamaNai Active Tickets,1346,mfistatus.py incorrectly filters out dropped LUNs/controllers,Backend,8.2.0-BETA1,,defect,,new,2012-03-04T19:26:25Z,2012-03-04T19:26:25Z,"The following section of code in mfistatus.py implicitly only scans for existing LUNs... {{{ devs = os.listdir(""/dev"") for dev in devs: if dev.startswith(""mfi""): }}} so if I had a LUN that way tied into the GUI say and completely dropped off the map (has happened once from what I've seen), then the 'status' will go missed. This is particularly important for tracking cases where a partial or complete HW RAID card failure would not be caught in the GUI, depending on how it failed; there's some level of ""redundancy"" built into the alert system where degraded zpools will indirectly point to an issue with the controller, but the problem is that it takes some time for that info to be trickled up to the end-user because of the ZFS sticky fingers bug noted in ticket # 1066. What needs to be done is that the LUNs tied into other subsystems (be they the storage.volumes subsystem, etc) need to be tied into the script in such a way (even if it's just a command line argument) so the script can help audit whether or not there's a complete HW RAID controller failure. Please do not rewrite the script to integrate it directly into django/sqlite :). It's fairly simple and well written the way it is and can be used outside of django.. it just needs a little more love.",gcooper Active Tickets,1355,AD administrator usernames with non-alphanumeric chars aren't handled properly,GUI,8.2.0-BETA1,,defect,,assigned,2012-03-05T01:16:04Z,2012-04-14T04:31:07Z,"See: http://support.microsoft.com/kb/909264 for the official requirements. Try inputting: ""ニャン・カット"" as the username with password: ""meowmeow"".",gcooper Active Tickets,1399,Improve robustness of replication,Backend,8.0.3-RELEASE,,defect,delphij,new,2012-03-14T22:05:29Z,2012-03-14T22:16:28Z,"Put a note here. It seems that a DNS issue could cause replication to enter a state where it won't recover, basically, the remote side holds a snapshot newer than the expected one, where the recovery logic is not triggered. Review of the replication script would be needed, and one more try of ""zfs rollback"" should happen if the recorded snapshot is found on the remote side. Note: in order to workaround this issue, the user can use 'zfs rollback -r' to restore the remote side to ""known good"" state.",delphij Active Tickets,1430,Samba & LDAP authentication issue,Backend,8.0.4-RELEASE,,defect,,new,2012-03-29T21:00:08Z,2012-11-19T20:30:20Z,"I have set up a new FreeNAS 8.04 system, authenticating against an OpenLDAP server running on an Ubuntu 11.10 server. LDAP authentication works fine for both SSH access and AFP share access, however when trying to connect to a CIFS share, every attempt is denied. I have set up the share as owned by a local (non-LDAP) user and it still fails, I have enabled guest access in both CIFS general and the share specifically but connecting as guest or a user fails. I have increased logging to ""full"" and even ""debug"" but see nothing in the logs upon each failed attempt (checking log.smbd, log.nmdb, and messages.) I'm not sure what to do now, I assume that there is some issue with the samba config, but I don't know what else to alter.",MotoLogic Active Tickets,1434,Preservation of reporting data needs to be made more robust,Backend,8.3.0-RELEASE-p1,,defect,,new,2012-03-30T03:37:10Z,2012-12-27T16:03:19Z,"Hi guys, I'm running 8.2 beta2 and earlier tonight my filer hung on shutdown...I got the ""syncing"" messages, but the system was stuck at that point & I had to power cycle it. When it came back up I once again had fresh, empty reporting data. I know there was a fix to change the ordering of things on shutdown to make sure the save_rdds.sh script runs properly, but I feel like there needs to be more done to preserve this data. I think the data should be saved off to stable storage, maybe on a user-selectable schedule, as well as optionally being exported along with the config when the config is saved. Zip all the data up into a tarball to make it easy to deal with between installs the way pfsense does it (I have data going back a year+ on my pfsense box despite a bunch of reinstall\restores). Put in a check when the system boots for the most recent rrd archive and load that....starting fresh with new rrd files should be the last resort. -Will",survive Active Tickets,1436,"New member disk not showing up in ""Create Volume"" screen",Backend,8.0.4-RELEASE,,defect,,new,2012-03-30T13:24:09Z,2012-05-06T19:48:13Z,"When inserting two brand new, blank WD 2TB Caviar Green disks, neither showed up in the ""Member Disks"" area of the ""Create Volume"" dialogue. The disks did show up in the ""Disk Replacement"" Dialogue from the ""View Disks"" pane of any previously created Volume. The disks were attached via SATA to a RocketRaid 2300 4 port PCI-E to SATA adapter. Two ports were used for these disks. The other two ports were in use and operational. One of the other ports on this card happens to connect to an (almost) identical disk bought a few days earlier (another WD 2tb caviar green, but possibly from a different batch). This is the output of ""camcontrol devlist"", which (I think) shows that this disk isn't there. at scbus0 target 0 lun 0 (ada0,pass0) at scbus0 target 1 lun 0 (ada1,pass1) at scbus0 target 2 lun 0 (ada2,pass2) at scbus0 target 3 lun 0 (ada3,pass3) at scbus0 target 15 lun 0 (pass4,pmp0) at scbus3 target 0 lun 0 (ada4,pass5) at scbus4 target 0 lun 0 (ada5,pass6) at scbus5 target 0 lun 0 (da0,pass7) at scbus5 target 1 lun 0 (da1,pass8) at scbus5 target 2 lun 0 (da2,pass9) at scbus6 target 0 lun 0 (da3,pass10) At first I figured that this may just be that the partition table hadn't been initialised, so I plugged it into a linux machine to create an MBR table with fdisk (but no partitions). This didn't work - the disk still failed to show. Next I tried putting a single id 83 (linux) partition on the disk (for no particular reason; the partition wasn't formatted). The disk now showed up in the ""Create Volume"" dialogue. A little after this I decided to delete the volume to add it to an existing pool, so I exported the volume and ticked to ""Mark the disk as new"". When the process was completed, the disk again failed to show in the ""Create Volume"" dialogue (even after reboot). It was the second time of the disk not showing up that lead me to open the ticket to help out this great project. I can post any other information asked for; just tell me the commands to insert as I haven't been working with freenas long. I know that all I will have to do to fix this is to plug the drive into a different machine and make a single partition on it, but that isn't an ideal fix.",kimbecause Active Tickets,1455,Replication to multiple targets always end up breaking,Backend,8.2.0-BETA2,,defect,,new,2012-04-10T10:24:31Z,2012-04-20T18:53:27Z,"I have a use case where I would like to backup(replicate) a dataset to 2 different machines. However, given the tracking mechanism of snapshots for replication, I have discovered a flaw with replication to multiple targets. basically, a source snapshot can either carry one of the 3 states: freenas:state = - (already replicated) freenas:state = LATEST (Latest replicated snapshot) freenas:state = NEW (Not yet replicated) When the replication demon kicks in, it will send an incremental stream from latest to new. This ""global"" state works fine if there is only 1 replication going on. If there are two (or more) replications tasks though, it ""kind"" of works in the sense that ''if'' both targets are synchronized, the ""send"" message will work for both targets. However, if one of the target machines ever go down, or if any of the replication fails, then that machine will be left behind in terms of snapshots, and the replication task will be broken. At this point, the snapshots must be sent by hand to re-synchronize the target machines. In the the long term, it is not a matter of ""if"" the replication will break, but ""when"". To fix this problem, I would recommend a separate property per snapshot eg: {{{ #!div style=""font-size: 80%"" Code highlighting: {{{#!sh zfs list -t snapshot -o name,freenas:state:rep1,freenas:state:rep2 Volume Name freenas:state:rep1 freenas:state:rep2 Volume@1 - - Volume@2 - LATEST Volume@3 LATEST NEW Volume@4 NEW NEW }}} }}} In this scenario, for example, rep1 is ""on time"", and will soon replicate the new snapshot @4. Rep 2 is a actually a new replication job to a new machine, and the replication job is still catching up. ",monarchdodra Active Tickets,1465,Moving CSV to other clusternode hangs in 8.2.1-ALPHA-r10639-x64 ISCSI,Backend,8.2.0-BETA2,,defect,,new,2012-04-18T07:19:27Z,2012-04-18T07:20:01Z,"Hi, i think it's an old bug. my CLuster is stable and Hyper-V Live migration works fine. But when i try to move CSV to an other clusternode the CSV comes not online again. I had to remove the drive vom Clusterstorages bring it online and make it again to a csv. the same when one node goes down which owned a CSV. kind regards HSS",mindmaster Active Tickets,1476,alert is green (healthy) even if smart reports problems to syslog,Backend,8.2.0-BETA2,,defect,,new,2012-04-20T21:33:20Z,2012-04-21T04:51:10Z,"The gui system reports itself healthy, no alerts, even though the syslog has notice about a disk failure: Apr 20 21:41:37 nas smartd[1830]: Device: /dev/ada1, 742 Currently unreadable (pending) sectors Apr 20 21:41:37 nas smartd[1830]: Device: /dev/ada1, 11 Offline uncorrectable sectors Apr 20 22:11:37 nas smartd[1830]: Device: /dev/ada1, 742 Currently unreadable (pending) sectors Apr 20 22:11:37 nas smartd[1830]: Device: /dev/ada1, 11 Offline uncorrectable sectors And the same can be seen from smartctl. I noticed this by accident while looking syslog from something totally else. Otherwise I would not have noticed any of the disk failure. I don't know if it sends mails or not, the mail setup on my nas doesn't work atm for some reason. Version is actually 64bit 8.2 Beta3, but there isn't such version in the menu of trac yet, thus wrong version in report. ",ikke Active Tickets,1486,Increase MAXLOGNAME to support longer usernames,Backend,8.0.4-RELEASE,,defect,,new,2012-04-24T01:14:16Z,2012-04-24T01:14:16Z,"When using Active Directory, our domain + separator takes up 10 characters. That means that only the shortest of usernames can log in via ssh. Can MAXLOGNAME be increased to something bigger (eg 64) so that longer logins can be used? References: http://bsdbased.com/2009/11/09/long-usernames-in-freebsd http://answerpot.com/showthread.php?3219475-kern%2F162976%3A+cron+fails+unnecessarily+via+setlogin%282%29+with+sufficiently+long+usernames http://lists.freebsd.org/pipermail/freebsd-hackers/2003-June/001205.html",dmuir Active Tickets,1502,S.M.A.R.T Test for replaced drive get lost,Backend,8.0.4-RELEASE,,defect,,new,2012-05-02T18:08:48Z,2012-05-02T18:08:48Z,"I just noticed that the S.M.A.R.T Tests of a recently replaced hard disk drive were not migrated to the new drive. It would be nice if S.M.A.R.T Tests will be preserved.",QZmn7igVMc Active Tickets,1520,Make iSCSI targets SCSI 3 PGR compliant,Backend,8.0.4-RELEASE,,defect,,new,2012-05-12T16:37:54Z,2013-01-04T19:56:04Z,"In a cluster environment, if you register a key on a FreeNAS 8.0.4 iSCSI target disk from client 1, and another key from client 2, then unregister the key from client 1, the key from client 2 also gets removed!",Hedrik Active Tickets,1531,"Maybe I'm just off base, but this seems like performance suckage.",FreeBSD,8.0.4-RELEASE-p2,,defect,,reopened,2012-05-19T17:02:36Z,2013-01-11T20:57:44Z,"I've been retiring some of our old storage servers, and upgrading the hardware. I had been running FreeNAS on some of these, and had always been annoyed because they would go catatonic for short periods of time during heavy write activity; I had never looked into this extensively. I knew that ZFS was a little piggy on CPU and these were old Opteron 240EE's with 8GB, so I had been writing it off as insufficient resources to make ZFS happy. This has been problematic. NFS clients don't like their servers going catatonic. iSCSI initiators don't like their servers going catatonic. etc. But I pretty much expected that modern hardware would solve the problem. I was horrified at the following, which represents an order-of-magnitude increase in suckageness. Comments inline. Console setup ------------- 1) Configure Network Interfaces 2) Configure Link Aggregation 3) Create VLAN Interface 4) Configure Default Route 5) Configure Static Routes 6) Configure DNS 7) Reset WebGUI login credentials 8) Reset to factory defaults 9) Shell 10) Reboot 11) Shutdown You may try the following URLs to access the web user interface: http://10.255.1.233/ 9 %df -k Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/ufs/FreeNASs1a 948903 387934 485057 44% / devfs 1 1 0 100% /dev /dev/md0 4663 1844 2446 43% /etc /dev/md1 823 3 755 0% /mnt /dev/md2 152791 15126 125442 11% /var /dev/ufs/FreeNASs4 20263 350 18292 2% /data storage0 760838283 12902098 747936184 2% /mnt/storage0 %zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT storage0 1.45T 24.7G 1.42T 1% ONLINE /mnt %zpool status pool: storage0 state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM storage0 ONLINE 0 0 0 raidz2 ONLINE 0 0 0 ada0p2 ONLINE 0 0 0 ada1p2 ONLINE 0 0 0 ada2p2 ONLINE 0 0 0 ada3p2 ONLINE 0 0 0 errors: No known data errors %cd /mnt/storage0 %ls -al total 25804137 drwxr-xr-x 2 root wheel 3 May 19 16:23 . drwxr-xr-x 5 root wheel 512 May 19 16:19 .. -rw-r--r-- 1 root wheel 13235126272 May 19 16:27 file %dd if=/dev/zero of=file bs=1048576 load: 0.02 cmd: dd 3216 [running] 1.09r 0.00u 0.00s 9% 964k **No response from dd to that !^T, I suspect due to it still being in the file-opening stage** load: 0.10 cmd: dd 3216 [running] 3.87r 0.00u 3.71s 32% 2020k 7552+0 records in 7551+0 records out 7917797376 bytes transferred in 2.327832 secs (3401361194 bytes/sec) load: 0.17 cmd: dd 3216 [tx->tx_quiesce_more_cv)] 7.20r 0.01u 4.76s 28% 2068k 12036+0 records in 12035+0 records out 12619612160 bytes transferred in 5.658315 secs (2230277345 bytes/sec) **Now at this point, 2230MB/sec? Sounds great but these drives cap out at 70MB/sec each.** load: 0.17 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 10.49r 0.01u 4.87s 21% 2068k **And now the system's catatonic. Note 10.49r** load: 0.15 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 12.90r 0.01u 4.87s 16% 2068k load: 0.15 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 14.93r 0.01u 4.87s 13% 2068k load: 0.14 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 17.30r 0.01u 4.87s 11% 2068k load: 0.14 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 19.91r 0.01u 4.87s 8% 2068k load: 0.13 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 22.14r 0.01u 4.87s 7% 2068k load: 0.13 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 26.71r 0.01u 4.87s 4% 2068k load: 0.12 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 32.93r 0.01u 4.87s 2% 2068k load: 0.10 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 39.79r 0.01u 4.87s 1% 2068k load: 0.09 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 46.72r 0.01u 4.87s 0% 2068k load: 0.08 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 52.39r 0.01u 4.87s 0% 2068k load: 0.07 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 58.47r 0.01u 4.87s 0% 2068k load: 0.50 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 71.57r 0.01u 4.87s 0% 2068k load: 0.42 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 82.68r 0.01u 4.87s 0% 2068k load: 0.33 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 96.48r 0.01u 4.87s 0% 2068k load: 0.26 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 112.70r 0.01u 4.87s 0% 2068k load: 0.31 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 131.05r 0.01u 4.87s 0% 2068k load: 0.20 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 159.51r 0.01u 4.87s 0% 2068k load: 0.19 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 179.73r 0.01u 4.87s 0% 2068k **Notice 179.73r, minus the previous 10.49r, means the system went out to lunch for 169 seconds** 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898293 secs (71349309 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898349 secs (71349286 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898357 secs (71349283 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898366 secs (71349280 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898373 secs (71349277 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898380 secs (71349274 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898386 secs (71349272 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898393 secs (71349269 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898400 secs (71349266 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898407 secs (71349263 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898414 secs (71349261 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898422 secs (71349257 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898429 secs (71349255 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898437 secs (71349251 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898445 secs (71349248 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898453 secs (71349245 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898459 secs (71349243 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 179.898466 secs (71349240 bytes/sec) 12242+0 records in 12241+0 records out 12835618816 bytes transferred in 181.944199 secs (70547008 bytes/sec) **Oh and there's all the stacked responses to my !^T's** load: 0.15 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 198.68r 0.03u 7.45s 8% 2068k load: 0.28 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 221.59r 0.03u 7.45s 0% 2068k load: 0.20 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 241.54r 0.03u 7.45s 0% 2068k load: 0.44 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 271.23r 0.03u 7.45s 0% 2068k 21849+0 records in 21848+0 records out 22909288448 bytes transferred in 294.758276 secs (77722291 bytes/sec) 21849+0 records in 21848+0 records out 22909288448 bytes transferred in 294.758329 secs (77722277 bytes/sec) 21849+0 records in 21848+0 records out 22909288448 bytes transferred in 294.758336 secs (77722275 bytes/sec) 21849+0 records in 21848+0 records out 22909288448 bytes transferred in 294.758342 secs (77722273 bytes/sec) load: 0.39 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 301.10r 0.03u 8.25s 4% 2068k load: 0.33 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 313.96r 0.03u 8.25s 0% 2068k 25932+0 records in 25931+0 records out 27190624256 bytes transferred in 324.295019 secs (83845334 bytes/sec) 25932+0 records in 25931+0 records out 27190624256 bytes transferred in 324.295065 secs (83845322 bytes/sec) !^C **Ok, enough of this, stop now** load: 0.24 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 332.80r 0.03u 9.87s 9% 2068k **Guess not** load: 0.22 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 339.76r 0.03u 9.87s 5% 2068k load: 0.17 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 354.30r 0.03u 9.87s 0% 2068k load: 0.13 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 366.89r 0.03u 9.87s 0% 2068k load: 0.22 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 390.92r 0.03u 9.87s 0% 2068k load: 0.23 cmd: dd 3216 [tx->tx_quiesce_done_cv)] 438.32r 0.03u 9.87s 0% 2068k 32334+0 records in 32333+0 records out 33903607808 bytes transferred in 478.452024 secs (70861040 bytes/sec) 32334+0 records in 32333+0 records out 33903607808 bytes transferred in 478.452074 secs (70861032 bytes/sec) 32334+0 records in 32333+0 records out 33903607808 bytes transferred in 478.452082 secs (70861031 bytes/sec) 32334+0 records in 32333+0 records out 33903607808 bytes transferred in 478.452090 secs (70861030 bytes/sec) 32334+0 records in 32333+0 records out 33903607808 bytes transferred in 478.452098 secs (70861029 bytes/sec) 32334+0 records in 32333+0 records out 33903607808 bytes transferred in 478.452105 secs (70861028 bytes/sec) 32334+0 records in 32333+0 records out 33903607808 bytes transferred in 478.452121 secs (70861025 bytes/sec) **Well, about 150 seconds after !^C, it actually stops** % So this kind of thing was completely melting the previous platform's 2005-vintage Opteron, but the new platform is resource-rich and I'm able to look at what's going on. In particular I can log in via ssh and get an interactive shell that is responsive as long as I don't touch the ZFS filesystem... So I look at it, and of course, all that time in tx->tx_quiesce_done_cv is time that the system is writing to the disks at about 30MB/sec each. Ok, so vfs.zfs.txg.timeout=""5"" ... that helped somewhat on the Opterons. It looks like it makes it ""better"": %dd if=/dev/zero of=file bs=1048576 load: 0.43 cmd: dd 2718 [zio->io_cv)] 2.93r 0.00u 0.07s 0% 964k load: 0.43 cmd: dd 2718 [zio->io_cv)] 4.84r 0.00u 0.11s 0% 964k load: 0.39 cmd: dd 2718 [zio->io_cv)] 6.81r 0.00u 0.16s 0% 964k load: 0.39 cmd: dd 2718 [zio->io_cv)] 9.07r 0.00u 0.21s 0% 964k load: 0.36 cmd: dd 2718 [running] 11.59r 0.00u 0.28s 1% 2020k 28+0 records in 27+0 records out 28311552 bytes transferred in 0.005912 secs (4788775086 bytes/sec) load: 0.36 cmd: dd 2718 [tx->tx_quiesce_done_cv)] 14.35r 0.00u 0.35s 1% 2068k 337+0 records in 336+0 records out 352321536 bytes transferred in 3.950970 secs (89173429 bytes/sec) load: 0.28 cmd: dd 2718 [tx->tx_quiesce_done_cv)] 27.17r 0.00u 0.75s 1% 2068k 1410+0 records in 1409+0 records out 1477443584 bytes transferred in 16.660683 secs (88678453 bytes/sec) load: 0.28 cmd: dd 2718 [running] 28.30r 0.00u 0.75s 2% 2068k 1524+0 records in 1523+0 records out 1596981248 bytes transferred in 16.715253 secs (95540358 bytes/sec) load: 0.26 cmd: dd 2718 [tx->tx_quiesce_done_cv)] 29.94r 0.00u 0.86s 2% 2068k load: 0.26 cmd: dd 2718 [tx->tx_quiesce_done_cv)] 31.03r 0.00u 0.86s 1% 2068k load: 0.26 cmd: dd 2718 [tx->tx_quiesce_done_cv)] 32.50r 0.00u 0.86s 1% 2068k load: 0.26 cmd: dd 2718 [tx->tx_quiesce_done_cv)] 33.98r 0.00u 0.86s 1% 2068k load: 0.24 cmd: dd 2718 [tx->tx_quiesce_done_cv)] 35.63r 0.00u 0.86s 1% 2068k load: 0.24 cmd: dd 2718 [tx->tx_quiesce_done_cv)] 37.25r 0.00u 0.86s 0% 2068k load: 0.24 cmd: dd 2718 [tx->tx_quiesce_done_cv)] 38.81r 0.00u 0.86s 0% 2068k load: 0.22 cmd: dd 2718 [tx->tx_quiesce_done_cv)] 40.38r 0.00u 0.86s 0% 2068k 1698+0 records in 1697+0 records out 1779433472 bytes transferred in 28.920370 secs (61528725 bytes/sec) 1698+0 records in 1697+0 records out 1779433472 bytes transferred in 28.920423 secs (61528611 bytes/sec) 1698+0 records in 1697+0 records out 1779433472 bytes transferred in 28.920431 secs (61528595 bytes/sec) 1698+0 records in 1697+0 records out 1779433472 bytes transferred in 28.920438 secs (61528580 bytes/sec) 1698+0 records in 1697+0 records out 1779433472 bytes transferred in 28.920445 secs (61528565 bytes/sec) 1698+0 records in 1697+0 records out 1779433472 bytes transferred in 28.920453 secs (61528548 bytes/sec) 1698+0 records in 1697+0 records out 1779433472 bytes transferred in 28.920460 secs (61528533 bytes/sec) 1698+0 records in 1697+0 records out 1779433472 bytes transferred in 28.920468 secs (61528516 bytes/sec) but even there, going catatonic for 10 seconds at a time, just not cool. A NAS product shouldn't come configured so that it goes catatonic in its default configuration, and that's my bug report, and hopefully you can see the justification. ",jgreco Active Tickets,1553,panic writing to ext2fs volume,FreeBSD,8.0.2-RELEASE,,defect,,new,2012-05-31T21:03:55Z,2012-07-31T12:40:40Z,"I am consistently receiving a panic if I try to back-up 1TB+ of data from a ZFS mirror to a locally-mounted ext2fs volume via USB, eSATA and SATA interfaces. FreeBSD 8.2 will give the same console warnings but not the panic. The panic itself appears to be this closed FreeBSD ticket: kern/129098: [panic] vinvalbuf: dirty bufs on 6-STABLE http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/129098 Console output and panic when trying via USB: g_vfs_done():da1s1[WRITE(offset=-1099510046720, length=131072)]error = 5 May 20 22:46:52 freenas kernel: g_vfs_done():da1s1[WRITE(offset=-1099509915648, length=131072)]error = 5 May 20 22:46:52 freenas kernel: g_vfs_done():da1s1[WRITE(offset=-1099509694464, length=4096)]error = 5 May 20 22:46:52 freenas kernel: g_vfs_done():da1s1[WRITE(offset=-1099509694464, length=4096)]error = 5 fsync: giving up on dirty ... panic: vinvalbuf: dirty bufs cpuid = 1 Uptime: ...",dexter Active Tickets,1559,Snapshots have wrong timestamp in Windows,Backend,8.3.0-RC1,,defect,,new,2012-06-02T03:04:56Z,2013-03-04T06:05:59Z,"When viewing zfs snapshot folders with in windows previous versions tab the time for all the folders is the same and is total wrong to the system time or the time when the snapshot was taken. (see attached screenshots) Opening any of the snapshot folders you can see that the correct date and time is being displayed in the address bar and is reflected in the folder name as to when the snapshot was taken (see attached screenshots) My freenas system time is set to GMT+10 Sydney Australia and so is my windows box. The strange this is I have no idea where this incorrect folder time in the previous version tab is coming from and it changes every time I restart the CIFS services with no pattern that I can see. I have also noticed that when the freenas autosnap script is taking the snapshot that the time reported in the console is way out from the system time as well. (see attached screenshots) I have attempted adding the following Auxiliary Parameters to my share's smb.conf vfs objects = shadow_copy2 wide links = yes shadow: snapdir = .zfs/snapshot shadow: sort = desc shadow: localtime = yes shadow: format = auto-%Y%m%d.%H%M-1d However the folder time is still displayed in correctly in the windows previous version tab. ",lordvorta Active Tickets,1696,CIFS share directory is not created,GUI,8.2.0-RELEASE-p1,,defect,william,accepted,2012-07-31T23:49:44Z,2012-12-27T15:58:52Z,If you try to share directory via CIFS and type nonexistent directory because you want to share volume subdirectory then your typed in directory is not created by GUI and sharing does not work.,hsn Active Tickets,1708,Unable to save permission changes,Backend,8.3.0-RELEASE-p1,,defect,,new,2012-08-06T09:55:23Z,2013-01-16T00:48:58Z,"Hi, I have setup a FreeNAS server running 8.2.0 and have got it to join my AD domain (Win 2003). When logged on as an administrator I can create a folder in the Admin share i created but I am unable to change the permissions of any folder or file I create. It just says: ""Unable to save permission changes on Shared"" ""The Parameter is incorrect."" I have searched online and can see lots of people asking this question but no answers that actually work. How can I get this working? Thanks",dataday Active Tickets,1750,FreeNAS-8.3.1-ALPHA: root readonly remount takes minutes,FreeBSD,8.3.0-BETA1,,defect,,new,2012-08-24T09:04:30Z,2012-08-28T11:20:51Z,"I just installed FreeNAS-8.3.1-ALPHA-r12166-x64. For testing and installing patches I must remount root writeable. The way back to remount root readonly takes a very long time (from 3 until 5 minutes) One guy already opens a thread in freebsd.org: [http://forums.freebsd.org/showthread.php?t=33021] Is this a known issue? Are there any workarounds? I did not test 8.3.0-BETA1.",willytenner Active Tickets,1777,"Unable to configure static route ""through physical interface"" instead of ""to next-hop""",GUI,8.2.0-RELEASE-p1,,defect,,new,2012-09-05T21:45:21Z,2012-09-07T19:56:51Z,"Hello, I run freenas on a VM on a dedicated server hosted by OVH, in bridge mode. That means that its IP is routed as a /32 and that its default gateway is on a different subnet and must itself be routed as a /32 through the physical interface. I could make it work using the console thanks to the following commands: route add -host -iface re0 route add default Unfortunately there is no way to make it persistent. There seem to be no clean way to make persistent change to the configuration through CLI. The static route configuration in the WebUI is too simplistic and does not allow specifying an interface instead of an IP (-iface). As it is, I will loose network connectivity the next time I will reboot the VM.",detunizedgravity Active Tickets,1822,"Unable to select ""inherit permissions"" independently from ""inherit owner"" (CIFS)",Backend,8.2.0-RELEASE,,defect,,new,2012-10-02T19:23:48Z,2012-10-02T19:24:27Z,"I am sharing my datasets using CIFS. I would like subdirectories created under a datashare to inherit the permissions of the parent dataset/directory so I selected ""inherit permissions"" in the share settings. However, in my testing, user-created directories are not inheriting the parent permissions UNLESS ""inherit owner"" is also selected.",sockbot Active Tickets,1830,ZFS-iSCSI - very low disk write performance w/ESXi,Backend,8.3.0-BETA3,,defect,,new,2012-10-08T07:30:01Z,2013-02-13T06:18:14Z,"Hello, There seems to be a change between FN 8.2 release and the current 8.3 Betas/RC1 that causes very low write performance on the 8.3 series (compared to the 8.2 release) on the same exact hardware/configuration. Specifically, the Random Write 4KB QD=1 and QD=32 tests using CrystalDiskMark. Ex: {{{ FN 8.3 RC1 x64 Sequential Read : 106.573 MB/s Sequential Write : 96.518 MB/s Random Read 512KB : 100.094 MB/s Random Write 512KB : 97.445 MB/s Random Read 4KB (QD=1) : 10.966 MB/s [ 2677.3 IOPS] Random Write 4KB (QD=1) : 4.692 MB/s [ 1145.5 IOPS] Random Read 4KB (QD=32) : 108.178 MB/s [ 26410.8 IOPS] Random Write 4KB (QD=32) : 5.159 MB/s [ 1259.5 IOPS] Test : 1000 MB [G: 2.8% (33.9/1226.0 MB)] (x5) Date : 2012/10/07 11:35:56 OS : Windows 7 SP1 [6.1 Build 7601] (x64) FreeNAS 8.3 RC1 x64- 1x SSD ZFS - iSCSI > ESXi 5.1 - Win7 VM }}} vs {{{ FN 8.2 Release p1 x64 Sequential Read : 106.174 MB/s Sequential Write : 109.102 MB/s Random Read 512KB : 98.710 MB/s Random Write 512KB : 99.570 MB/s Random Read 4KB (QD=1) : 10.472 MB/s [ 2556.6 IOPS] Random Write 4KB (QD=1) : 10.921 MB/s [ 2666.2 IOPS] Random Read 4KB (QD=32) : 113.317 MB/s [ 27665.2 IOPS] Random Write 4KB (QD=32) : 59.728 MB/s [ 14582.0 IOPS] Test : 1000 MB [E: 1.0% (53.5/5117.0 MB)] (x5) Date : 2012/10/07 23:38:41 OS : Windows 7 SP1 [6.1 Build 7601] (x64) FreeNAS 8.2 Release P1 x64 - 1x SSD ZFS - iSCSI > ESXi 5.1 - Win7 VM }}} The testing OS is Win7 64bit, running as a VM inside an ESXi 5.1 server, connected directly to the FN server via GigE. The FN server is configured with 1x 120GB SSD drive, formatted as ZFS. Then iSCSI, with a file extent inside the SSD. One thing I noted is that on FN 8.3, using stat while the test is running, the drive would not always get to 100% busy. But, under FN 8.2, the drive would frequently hit 100% busy whenever it was being used. Here is some info on the hardware: NAS server: Supermicro 12 bay chassis, X7DBE MB, 20GB ECC RAM, 2x Xeon E5310, 2x intel based NIC ports, 2x Broadcom based NIC ports. ESXi 5.1 server: Supermicro 1u chassis, X8DTU-F MB, 24GB ECC RAM, 2x Xeon L5520, 2x intel based NIC ports, 2x Broadcom based NIC ports. I used 2x USB sticks, one with FN 8.2 release p1, and one with FN 8.3 RC1. Before each test, the SSD was wiped and reformatted for ZFS (pool v15 on FN8.3 and Pool v28 on FN 8.3). I have switched between the USB sticks many times, and the test results are always pretty much the same. Thank you.",got2go Active Tickets,1847,"System dies, no error messages",Backend,8.3.0-RC1,,defect,,new,2012-10-18T16:25:49Z,2013-01-14T10:40:56Z,"The system is running ok and suddenly it's just dead. No error messages, no console output. From the beginning I thought it had something to do when I did ""heavy"" access from my laptop (linux) but it seems to die even if there is no nfs-access as well. It seems to take somewhere between 0,5h - 1h, (sometimes it can stay up to say 12h). 8.3.0-RC1, x64 (r12617), (NFS, CIFS, rsync, smart, ssh enabled) AMD Athlon II X3 415e, 8 GB. ASUS motherboard. Promise SATA300 TX4. 6 disks in raid-z2. 2 datasets (Samsung F4) 3 disks, separate volumes. (various) 3 clients (usually nfs). Only message from gui is the alerts telling zfs-pool is not updated. The system was created with Freenas v8 (about 1,5 year ago) and has been updated to 8.0.1, 8.0.2, 8.0.3 and 8.0.4. All worked find all the time. Then updated to 8.2. Kernel panics... after reading about many other having this problem, I upgraded to 8.3.0-beta2. Worked fine for some weeks. After starting to halt I was going to update to beta 3 but RC1 was just released (not announced). No change from beta2. Strange halts could be hardware faults. I ran memory tests for hours, no problems found. I have check all cables, cards fully inserted, etc. Updated BIOS. I booted on RC1-CD and reinstalled/upgraded again (in case RC1 was updated when it was actually announced). The usb memory stick is a SANDISK Cruzer Blade 4GB. I bought a new one and did a fresh install (imported old db). The new one is an ADATA Classic C802 4GB. No change, system freezed up. ",audix Active Tickets,1849,"Physical Drive order swapped, but GUI all over the place",Backend,8.2.0-RELEASE-p1,,defect,,new,2012-10-20T11:27:45Z,2012-10-20T20:18:25Z,"GUI View Disks and Volume Status displaying incorrect device names for drives after swapping drive bays. Originally ada0 and ada1 were used for a zfs stripe (raid0) I moved 2 disks from bays 1 and 2 to 4 and 3 respectively and added 2 new smaller drives. After the relocation, setup as a ufs mirror on ada0 and ada1 (in bays 1 and 2 - although I cannot confirm what device names were used shown at the time). I noticed now that when I look at the gui to check the volume status of the zfs stripe, I am shown the correct device ids, but when I click on edit to see the details, I am shown the details of the 500GB disks. I have no idea what changing smart statuses etc would result in - which device would be changed etc ? It appears that the gui is not using realtime information or updating it on boot when things are changed. This causes confusion and possible issues of modifying and/or destroying wrong drives etc. I found a similar bug reported 18months ago, but that was marked as resolved. Included some screenshots of conflicting data. gpart shows ada2 is 1TB drive, but gui shows it as a 500GB drive when editing drive shown in strip layout. Volume screen shows incorrect data for drive names.",enly1 Active Tickets,1858,Crash bug on absent USB CDROM on reboot,FreeBSD,8.3.0-RC1,,defect,,new,2012-10-23T17:04:47Z,2012-10-23T18:29:22Z,"Running 8.3RC, if you install FreeNAS from a removable (USB) CDROM, and then disconnect said CDROM from the system while off prior to a cold boot, the system will crash mid-boot. Simply reconnecting the CDROM and rebooting resolves the crash bug. ",extrapilot Active Tickets,1862,Panic on boot of fresh 8.3.0-RC1-x64 USB install with Intel S1200BTL,FreeBSD,8.3.0-RC1,,defect,,new,2012-10-24T15:47:32Z,2012-10-24T16:11:42Z,"With installation of 8.3.0-RC1-x64 on any USB stick I have tried, I encounter the following panic on boot: {{{ Trying to mount root from ufs:/dev/ufs/FreeNASs1a Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x308 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80578e0e stack pointer = 0x28:0xffffff800007c840 frame pointer = 0x28:0xffffff800007c860 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1 (kernel) [thread pid 1 tid 100002 ] Stopped at _mtx_lock_sleep+0x4e: movl 0x398(%rcx),%esi db> tr Tracing pid 1 tid 100002 td 0xffffff00064c78c0 _mtx_lock_sleep() at _mtx_lock_sleep+0x4e bufobj_invalbuf() at bufobj_invalbuf+0x2ca vfs_mountroot_try() at vfs_mountroot_try+0x396 vfs_mountroot() at vfs_mountroot+0x3d1 start_init() at start_init+0x4c fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff800007cd00, rbp = 0 --- }}} This is with standard install from ISO or with a direct dd of the .img. This happens with multiple brands of USB stick. 8.2.0 works fine on the same sticks. 8.3.0-RC1 works fine if installed on a standard hard drive or SSD. I have tried various settings in BIOS to no avail. (USB compatibility settings, SATA mode, disabling all MP features and booting single core, etc) This crash only happens with 8.3.0 series installed to USB. I will try to reproduce this on vanilla FreeBSD and submit the bug there as well. (Related forum post: http://forums.freenas.org/showthread.php?9471-Panic-on-boot-of-fresh-8-3-0-RC1-x64-USB-install-with-Intel-S1200BTL)",pauldoom Active Tickets,1875,ZFS Replication - does not start unless there is a snapshot task,Backend,8.3.0-BETA3,,defect,,new,2012-10-28T16:21:11Z,2012-10-28T16:21:11Z,"The ZFS Replication schedule will not apply unless there is a snapshot task that also applies. If the snapshot replciation fails for any reason, the replication will not restart even if the automated replication is in the allowed time frame for replication. Autorepl.py is called at the end of autosnap.py, and autosnap.py is set as a cron task to run once per minute. At line 167 in autosnap.py there is logic to check for a snapshot task and if none is found the script exits without kicking off any replication. Would it be possible or easier to relocate starting of autorepl.py into a cron task rather than adjusting logic in autosnap.py?",maglaubig Active Tickets,1881,Booting 8.3.0+ on DH55tc + i3,Backend,8.3.0-RELEASE,,defect,,new,2012-10-31T16:11:10Z,2012-11-01T19:32:34Z,"I'm creating this ticket as i didnt get any response from the forum. (Hope i'm not the only one with this issue) Problem: Cannot ""warm"" reboot Freenas 8.3.0 Release x64 and above with: - WebGUI - shutdown -r now - reboot Starting works only if i cleanly shutdown the system prior or removing the power cord for 5 min (after trying a reboot). Things i tried, which result all in the same error and system freeze: - GUI upgrade from a fully working 8.2.0 x64 Release -> Error - Fresh install 8.3.0 Release x64 -> load config from WebGUI -> Error - Fresh install 8.3.0 Release x64 -> Reboot -> Error - Cold Boot with removed HDD Caddys -> works -> Reboot -> Error - Cold Boot with removed Sata Cables -> works -> Reboot -> Error - Tried FreeNAS-8.3.1-ALPHA-r12712-x64.img -> boot ok -> Reboot -> Error - loaded BIOS default - disabled/enabled mostly all options (there arent that many, like a notebook BIOS) - Testing 2 other USB Sticks -> Error {{{ atapci0: [ITHREAD] ata2: at channel 0 on atapci0 ata2: [ITHREAD] ata3: at channel 1 on atapci0 ata3: [ITHREAD] uart2: Reserved 0x0 bytes for rid 0x10 type 4 at 0xf148 }}} (Last line is from booting with verbose logging) Info: Prepared the USB stick from my Fedora Desktop with the following command: {{{ xzcat Downloads/FreeNAS-8.3.0-RELEASE-x64.img.xz | sudo dd of=/dev/sdc bs=64k }}} Hardware: {{{ Intel DH55TC (Mainboard 6x sata onboard, and latest BIOS) Intel Core i3 530 2.93GHz 4x WD20EARS 2x WD20EARX 2x 3in3 Xigmatec HDD Cages }}} Does this mean 8.3 Release doesn't support rebooting o_O""? Rebooting FreeBSD 9.0 from USB (memstick) and installation ( on2.5"" hdd in hotswap bay) both work. ",yell Active Tickets,1882,Stopping AFP service leaves cnid_dbd process running,Backend,8.3.0-RELEASE,,defect,,new,2012-10-31T17:23:50Z,2012-10-31T17:23:50Z,"I have individual zfs filesystem (datasets, in the UI lingo I think...) for the volumes I share out to my macs. When I want to destroy one I stop the service in the Control Services UI then try to destroy it via the UI. It doesn't work because it's busy. Trying to destroy it from the command line has a similar result. Fstat shows that there are still cnid_dbd processes running in those/that filesystem. Killing the cnid_dbd process allows the filesystem to be destroyed. I believe that cnid_dbd is part of the AFP suite and should be stopped when AFP is disabled. There is a similar problem if you use the Sharing menu to delete a shared volume without stopping the entire service.",hartzell Active Tickets,1887,cifs not talking to ldap auth,Backend,8.3.0-RELEASE,,defect,,new,2012-11-01T18:17:13Z,2013-03-08T18:21:01Z,"Hi, FreeNAS-8.3.0-RELEASE-x64 (r12701M), upgraded from -beta and -rc. I'm trying to make CIFS authenticate against LDAP. The machine is successfully talking to the LDAP server, and freenas-debug -c shows the LDAP users and groups. When I browse to the machine, log.smbd shows: [2012/11/01 14:07:53.072280, 0] passdb/secrets.c:350(fetch_ldap_pw) fetch_ldap_pw: neither ldap secret retrieved! [2012/11/01 14:07:53.072326, 0] lib/smbldap.c:1180(smbldap_connect_system) ldap_connect_system: Failed to retrieve password from secrets.tdb [2012/11/01 14:07:53.072442, 1] lib/smbldap.c:1409(another_ldap_try) Connection to LDAP server failed for the 1 try! [2012/11/01 14:07:54.110683, 0] passdb/secrets.c:350(fetch_ldap_pw) fetch_ldap_pw: neither ldap secret retrieved! [2012/11/01 14:07:54.110703, 0] lib/smbldap.c:1180(smbldap_connect_system) ldap_connect_system: Failed to retrieve password from secrets.tdb [2012/11/01 14:07:54.110786, 1] lib/smbldap.c:1409(another_ldap_try) Connection to LDAP server failed for the 2 try! ... It appears that the LDAP configuration isn't plugged into SMB somehow? Here are my config files, with IPs and domains changed. /etc/local/ldap.conf is: host doorbell.example.com base dc=example,dc=com rootbinddn pam_password clear nss_override_attribute_value loginShell /bin/sh nss_base_passwd ou=people,dc=example,dc=com nss_base_group ou=groups,dc=example,dc=com ssl start_tls tls_cacertfile /usr/local/etc/certs/cacert.crt ldap_version 3 timelimit 30 bind_timelimit 30 bind_policy soft pam_ldap_attribute uid pam_groupdn=sysadmins,ou=group The /etc/local/openldap/ldap.conf is: HOST doorbell.example.com BASE dc=example,dc=com TLS_CACERT /usr/local/etc/certs/cacert.crt TLS_REQCERT allow smb.conf is: [global] encrypt passwords = yes dns proxy = no strict locking = no read raw = yes write raw = yes oplocks = yes max xmit = 65535 deadtime = 15 display charset = LOCALE max log size = 10 syslog only = yes syslog = 1 load printers = no printing = bsd printcap name = /dev/null disable spoolss = yes smb passwd file = /var/etc/private/smbpasswd private dir = /var/etc/private getwd cache = yes guest account = nobody map to guest = Bad Password obey pam restrictions = Yes # NOTE: read smb.conf. directory name cache size = 0 netbios name = freenas workgroup = lodden server string = moonbase3 use sendfile = yes large readwrite = no store dos attributes = yes hostname lookups = yes local master = yes time server = yes security = user passdb backend = ldapsam:ldap://doorbell.example.com ldap suffix = dc=example,dc=com ldap user suffix = ou=people ldap group suffix = ou=groups ldap ssl = start tls ldap replication sleep = 1000 ldap passwd sync = yes #ldap debug level = 1 #ldap debug threshold = 1 ldapsam:trusted = yes idmap uid = 10000-39999 idmap gid = 10000-39999 create mask = 0666 directory mask = 0777 client ntlmv2 auth = yes dos charset = CP437 unix charset = UTF-8 log level = 1 [homes] comment = Home Directories valid users = %U writable = yes browseable = yes path = /mnt/storage1/sambahomes/%U [cdr] path = /mnt/storage1/CDR printable = no veto files = /.snap/.windows/.zfs/ comment = cdrs from switches writeable = yes browseable = yes inherit owner = no inherit permissions = no vfs objects = zfsacl hosts allow = 192.0.2.*, 192.0.3.* guest ok = no inherit acls = Yes map archive = No map readonly = no nfs4:mode = special nfs4:acedup = merge nfs4:chown = yes [iobase4] path = /mnt/storage2/iobase4 printable = no veto files = /.snap/.windows/.zfs/ writeable = no browseable = yes inherit owner = no inherit permissions = no vfs objects = zfsacl hosts allow = 192.0.20/24, 192.0.3.0/24 hosts deny = ALL guest ok = no inherit acls = Yes map archive = No map readonly = no nfs4:mode = special nfs4:acedup = merge nfs4:chown = yes ",mwlucas Active Tickets,1893,AFP randomly stops working in FreeNAS-8.3.0-RELEASE-x64 (r12701M),Backend,8.3.0-RELEASE,,defect,,reopened,2012-11-06T15:22:49Z,2012-11-20T13:02:18Z,"At random times AFP just stops working on my freshly installed 8.3.0 box. My Macs at random times start having problems accessing all AFP shares. These shares are Time Machine (only 1) and general storage. It also does not matter it the connection is new or existing. When this happens the only fix is to restart the AFP service. Syslog only shows the logins and logouts of users along with the transfer statistics. There are no lines indicating an issue. What other information could I add to the ticket to help?",gtholder Active Tickets,1898,UPS puts system in perpetual shutdown loop,Backend,8.3.0-RELEASE,,defect,,new,2012-11-11T19:27:56Z,2012-11-11T19:27:56Z,"Configuring the UPS service prevents the system from running, issuing an immediate shutdown command as soon as the UPS service starts during boot. Three email messages are generated each time: ON BATT LOW BATT SHUTDOWN the driver in question was blazer_usb and the problem occurred even with the UPS completely out of the loop. I am running 8.3.0-RELEASE 64 bit ",technoholic Active Tickets,1900,ISCSI performace low,Backend,8.3.0-RELEASE,,defect,,new,2012-11-14T04:09:02Z,2013-02-20T18:24:46Z,"Hi, Getting error on verious ISCSI LUN with slow performance: Nov 13 23:41:59 ssr212ma istgt[25631]: istgt_iscsi.c: 539:istgt_iscsi_read_pdu: ***ERROR*** iscsi_read() failed (-2,errno=35) Nov 13 23:41:59 ssr212ma istgt[25631]: istgt_iscsi.c:5223:worker: ***ERROR*** conn->state = 2 Nov 14 05:25:20 ssr212ma istgt[25631]: Login from iqn.1991-05.com.microsoft:isp239vm1 (10.98.98.160) on iqn.2011-03.ssr212ma.istgt:isp239vm1-lun1 LU4 (10.98.98.150:3260,1), ISID=400001370001, TSIH=9, CID=1, HeaderDigest=off, DataDigest=off Nov 14 05:25:30 ssr212ma istgt[25631]: istgt_iscsi.c: 539:istgt_iscsi_read_pdu: ***ERROR*** iscsi_read() failed (-2,errno=35) Nov 14 05:25:30 ssr212ma istgt[25631]: istgt_iscsi.c:5223:worker: ***ERROR*** conn->state = 2 Nov 14 05:26:45 ssr212ma istgt[25631]: istgt_iscsi.c:3570:istgt_iscsi_op_task: ***WARNING*** CmdSN(2790323) might have dropped ",vivek_sarmalkar Active Tickets,1915,iSCSI authorized access group with different user and peer user,Backend,8.3.0-RELEASE,,defect,,reopened,2012-11-27T06:24:34Z,2012-11-29T10:48:44Z,"if user and peer user are different, iSCSI authenticate fails even if only CHAP is enabled (changing peer user breaks CHAP, with mutual CHAP off). The description in the GUI is pretty ambiguous about user and peer user. I assumed user => initiator name (vSphere) peer user => target name (FreeNAS) tested with vSphere 5.1",realdreams Active Tickets,1924,Configuring an Address On an Aggregated Interface Causes a Page Fault,FreeBSD,8.3.0-RELEASE,,defect,,new,2012-12-01T08:11:42Z,2012-12-01T08:13:52Z,"I currently have a Super Micro server on which I have installed a fresh copy of FreeNAS 8.3.0. The server has two network interfaces which I would like to bond together. If I try to setup the aggregation via the web interface everything goes fine till I try to assign it an address or tell it to acquire one from DHCP. After clicking the submit button on the interface config panel the server kernel panics and outputs a page fault. Just to confirm that it wasn't a hardware issue I tried doing the same thing with a VirtualBox VM and the same thing happened. Any help regarding this issue would be greatly appreciated. Thanks, Neil Betham",nbetham Active Tickets,1930,Browsing a shadow copy kills 'Extended attributes',Backend,8.3.0-RELEASE,,defect,,new,2012-12-03T23:07:44Z,2012-12-05T21:19:12Z,"We have enabled 'Extended Attributes' on our CIFS share and can set the read-only attribute on individual files in the share from Windows. When I right-click on a folder, select 'Previous Versions' and press 'Open' on one of the versions, all read-only attributes disappear (not just in the shadow copy, also in the 'normal' file view) When I restart the CIFS service, the read-only attributes reappear. Steps to reproduce: * Create a new dataset ATTRIBS, and give full permissions to everyone * Create a Samba share for it, allowing guest access * Make sure that in the CIFS settings 'Extended Attributes' is enabled. * From Windows browse to the share, create a dummy file test.txt and a folder TESTFOLDER * From Windows make test.txt read-only * Set up a periodic snapshot on ATTRIBS and wait for the first shadow copy * Restart the CIFS service * From Windows right-click on TESTFOLDER. It should show one previous version * Select that version and press 'Open' (and now you can close it) Next check test.txt: you will notice the read-only attribute is gone. Right now you can verify smbd.log: it shows {{{ [2012/12/03 22:16:28.308853, 1] smbd/dosmode.c:247(get_ea_dos_attribute) get_ea_dos_attribute: Cannot get attribute from EA on file @GMT-2012.12.03-17.00.00/..: Error = Operation not supported }}} My guess: a samba shadow copy does not properly support Extended Attributes and dosmode.c on error disables the dos attributes with set_store_dos_attributes(SNUM(conn), False); I am not sure if this is a freenas bug or a samba bug.",glipman Active Tickets,1933,ZFS Send dies at 63.7G,Backend,8.3.0-RELEASE,,defect,,new,2012-12-05T20:36:36Z,2012-12-05T20:36:36Z,"Tried from 2 different FreeNAS servers: Steps to reproduce: Create snapshot: {{{ [root@freenas] ~# zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT pool/VMs@snap1 1.82G - 592G - }}} Send snapshot: {{{ [root@freenas] ~# zfs send pool/VMs@snap1 | ssh mmsdev@192.168.254.220 ""/usr/sbin/zfs receive data/VM/nfs"" Could not create directory '/root/.ssh'. The authenticity of host '192.168.254.220 (192.168.254.220)' can't be established. RSA key fingerprint is 94:a5:2f:f0:0b:e7:90:bc:0a:d8:d2:3b:2f:d4:0d:8e. Are you sure you want to continue connecting (yes/no)? yes Failed to add the host to the list of known hosts (/root/.ssh/known_hosts). Password: }}} It'll start transferring the dataset. Checking on the destination I can see the filesystem growing. When it reaches 63.7G (exactly, every time): {{{ NAME USED AVAIL REFER MOUNTPOINT data/VM/nfs 63.7G 3.49T 63.7G /data/VM/nfs }}} I get this back on the initial SSH connection on the FreeNAS boxes: {{{ The authenticity of host '192.168.254.220 (192.168.254.220)' can't be established. RSA key fingerprint is 94:a5:2f:f0:0b:e7:90:bc:0a:d8:d2:3b:2f:d4:0d:8e. Are you sure you want to continue connecting (yes/no)? }}} Source boxes are FreeNAS 8.3.0 Destinations are Solaris 11 I isolated the problem on the FreeNAS side after transferring 1.5TB from ZFS on Linux to the Solaris 11 boxes Network config: {{{ lagg0: flags=8843 metric 0 mtu 1500 options=401bb ether 00:1b:21:ce:d9:60 media: Ethernet autoselect status: active laggproto lacp laggport: igb3 flags=1c laggport: igb2 flags=1c laggport: igb1 flags=1c laggport: igb0 flags=1c vlan254: flags=8843 metric 0 mtu 1500 options=103 ether 00:1b:21:ce:d9:60 inet 192.168.254.7 netmask 0xffffff00 broadcast 192.168.254.255 media: Ethernet autoselect status: active vlan: 254 parent interface: lagg0 }}}",ebastos Active Tickets,1953,Add NFS share fail,Backend,8.3.0-RELEASE-p1,,defect,,reopened,2012-12-17T07:05:34Z,2013-04-15T18:44:56Z,"I want to add an NFS share, the error occurred.Please help me ----------------------------------------------------------------- Request Method: GET Request URL: http://192.168.100.XXX/admin/app-sharing/NFS_Share/add/ Software Version: FreeNAS-8.2.0-RELEASE-p1-x64 (r11950) Exception Type: AttributeError Exception Value: 'NoneType' object has no attribute 'gr_name' Exception Location: /usr/local/www/freenasUI/freeadmin/forms.py in _reroll, line 141 ----------------------------------------------------- Environment: Software Version: FreeNAS-8.2.0-RELEASE-p1-x64 (r11950) Request Method: GET Request URL: http://192.168.100.220/admin/app-sharing/NFS_Share/add/ Traceback: File ""/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py"" in get_response 105. response = middleware_method(request, callback, callback_args, callback_kwargs) File ""/usr/local/www/freenasUI/freeadmin/middleware.py"" in process_view 166. return login_required(view_func)(request, *view_args, **view_kwargs) File ""/usr/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py"" in _wrapped_view 23. return view_func(request, *args, **kwargs) File ""/usr/local/www/freenasUI/freeadmin/views.py"" in generic_model_add 482. mf = mf() File ""/usr/local/www/freenasUI/common/forms.py"" in __init__ 49. field._reroll() File ""/usr/local/www/freenasUI/freeadmin/forms.py"" in _reroll 141. glist.extend([(x.gr_name, x.gr_name) for x in FreeNAS_Groups(flags=FLAGS_DBINIT|FLAGS_CACHE_READ_GROUP|FLAGS_CACHE_WRITE_GROUP)]) Exception Type: AttributeError at /admin/app-sharing/NFS_Share/add/ Exception Value: 'NoneType' object has no attribute 'gr_name'",liaorice Active Tickets,1967,AFP server shows up twice in OS X finder sidebar,Backend,8.3.0-RELEASE-p1,,defect,,new,2012-12-23T13:47:59Z,2012-12-23T13:47:59Z,"If I create an AFP share and turn on the AFP service the freenas server shows up once in the side bar of the OS X finder (see: ""server name freenas one finder side bar server item.png"") which is OK. If I subsequently modify the server name the freenas server shows up twice in the finder side bar (see: ""server name modified two finder side bar server items.png""), once with the name freenas and once with the new name (in this case AFP Shares on SRV). This is not correct I guess. This might be due to a conflict in ...avahi/services/afp.service and afpd.conf.",haje Active Tickets,1976,Sending mail via a server times out too quickly,Backend,,,defect,,new,2012-12-30T21:33:33Z,2012-12-30T21:33:33Z,"A DNSBL I use on my mail server died. All this meant is that mail receipt was slower, as DNS timed out. However, FreeNAS stopped sending status messages. It turns out that it times out too quickly, and no mail was sent. It was not clear to me where the timeout is set; however, it should be willing to wait for several minutes, at the least.",sef Active Tickets,1979,Problem Installing ACER ASPIRE M1600,FreeBSD,8.3.0-RELEASE,,defect,,new,2013-01-01T16:21:28Z,2013-01-02T15:32:28Z,"I try to install Freenas 8.3.0 on my PC (Acer Aspire M1600)[[BR]] I got error something like this.[[BR]] [[BR]] [[Image(http://i49.tinypic.com/x35rhx.jpg)]]",bungandy Active Tickets,1994,samba3 domainjoin,Backend,,,defect,,new,2013-01-08T12:09:02Z,2013-01-08T12:09:02Z,"i can do a manual samba3 domain join add to smb.conf: security = domain wins server = 10.100.10.10 and type in the shell: net rpc join -U User -S server winbindd start but after a reboot my join is gone, so i look for a way to make it bootsave thanks for help Ansgar",aj Active Tickets,1999,autorepl.py don't update freenas:state of snapshots of child datasets,Backend,8.3.0-RELEASE-p1,,defect,,new,2013-01-14T20:51:15Z,2013-01-14T20:51:15Z,"When you schedule a recursive periodic snapshot the snapshots of all child datasets are created with the freenas:state=NEW which prevents them from being automatically removed. autorepl.py will recursively replicate the child datasets and snapshots but after it is done all child snapshots still have the freenas:state=NEW. I believe that 2 changes are necessary here: First, the LATEST snapshot on the child datasets should also be tracked and updated by autorepl.py. Second, the autosnap.py should only preserve datasets marked with freenas:state=LATEST. If a snapshot expires it doesn't matter if it has been replicated or not, it is EXPIRED and should be deleted unless it has to be kept to continue on performing incremental updates to the remote site.",raphaabreu Active Tickets,2007,VLAN support for plugin-jails,Backend,8.3.1-BETA2,,defect,,new,2013-01-17T20:32:37Z,2013-01-20T13:57:03Z,"Currently the plugins-jail does not work in connection with VLANs. (The attached patch is only a quick shot for demonstration!)",QZmn7igVMc Active Tickets,2023,Support for Intel chipset PCH-EG20T,Backend,8.3.0-RELEASE,,defect,,new,2013-01-30T12:25:52Z,2013-01-31T13:12:30Z,"HiI'm trying to do an embedded NAS using ATOM E6xx series supported from chipset PCH-EG20T , freenas comes up but seems that doesn't see the ethernet port because when I'm trying to configure the network interface doesn't permit to do it "" selectin 1 then the only possibility is to quit , if you try to set 1 or other , continue to ask a number or quit. this happen as well as 8.3.0 as with 8.3.1 beta 2. probably there isn't a driver in , could you help me to find a possible solution ? Many Thanks Massimo",spanom Active Tickets,2029,igb0 watchdog timeout,FreeBSD,8.3.0-RELEASE-p1,,defect,,new,2013-02-05T03:46:02Z,2013-02-06T01:42:16Z,"Hi, I got trouble with igb interface. Can anyone give me a clue how to solve this problem? Thanks! # uname -a FreeBSD ill-neptune.local 8.3-RELEASE-p5 FreeBSD 8.3-RELEASE-p5 #2 r244158M: Wed Dec 12 10:04:42 PST 2012 root@build.ixsystems.com:/home/jpaetzel/8.3.0/os-base/amd64/usr/home/jpaetzel/8.3.0/FreeBSD/src/sys/FREENAS.amd64 amd64 igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 644, hw tdt = 657 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 832, hw tdt = 847 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 240, hw tdt = 255 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 608, hw tdt = 614 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 880, hw tdt = 883 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 272, hw tdt = 283 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 260, hw tdt = 274 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 48, hw tdt = 59 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 336, hw tdt = 337 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 888, hw tdt = 902 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 80, hw tdt = 95 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 320, hw tdt = 331 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 976, hw tdt = 989 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 880, hw tdt = 886 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 96, hw tdt = 107 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 288, hw tdt = 296 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 976, hw tdt = 980 igb0: TX(0) desc avail = 0,Next TX to Clean = 0 igb0: link state changed to DOWN igb0: link state changed to UP dev.igb.0.%desc: Intel(R) PRO/1000 Network Connection version - 2.3.1 dev.igb.0.%driver: igb dev.igb.0.%location: slot=0 function=0 dev.igb.0.%pnpinfo: vendor=0x8086 device=0x10a7 subvendor=0x1014 subdevice=0x03ab class=0x020000 dev.igb.0.%parent: pci11 dev.igb.0.nvm: -1 dev.igb.0.enable_aim: 1 dev.igb.0.fc: 3 dev.igb.0.rx_processing_limit: 100 dev.igb.0.link_irq: 0 dev.igb.0.dropped: 0 dev.igb.0.tx_dma_fail: 0 dev.igb.0.rx_overruns: 0 dev.igb.0.watchdog_timeouts: 45 dev.igb.0.device_control: 1087373889 dev.igb.0.rx_control: 67141634 dev.igb.0.interrupt_mask: 0 dev.igb.0.extended_int_mask: 2147483648 dev.igb.0.tx_buf_alloc: 14 dev.igb.0.rx_buf_alloc: 34 dev.igb.0.fc_high_water: 29488 dev.igb.0.fc_low_water: 29480 dev.igb.0.queue0.interrupt_rate: 0 dev.igb.0.queue0.txd_head: 888 dev.igb.0.queue0.txd_tail: 900 dev.igb.0.queue0.no_desc_avail: 0 dev.igb.0.queue0.tx_packets: 436349867 dev.igb.0.queue0.rxd_head: 513 dev.igb.0.queue0.rxd_tail: 512 dev.igb.0.queue0.rx_packets: 425562895 dev.igb.0.queue0.rx_bytes: 100020119342 dev.igb.0.queue0.lro_queued: 0 dev.igb.0.queue0.lro_flushed: 0 dev.igb.0.mac_stats.excess_coll: 0 dev.igb.0.mac_stats.single_coll: 0 dev.igb.0.mac_stats.multiple_coll: 0 dev.igb.0.mac_stats.late_coll: 0 dev.igb.0.mac_stats.collision_count: 0 dev.igb.0.mac_stats.symbol_errors: 0 dev.igb.0.mac_stats.sequence_errors: 0 dev.igb.0.mac_stats.defer_count: 0 dev.igb.0.mac_stats.missed_packets: 0 dev.igb.0.mac_stats.recv_no_buff: 0 dev.igb.0.mac_stats.recv_undersize: 0 dev.igb.0.mac_stats.recv_fragmented: 0 dev.igb.0.mac_stats.recv_oversize: 0 dev.igb.0.mac_stats.recv_jabber: 0 dev.igb.0.mac_stats.recv_errs: 0 dev.igb.0.mac_stats.crc_errs: 0 dev.igb.0.mac_stats.alignment_errs: 0 dev.igb.0.mac_stats.coll_ext_errs: 0 dev.igb.0.mac_stats.xon_recvd: 0 dev.igb.0.mac_stats.xon_txd: 0 dev.igb.0.mac_stats.xoff_recvd: 0 dev.igb.0.mac_stats.xoff_txd: 0 dev.igb.0.mac_stats.total_pkts_recvd: 425651764 dev.igb.0.mac_stats.good_pkts_recvd: 425562657 dev.igb.0.mac_stats.bcast_pkts_recvd: 395845 dev.igb.0.mac_stats.mcast_pkts_recvd: 47237 dev.igb.0.mac_stats.rx_frames_64: 128623 dev.igb.0.mac_stats.rx_frames_65_127: 12448460 dev.igb.0.mac_stats.rx_frames_128_255: 463588 dev.igb.0.mac_stats.rx_frames_256_511: 28029848 dev.igb.0.mac_stats.rx_frames_512_1023: 5756859 dev.igb.0.mac_stats.rx_frames_1024_1522: 378735279 dev.igb.0.mac_stats.good_octets_recvd: 591288497119 dev.igb.0.mac_stats.good_octets_txd: 105497668860 dev.igb.0.mac_stats.total_pkts_txd: 482900105 dev.igb.0.mac_stats.good_pkts_txd: 482900105 dev.igb.0.mac_stats.bcast_pkts_txd: 245 dev.igb.0.mac_stats.mcast_pkts_txd: 586 dev.igb.0.mac_stats.tx_frames_64: 339321178 dev.igb.0.mac_stats.tx_frames_65_127: 88426360 dev.igb.0.mac_stats.tx_frames_128_255: 1941828 dev.igb.0.mac_stats.tx_frames_256_511: 786064 dev.igb.0.mac_stats.tx_frames_512_1023: 5373139 dev.igb.0.mac_stats.tx_frames_1024_1522: 47051536 dev.igb.0.mac_stats.tso_txd: 7713116 dev.igb.0.mac_stats.tso_ctx_fail: 0 dev.igb.0.interrupts.asserts: 38751909 dev.igb.0.interrupts.rx_pkt_timer: 425557788 dev.igb.0.interrupts.rx_abs_timer: 425558074 dev.igb.0.interrupts.tx_pkt_timer: 428636455 dev.igb.0.interrupts.tx_abs_timer: 0 dev.igb.0.interrupts.tx_queue_empty: 482896063 dev.igb.0.interrupts.tx_queue_min_thresh: 0 dev.igb.0.interrupts.rx_desc_min_thresh: 0 dev.igb.0.interrupts.rx_overrun: 0 dev.igb.0.host.breaker_tx_pkt: 0 dev.igb.0.host.host_tx_pkt_discard: 0 dev.igb.0.host.rx_pkt: 4870 dev.igb.0.host.breaker_rx_pkts: 0 dev.igb.0.host.breaker_rx_pkt_drop: 0 dev.igb.0.host.tx_good_pkt: 4042 dev.igb.0.host.breaker_tx_pkt_drop: 0 dev.igb.0.host.rx_good_bytes: 591288452065 dev.igb.0.host.tx_good_bytes: 105497686660 dev.igb.0.host.length_errors: 0 dev.igb.0.host.serdes_violation_pkt: 0 dev.igb.0.host.header_redir_missed: 0 ",dikshie Active Tickets,2046,system crash all the time,Backend,8.3.1-BETA2,,defect,,new,2013-02-16T14:57:57Z,2013-03-04T19:39:26Z,"Hi, My system crash when I copy or read any file on my zfs partition. It's really boring because I can't do anything why my NAS ! I post a picture of the issue Thanks for any help ",deteklover Active Tickets,2048,"After fresh install, trying to create encrypted volume, Error occurs = Database is locked",Backend,8.3.1-BETA3,,defect,,new,2013-02-17T17:54:23Z,2013-02-18T18:44:55Z,"Tried two different flash drives and different USB ports. Image is written using Win32DiskImager. FreeNAS-8.3.1-BETA3-x64 (r13264) 8GB DDR3-1600 (PC3-12800) CL 9 Dual Channel Desktop Memory Kit AsRocks FM2A75M-ITX AMD A6-5400K APU with Radeon(tm) HD Graphics 3 WD Red 3TB drives Bios on motherboard is latest. Not sure what else to try? Request Method: POST Request URL: http://192.168.1.75/admin/app-system/Advanced/edit/1/?inline=true Software Version: FreeNAS-8.3.1-BETA3-x64 (r13264) Exception Type: DatabaseError Exception Value: database is locked Exception Location: /usr/local/lib/python2.7/site-packages/django/db/backends/sqlite3/base.py in execute, line 344 Server time: Sun, 17 Feb 2013 09:52:41 -0800 ------------------------------------------------------------- Traceback---- Environment: Software Version: FreeNAS-8.3.1-BETA3-x64 (r13264) Request Method: GET Request URL: http://192.168.1.75/services/core/?dojo.preventCache=1361122385997 Traceback: File ""/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py"" in get_response 105. response = middleware_method(request, callback, callback_args, callback_kwargs) File ""/usr/local/www/freenasUI/../freenasUI/freeadmin/middleware.py"" in process_view 166. return login_required(view_func)(request, *view_args, **view_kwargs) File ""/usr/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py"" in _wrapped_view 20. return view_func(request, *args, **kwargs) File ""/usr/local/www/freenasUI/../freenasUI/services/views.py"" in core 141. smart = models.SMART.objects.create() File ""/usr/local/lib/python2.7/site-packages/django/db/models/manager.py"" in create 137. return self.get_query_set().create(**kwargs) File ""/usr/local/lib/python2.7/site-packages/django/db/models/query.py"" in create 377. obj.save(force_insert=True, using=self.db) File ""/usr/local/lib/python2.7/site-packages/django/db/models/base.py"" in save 463. self.save_base(using=using, force_insert=force_insert, force_update=force_update) File ""/usr/local/lib/python2.7/site-packages/django/db/models/base.py"" in save_base 551. result = manager._insert([self], fields=fields, return_id=update_pk, using=using, raw=raw) File ""/usr/local/lib/python2.7/site-packages/django/db/models/manager.py"" in _insert 203. return insert_query(self.model, objs, fields, **kwargs) File ""/usr/local/lib/python2.7/site-packages/django/db/models/query.py"" in insert_query 1593. return query.get_compiler(using=using).execute_sql(return_id) File ""/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py"" in execute_sql 910. cursor.execute(sql, params) File ""/usr/local/lib/python2.7/site-packages/django/db/backends/sqlite3/base.py"" in execute 344. return Database.Cursor.execute(self, query, params) Exception Type: DatabaseError at /services/core/ Exception Value: database is locked ",themuffinman Active Tickets,2052,Backup to FreeNas aborts between 2.4GB and 4.2GB mark,Backend,,,defect,,new,2013-02-18T21:06:57Z,2013-03-15T17:24:47Z,"I have been on the IRC channel and jpaetzel requested I create this ticket for further analysis. Backups keep either failing or aborting or whatever around between the 2.4GB and 4.2GB mark. The tests I have done have been from two different machines (both in the same location) and I have now tried two different backup clients (Handy Backup and SyncBackPro) with the same result. When I go look at the source machine where SyncBackPro is running, the program is no longer running. There is no log file for me to review, no final email was sent after which should occur after the job is completed. Also, I don't see any issues in the Windows event logs. When I restart SyncBackPro and run the Sync job again, it picks up from where it left off and does another ~4GB until the program just exits or whatever again. This just feels like there is some timeout setting or something like that going on. Normally, 4GB makes me think of a FAT32 type of filesize limit, but I am syncing from an NTFS filesystem to a ZFS filesystem, so that shouldn't be an issue. Per jpaetzel, I have run the following to get a dump: tcpdump -i igb0 -s 0 -w tcpdump.out host ip.of.cifs.client (with appropriate parms replaced). The file was still almost 1GB after bzip2, so I took the last 100 lines via tail which I hope will still result in a file that is usable for analysis. Any suggestions are welcome as I really need to get past this for any backups or syncs to complete. ",schuc Active Tickets,2106,Plugin Jail prevents AFP server name from broadcasting...,Backend,8.3.1-RELEASE,,defect,,new,2013-03-29T02:28:17Z,2013-03-29T02:28:17Z,"In FreeNAS-8.3.1-RELEASE-x64 (r13452) the AFP server name is no longer visible in Lion or Mountain Lion's finder sidebar (the most recent Apple versions of each) after I install the jail plugin. You cannot connect by using ""Connect to server"" AFP://servername either. You can, however, connect using AFP://192.168.1.2 and then all the shares become visible and once a share is mounted the server shows up in the shared section of the finder's sidebar. Once connected everything works as you would normally expect. So the server is sharing files correctly it's just not broadcasting it's name (maybe I'm using the wrong term here - but I hope the idea is clear....) If I turn off the plugins service (I'm using the one for this version installed fresh) the server name immediately reappears in the sidebar. The only installed plugin is minidlna (also the one for this FN version) The MB has two onboard NICs, only one is configured. could it be the jail IP address bridging that's doing it ? ",mikedeissler Active Tickets,2121,nptd2 and bzip2 vulnerabilities?,FreeBSD,8.3.1-RELEASE,,defect,,new,2013-04-10T21:42:47Z,2013-04-10T21:42:47Z,"This is pasted from a user created thread at http://forums.freenas.org/showthread.php?12311-FreeBSD-security-vulnerabilities-in-FreeNAS-that-are-not-fixed-but-supposed-to-be Colleagues, I have FreeNAS 8.3.1-REL based upon FreeBSD 8.3p6. Security scanning reveals that bzip2(ver 1.0.5), nptd2(ver 4.2.4p5) and openssl(ver 0.9.8q) need to be upgraded in order to patch the vulnerabilities to 1.0.6, 4.2.4p7 and 1.0.0h respectively. I posted to FreeBSD forums to try and get to the bottom of the issues and possible resolve the security vulnerabilities in FreeNAS/FreeBSD. What is odd is that the community says that the vulnerabilities in ntpd and bzip2 were fixed long ago and should NOT be present in FreeNAS 8.3.1-REL/FreeBSD 8.3p6 --but they STILL are. Reference:http://forums.freebsd.org/showthread.php?p=216392&posted=1#post216392 Anyone know why the BSD community says this stuff is patched since 8.1 and the problems still show up in FreeNAS as of only a couple months ago? The vulnerabilities are years old now. -Jim I have no idea if the user is correct or not. I am just creating the ticket because I could find no other ticket for this in the system.",noobsauce80 Active Tickets,2128,8.3.1 p2 dirty : new jail mount points not persistent across reboot.,Backend,8.3.1-RELEASE,,defect,,new,2013-04-13T06:24:52Z,2013-04-13T06:34:25Z,"AMD 2 x quad Opteron 2.7Ghz Tyan S2927 Mainboard 16GB ECC Ram 6 x WD 1TB Z2 Updated from 8.2.0, Jail mount points were persistent. After update though I installed some perl modules and wrote a script in the jail using jexec, then through the GUI created a mount point. After a reboot, the mount point was still in the GUI table, but not enabled. I have enabled the mount point and rebooted. The system came back up with the one mount point disabled. No errors listed in the messages log. The jail environment is 8.2.0 until I create pbi's for my additions. I'll be updating to 8.3.1 p2 release to see if it's corrected ",cordel Active Tickets,2132,RRDs saved to /data not checked for size,Backend,8.3.1-RELEASE,,defect,william,accepted,2013-04-15T17:41:00Z,2013-05-15T12:45:47Z,"Every hour the system tries to save the RRD datafiles backing the reporting to /data. The save script does not check that the RRDs will actually fit on /data, causing it to try and fail to copy the data every hour on systems with lots of RRDs, generating a cron email and a system log entry. While RRD files are of fixed size (based on configured parameters), the number of RRD files varies by user-controllable factors such as # of network interfaces and # of pools and datasets. ",dwhite Active Tickets,2133,Cannot assign permissions for Active Directory users,Backend,8.3.1-RELEASE-p1,,defect,,new,2013-04-16T10:33:01Z,2013-05-20T21:12:37Z,"First some details on my system: FreeNAS-8.3.1-RELEASE-p2-x64 (r12686+b770da6_dirty) Intel(R) Core(TM)2 CPU 6420 @ 2.13GHz 4006MB Connecting FreeNAS to Active Directory (SBS2003 - Portuguese) is working. The log shows: AD_status_domain: net ads status -U Administrator AD_status_domain: Okay The 'wbinfo' command line tool works ok. I can list users, groups and the RPC connection test succeeds. The problem is that user and group listboxes only show local users, the domain users and groups are missing in those lists, so it is not possible to assign domain permissions to volumes or shares. If I knew what component to inspect, I could help debugging this, i.e., how are the user and group listboxes populated from Active Directory?",tareco Active Tickets,2141,MiddlewareError: Unable to backup plugins,Backend,8.3.1-RELEASE,,defect,,new,2013-04-21T19:46:47Z,2013-04-21T20:07:49Z,"Hello, for whatever reason manage.py gives me this error while I try to upgrade a jail: manage.py: [middleware.exceptions:38] [MiddlewareError: Unable to backup plugins] This happens repeatedly every time I try updating jail via web-gui. My freenas is of version 8.3.1 r13452. I don't recall what's the old version of jail, it's been around for some while. The new jail I try to use is the latest from 8.3.1 p1. Here is a thread on forums I opened for it, but unfortunately no-one answered: http://forums.freenas.org/showthread.php?12348-freenas-jail-update-fails-what-does-it-do There is enough space (>2G) on the disk I have the jail on. I have transmission and minidlna plugins in use.",ikke Active Tickets,2153,Unable to replace disk,Backend,8.3.1-RELEASE-p1,,defect,,new,2013-04-25T13:43:46Z,2013-05-11T22:01:03Z,"Steps to reproduce (I first encountered this on a real system, but it is also reproducible in a fresh virtual machine install): 1. Create *encrypted* raidz volume consisting of 3 drives (da1, da2, da3) 2. Offline da1 3. Replace da1 with da4 4. Detach da1 (if needed). 5. You have now a healthy volume again. 6. Offline da4 7. Try to replace with da1. Actual: Replacement fails with: Error: Unable to GPT format the disk ""da1"" Log contains this new messages: Apr 25 06:31:12 freenas notifier: swapoff: /dev/da1p1.eli: No such file or directory Apr 25 06:31:12 freenas notifier: geli: No such device: /dev/da1p1. Apr 25 06:31:12 freenas notifier: dd: /dev/da1: Operation not permitted Apr 25 06:31:13 freenas notifier: dd: /dev/da1: Operation not permitted Apr 25 06:31:14 freenas manage.py: [middleware.exceptions:38] [MiddlewareError: Unable to GPT format the disk ""da1""] Expected: Replacement succeeds. Notes: Trying to reboot the system in this state fails too (Sorry, an error occurred) *This does not happen when using unencrypted pool.*",dusan Active Tickets,2162,Error while creating new user,GUI,8.3.1-RELEASE-p1,,defect,,new,2013-04-30T16:57:57Z,2013-05-20T11:45:46Z,"I getting an error ""This field is required"" in Home Directory Mode field. All checkboxes in this field are grayed. Tried in various browsers and platforms (pc, mac) with same error. Everything become ok after rebooting the freenas. I thik this problem will return later. FreeNAS-8.3.1-RELEASE-p2-x64 (r12686+b770da6_dirty)",beezone Active Tickets,2167,After power is off FreeNAS loses connection with UPS,Backend,8.3.1-RELEASE,,defect,,new,2013-05-05T12:48:21Z,2013-05-05T12:48:21Z,"UPS Mustek PowerMust 636 After power is off FreeNAS loses connection with UPS and doesn't reconnect, is necessary to switch UPS OFF and ON via web gui",poldas Active Tickets,2178,Replacing encrypted zpool disk but can't recover using recovery key,GUI,8.3.1-RELEASE-p2,,defect,,new,2013-05-11T22:17:46Z,2013-05-17T15:20:16Z,"So I have a RAIDZ2 with a failing disk. FreeNAS-8.3.1-RELEASE-p2-x64 (r12686+b770da6_dirty) is in use(and was used to create the encrypted zpool). Some data was copied to the zpool, then the disk was found to be failed. As I always say when people ask how to recover from a failed disk in the forum, I followed section 6.3.11 of the manual. So after mounting the zpool with the recovery key(I'm lazy and didn't feel like entering the password) I offlined the failing disk. [B]# zpool status[/B] showed that the disk was offline. Then did a shutdown of the server. After the server was off I removed the bad disk and inserted the replacement disk in its hard drive bay. Booted up the server, then went back to section 6.3.11 of the manual. So I remounted the zpool with the recovery key(again.. because I'm lazy). After the zpool was mounted I clicked the ""replace"" button in the GUI and chose the new disk. It asked for a passphrase, so I entered the password that is normally used to decrypt the zpool if you aren't using the recovery key(this may be key to the issue because if you remember I have always used the recovery key). I had to enter the normal passphrase for the zpool since you can't leave the field empty(the GUI makes you enter a passphrase). The resilvering started automatically and all seems well. After the resilver finishes I did a # zpool status and took a look. Sure enough the old disk is still listed, as expected. The manual has step 6.3.11.4 that says to detach the disk. So I clicked the ""detach"" button in the GUI. The disk disappears from the GUI and a # zpool status shows everything is perfect. Fantastic! All is well. But I decided I wanted to do a reboot and try to mount the zpool again just to be sure that everything is okay for the long term. So again, I did a reboot. This time I chose my recovery key(laziness...) and I have a zpool that is degraded. If I do a zpool status, that new disk that just finished resilvering is not decrypting. I have a degraded pool again. So I started the resilvering again, but went to a VM and checked my steps. Sure enough, if you do all of the steps I've explained in a VM, then you will end up with a zpool that will lose that newly resilvered disk when you reboot IF you use the recovery key. If you use the regular key + pasphrase, then the zpool will mount with all the disks. There seems to be no difference for the actual disk replacement steps regardless of if you use the key+passphrase or the recovery key. So now the recovery key is not very useful because my RAIDZ2 will not be anything more than a RAIDZ1 without getting a recovery key that will work for all the drisks. If enough disks fail it could render the recovery key useless. But, not matter what I do(whether I used the recovery key from the very beginning or the key+passphrase, I cannot recreate a new recovery key(nor is the old one useful if I have a disk that won't ever mount with the recovery key). So it appears that after replacing a failed disk you are in a situation where you cannot use recovery keys at all, except for the original zpool disks. If I try to ""Remove Recovery Key"" from the GUI I get the error ""Error: Unable to remove key: geli: Cannot open gptid/a5c302c1-ba7d-11e2-be48-0800273c22b6: No such file or directory."" except that the a5c302c1 isn't part of my zpool. If I try to ""Add Recovery Key"" from the GUI I get the error ""Error: Unable to set recovery key: geli: Cannot open gptid/a5c302c1-ba7d-11e2-be48-0800273c22b6: No such file or directory."" except that again, for the same reason as above, the a5c302c1 is NOT part of my zpool. No recovery key is then offered for download(not sure if this matters, but included for completeness). If I try to do an ""Encryption Re-Key"" and enter my passphrase from the GUI then I get the error ""Error: Unable to set key: geli: Cannot open gptid/a5c302c1-ba7d-11e2-be48-0800273c22b6: No such file or directory."", except that the a4c302c1 isn't part of my zpool anymore. I've tried rebooting, and whatnot to see if it will forget about the a4c302c1 but its clear it won't. To be honest, I'm only taking an educated guess that the a4c302c1 was the old disk. But I think it's pretty safe to say that it was. If I do a @ zpool status of my array when it is mounted and listed as healthy my zpool contains GPTs starting with b43505a5,a5fda44a, and a62d806a. So what went wrong with recovering from a failed disk? I followed the FreeNAS manual to the best of my ability and I'm not understanding what went wrong with this whole process. I've ruled out the fact that I used the recovery key instead of the actual key+passphrase and there's no warning in the manual that if you replace a failed disk in an encrypted zpool that there is no longer any way to create a new recovery key(at least that I can find). I have to assume that this wasn't oversight by the manual writers and that somehow I'm doing something wrong but section 6.3.11 doesn't provide any clear indication as to what I may have done wrong nor has reading through the FreeNAS manual. Additionally, I'd recommend that 6.3.11 be expanded for disk replacement to include steps for replacing a failed disk on an encrypted zpool to include mounting the degraded encrypted zpool, etc. I know it's common sense for many of us but new users might quickly get very upset and start worrying about their data. I couldn't find the proper place to request changes to the manual. Someone said there is a way to create a wiki account. Listed as major because this can have serious consequences if you have multiple disk failures with no ""recovery key"" and you forget your passphrase.",noobsauce80 Active Tickets,2184,"GUI shows available and intact spare as ""null"" after drive failure",GUI,8.3.1-RELEASE-p2,,defect,william,accepted,2013-05-14T15:41:36Z,2013-05-16T17:24:10Z,"I have a RAID-Z containing 7 devices and 1 hot spare. I physically remove one of the devices (da2 in this case) and the volume status shows the spare as status ""null"" although {{{ zpool status }}} returns the correct state. This prevents me from replacing the failed drive with the spare from the GUI. See attached screenshots.",hlinden Active Tickets,55,Unconfigured network interface handling in GUI,GUI,8.0.3-RELEASE-p1,,enhancement,,new,2010-11-22T16:48:43Z,2012-02-07T16:25:11Z,"On a fresh system, It appears the default behavior is to configure all network cards to dhcp. I think this is a great idea, however, to make the experience even better for users: Users expect to see their devices under the ""network -> interfaces"" tab whether they've been 'configured' or not. If an Ethernet adapter is recognized by freenas and set to DHCP in the backend, the interfaces tab should reflect that configuration from the beginning. Right now, devices do not appear in the menu selection unless they have been manually set in the GUI.",surlyjake Active Tickets,286,GUI for ZFS pool scrubbing: configurable frequency and archived results / error trends,Backend,8.0.3-RELEASE-p1,,enhancement,jpaetzel,accepted,2011-04-24T02:18:30Z,2012-02-07T17:46:39Z," (Enhancement request to maximize zpool reliability/availability) Automatic, periodic ZFS pool scrubbing with results collection, reporting, and alerts. It would be great to have functionality in the GUI to streamline the setting of weekly or monthly zpool scrubs, collect and archive scrub results, and include the last few scrub results in periodic emails. A reasonable default would be to set a weekly zpool scrub at e.g. 3am Sunday for all zpools upon creation. Some background from the ZFS Best Practices wiki: ""Run zpool scrub on a regular basis to identify data integrity problems. If you have consumer-quality drives, consider a weekly scrubbing schedule. If you have datacenter-quality drives, consider a monthly scrubbing schedule. You should also run a scrub prior to replacing devices or temporarily reducing a pool's redundancy to ensure that all devices are currently operational."" -- http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide The implicit rationale for periodic scrubbing is to proactively detect bit errors and stay ahead of drive failures. Having recently completed a scrub maximizes the probability that the data you have on disk is correct, since if/when you enter degraded mode you can no longer correct latent errors. ",jal Active Tickets,388,There is no way to limit periodic snapshots on remote server,Backend,8.2.0-RELEASE,,enhancement,,new,2011-06-03T18:24:28Z,2012-08-25T09:26:56Z,"Server A takes snapshots every 15 minutes and keeps them up to 2 hours. Server A replicates snapshots to Server B. Server A automatically destroys snapshots greater than 2 hours. Server B retains all received snapshots. Is it possible to keep these servers in sync; which Server B will destroy any snapshots greater than what's reported from Server A. ",ajb Active Tickets,458,Feature request: DRAM ECC error alerting/logging/reporting,Backend,8.0-RELEASE,,enhancement,,assigned,2011-06-22T21:36:49Z,2012-04-14T00:57:15Z,"For optimal data reliability and availability, it would be ideal to be able to track DRAM ECC errors, via email alerts and, ideally, in a centralized location in the web UI (perhaps alongside SMART warnings and ZFS scrub errors). The goal is to be able to spot trends of corrected errors in a given component (DIMM or disk), since they often come in advance of an uncorrectable error or component failure. ECC errors are exposed via MCA reports in /var/log/messages in FreeBSD 8.2, and the 'mcelog' utility looks pretty handy! See also: http://lists.freebsd.org/pipermail/freebsd-stable/2010-December/060705.html ",jal Active Tickets,475,ACL webGUI options,GUI,8.0-RELEASE,,enhancement,,new,2011-06-28T18:49:39Z,2011-06-28T18:49:39Z,"would be nice to get an GUI option for the ACL (""getfacl"" and ""setfacl""). I think a lot of home users will end up needing this in order to give family and friends one set of rights while keeping others for their own users. Forum examples: http://forums.freenas.org/showthread.php?670-Group-and-users-configuration-for-n00b-%28like-me...%29 http://forums.freenas.org/showthread.php?297-Q.-about-setting-up-basic-structures PS: Hope i set the options below right, if not I'm sorry. This bugtracker is a bit different then the other ones I'm used to. -Bohs",dJabba Active Tickets,549,Enhancement: ZFS-hosted Configuration,Backend,8.0-RELEASE,,enhancement,,new,2011-07-23T17:09:30Z,2011-07-23T17:09:30Z,"This enhancement request is asking for FreeNAS/TrueNAS to be more NetApp-like in terms of separating boot media and filer configuration. This works as follows: - The flash device is entirely read-only and just contain a vanilla FreeNAS OS image. - Configuration state is stored separately on a dedicated ZFS dataset (called the ""root volume"" in NetApp parlance). The big advantages of this model: - Backup and recovery of the FreeNAS configuration uses the same tools and techniques as backup and recovery of ZFS datasets, including RAID-Z protection and automated replication. The flash device is completely replaceable and unnecessary to individually back up, as it contains a vanilla FreeNAS boot image. - FreeNAS ""personality"" is associated with the drives, not the appliance head. If I physically move my ZFS pool between FreeNAS heads, the dataset and pool configuration should follow the drives. ",jal Active Tickets,637,Get diag info from GUI / console in a more aggregated manner,GUI,8.0-RELEASE,,enhancement,,new,2011-08-20T19:25:57Z,2011-09-29T01:37:25Z,It would awesome if I could access the Logs from the Web GUI and then have the ability to either e-mail them or save them to the setup storage device so I can access from an active computer. This would allow users to have an easier time getting support. As it is I am going to have to hand write the errors from a screen I have to setup so I can get better assistance. ,qops1981 Active Tickets,666,TreeMenu displays (too many?) saved items,GUI,8.0.1-BETA4,,enhancement,,new,2011-08-26T22:05:14Z,2011-08-26T22:05:14Z,"Can we set a hard limit (or remove) the amount of saved objects that are displayed in the tree menu? I am not sure if there is a need to access saved items from the tree menu, that's what datagrids/tables are for :). I would opt to *only* use the tree to navigate to section/sub-sections of the UI, or to launch 'Add New' and 'Show All' operations, not for displaying/editing volumes, shares, users, etc...",james Active Tickets,778,ZFS Replication - Confirm status,Backend,8.0.1-RC1,,enhancement,,new,2011-09-13T06:55:21Z,2011-10-04T15:22:22Z,A nice replication enhancement to receive a report on the current state of replication good or bad at a user configurable interval.,daxroc Active Tickets,856,Per-user quota support in GUI,Backend,8.0.1-RC2,,enhancement,,new,2011-09-30T06:40:43Z,2011-09-30T06:40:43Z,"A customer has requested that per-user GUI support be made available in the GUI. This can be enabled and queried via the following subcommands: # zfs list -o userquota@johndoe tank/usr USERQUOTA@JOHNDOE none # zfs set userquota@johndoe=100g tank # zfs list -o userquota@johndoe tank USERQUOTA@JOHNDOE 100G # zfs set userquota@johndoe=none tank # zfs list -o userquota@johndoe tank USERQUOTA@JOHNDOE none A quickly hacked version can go in the CLI under ""permissions"", but given a more proper design, a tree hierarchy based GUI should be created for managing permissions and properties, as discussed earlier today (otherwise it's not intuitive how permissions are set and it's editing quotas and permissions can become painful). The examples above show ZFS permissions getting and setting; it's sort of doable in UFS as well, but it's more painful and less granular I've read, as it's set on a per-filesystem basis instead of a per-directory/dataset basis. So I wouldn't worry about UFS, but I would make things abstract enough that if someone wished to set quotas for UFS or other filesystems in the future, the building blocks would be there to complete the said task (with appropriate restrictions).",gcooper Active Tickets,939,Have the SMART test email default to the admin's address,GUI,8.0.2-RELEASE,,enhancement,,new,2011-10-20T01:28:24Z,2012-02-03T19:27:13Z,"Today, instead of the email address field being empty in the SMART test service configuration GUI, it should really default to the admin's email address. This should be an item autopopulated from the translation code. Having a checkbox for enabling / disabling SMART test emails seems silly on the other hand because if someone wants the auto-SMART test capability from smartd, they really should get the corresponding email as well.",gcooper Active Tickets,957,tftpd feature request,Backend,8.0.2-RELEASE,,enhancement,,new,2011-10-27T00:21:39Z,2011-12-12T22:25:14Z,would like to have tftpd added to freenas and with a gr /\ so u can boot pxe envirments.,dw5304 Active Tickets,958,zfs replication to local storage feature request,Backend,8.0.2-RELEASE,,enhancement,,new,2011-10-27T00:24:19Z,2011-10-28T18:25:44Z,"i would also like to have the ability to replicate to local hdd storage instead of a remote machine. ",dw5304 Active Tickets,964,Set up separate schedules for ZFS replication and snapshotting,Backend,8.0.2-RELEASE,,enhancement,,new,2011-10-28T19:01:50Z,2011-10-28T19:01:50Z,"A customer requested that we provide different ways to schedule replication and snapshotting, because he prefers to snapshot during the day and do his backups at night at a set time. The default should be simultaneous snapshot / replication (current behavior), but have additional dialogs so they can set a second schedule for replication.",gcooper Active Tickets,1001,'vlan' property should be tied into the interface configuration pane,GUI,8.0.2-RELEASE,,enhancement,,new,2011-11-10T06:04:12Z,2011-11-10T06:04:12Z,"In order to streamline the way that interfaces are configured, it would be really nice if vlan configuration became a property of an interface. It would at least make one-stop configuration a reality and would make everyone's lives a lot easier instead of having to do the multiple reboot song and dance in order to configure networking.",gcooper Active Tickets,1002,Interface configuration really shouldn't require multiple reboots,Backend,8.0.2-RELEASE,,enhancement,,new,2011-11-10T06:07:33Z,2011-11-10T06:07:33Z,"Having to jump through hoops multiple times to configure a network is annoying.. especially with machines that have multiple HBAs/NICs/RAID cards that install BIOSes, etc.. it really makes life more annoying for initial setup, or if one needs to modify things down the line. Most of this stuff can be setup one time without having to reboot. Born out of the fact that I need to internally play Jeopardy music every time I talk to someone in support calls when it reboots the system multiple times.",gcooper Active Tickets,1023,Make software more IPv6 capable,Backend,8.0.2-RELEASE,,enhancement,,new,2011-11-19T01:21:09Z,2011-11-19T01:21:09Z,"There are certain assumptions in the GUI code and middleware that think that we're always going to be dealing with IPv4 networks. This is wrong and this hinders us from making progress in the respect that IPv4 is officially dying as a protocol (running out of addresses). Do an egrep for ""XXX:.*ipv4"" (case insensitive) in the code to get a preliminary idea of what I mean.",gcooper Active Tickets,1048,Secure WebDAV client-side replication/off-site backups,Backend,8.0.2-RELEASE,,enhancement,,new,2011-11-27T23:06:22Z,2011-11-27T23:06:22Z,"Will it be possible to use WebDAV remotely to mirror the contents of a selected FreeNAS ZFS partition in future versions? I have a FreeNAS server running 8.0.1-RELEASE. I also have a Secure WebDAV based file store, provided by a reputable firm whom I have done business with for many years, and who have sufficiently good/redundant fibre connectivity, and BGP route distribution, that I don't need to worry about reaching that file store. Also: I have no capability to run shell scripts or otherwise mount the WebDAV volume - it is strictly storage only. So I cannot use 'zfs receive'. I would prefer not to use a so-called 'cloud provider' for reasons of data protection and information security. There is demand for an iDisk style server for iOS devices to see FreeNAS storage - this is NOT the same thing. ",bms Active Tickets,1102,Run Cron jobs / Rsync tasks on demand,Backend,8.0.2-RELEASE,,enhancement,,new,2011-12-15T10:35:50Z,2011-12-15T11:06:32Z,"If would be very usefull that cron jobs and Rsync tasks could be created without scheduling with the ability to run them manually on demand (i.e ""Run Now"" button) For instance, my backup target machine, for security reason (disk rotation), is not always available ",psxtekno Active Tickets,1141,Permissions setting in the GUI needs to be more intelligent,Backend,8.0.3-RC2,,enhancement,,new,2012-01-01T10:39:51Z,2012-01-01T10:59:33Z,"1. Home users might not need ACLs. It should really be something like: - Off - Unix - Windows 2. The ACLs and permissions shouldn't be blindly set by default in the GUI unless the values change OR someone checks a box that says ""set permissions"". 3. Setting ACLs, owner, group, and mode should be individual operations and not all glommed into one operation (either in the GUI, or middleware.notifier.notifier.mp_set_permission).",gcooper Active Tickets,1164,Add support for NIS user/group integration,Backend,8.0.3-RELEASE,,enhancement,,new,2012-01-11T18:46:03Z,2012-08-10T19:55:22Z,"Some users have requested that we add support for NIS user/group integration in FreeNAS. Basically we need to support yp in a similar manner as what's currently done in the AD/LDAP integration feature sets.",gcooper Active Tickets,1175,Updater mechanism,Backend,8.0.2-RELEASE,,enhancement,,new,2012-01-12T17:09:51Z,2012-01-12T17:09:51Z,"The following is a brief description of how we could and should provide updates to the end user from a 20k ft view: 1. Periodically create a session with a remote site or proxy (if the administrator has a large deployment of machines that need to be managed) via a daemon (not a cronjob). The period with which the update list can be polled can be configured within the GUI/CLI. 2. Provide details about the underlying device (serial number, model, etc) s.t. the authority in charge of providing the update could give a yay or nay as to whether or not the system could be updated for policy reasons (this is for non-FreeNAS instances). 3. Grab a list of compatible images. 4. Cache the list of compatible images somewhere. 5. Take the list in step 4. and notify the user that an update was available. Once the user goes to the right dialog... 6. Present the list of images to the user in such a manner that they could determine whether or not they wish to upgrade to X, Y, or Z. 7. Pull down the image (via HTTP, FTP, SSH, or another arbitrary method). 8. Install using the predefined algorithm. Finally, this functionality should be enabled by default, but the administrator should be able to also opt out if requested.",gcooper Active Tickets,1177,Need knob in the GUI for tuning the user cache size,GUI,8.0.3-RELEASE,,enhancement,,new,2012-01-12T18:13:28Z,2012-01-12T18:13:28Z,"Per http://forums.freenas.org/showthread.php?5576-Large-Active-Directory-Env-Configuration and other bits, it would be nice if there was a knob in the GUI for configuring what the size of /var/tmp/.cache should be. It should be maintained under whatever dialog the authentication should go for. For now putting it under System -> Advanced should suffice. It should allow values between 256m and 4g; m and g are the suffixes that should be allowed.",gcooper Active Tickets,1179,Existing tunables and sysctls entries in /etc/sysctl.conf and /boot/loader.conf should be listed under loaders / sysctls GUI forms,GUI,8.0.3-RELEASE,,enhancement,,new,2012-01-12T18:24:37Z,2012-01-12T18:24:37Z,"Some of the values that are in /etc/sysctl.conf and /boot/loader.conf would be good to present to the end user in the sysctl and loaders GUI forms, s.t. they could fully tune the values to suit their tastes. Examples of this are: /boot/loader.conf: 1. Drivers currently in /boot/loader.conf . 2. kern.ipc.nmbclusters /etc/sysctl.conf: 1. kern.metadelay 2. kern.dirdelay Etc.",gcooper Active Tickets,1195,Provide SNMP plugin for collectd,Backend,8.0.3-RELEASE,,enhancement,,new,2012-01-14T11:45:36Z,2012-01-14T11:45:36Z,"Hi Freenas Team, Requesting the capability to provide SNMP monitoring from collectd, further information [http://collectd.org/wiki/index.php/Plugin:SNMP here]. This requires the SNMP plugin to be installed. This plugin has a dependency on [http://www.net-snmp.org net-snmp]. Thanks, JB.",jukebox Active Tickets,1199,Allow selection of GEOM-based for iSCSI device extents,Backend,8.0.3-RELEASE,,enhancement,,new,2012-01-16T18:29:17Z,2012-01-17T00:46:36Z,"Currently, it appears that ""add extent"" will only let me select simple raw disk devices or ZVOLs; it would be great if I could also select GEOM-based devices here, e.g. a gmirror created from the command line.",razzfazz Active Tickets,1219,user unable to change password using the webconsole,GUI,8.0.3-RELEASE-p1,,enhancement,,reopened,2012-01-27T11:29:27Z,2012-01-27T18:44:15Z,"Hi, I am using freenas FreeNAS-8.0.3-RELEASE-p1-x64 (9591) , I find that their is no way for a user to change his password by himself using the web console (and also the command line). The only option seems to be for the admin to change the password for the user and keep the user updated on it . It would be good to allow the users to change their password using the web console as it then automatically updates the requisite files used by freenas and also survives a rebbot . Thanks & Regards, Suresh ",suresh Active Tickets,1235,shadow_copy support in samba is limited to single snapshot formats,Backend,8.0.3-RELEASE-p1,,enhancement,,new,2012-02-03T07:55:23Z,2012-02-03T07:55:32Z,"The code currently allows shadow_copy to function with ZFS snapshots with one snapshot format: {{{ 473 shadow: format = auto-%Y%m%d.%H%M-${task_rint}${task_runit} }}} So if I setup snapshots tasks with different policies (one which snapshots once a week and is valid for a month and another which snapshots once a day and is valid for a week), only the former case will be handled. 2 things need to happen: 1. samba needs to be enhanced to support multiple date formats. 2. middleware needs to be enhanced to produce input to smb.conf to handle multiple formats.",gcooper Active Tickets,1261,local master shouldn't be enabled when AD is enabled,GUI,8.0.3-RELEASE-p1,,enhancement,,new,2012-02-08T00:12:16Z,2012-02-08T00:12:16Z,"According to jhixson we shouldn't enable 'local master' in the GUI when AD is on. This can be easily controlled via ix-samba, but it would be a good idea to hide the option too.",gcooper Active Tickets,1265,Need mechanism for setting the time via the GUI/forcing ntpdate,GUI,8.0.3-RELEASE-p1,,enhancement,,new,2012-02-11T22:32:31Z,2012-02-11T22:32:31Z,"If the time skew grows large enough between the ntp server and the local time, ntpd won't update the local time. This causes issues with time sensitive protocols and tie-ins, like CIFS, AD/LDAP, etc. There needs to be an alternate way to either specify the time manually or force ntpdate to be run against the server.",gcooper Active Tickets,1271,Data Focused Share Creation,GUI,8.0.2-RELEASE,,enhancement,william,accepted,2012-02-12T11:30:20Z,2012-09-11T16:23:16Z,"Attached you find a PDF (to preserve formating) which describe my opinion on how to improve usuablity related ""share creation"" ",bubulein Active Tickets,1326,Need less obfuscated mechanism for specifying home directories,GUI,8.0.4-RC1,,enhancement,,new,2012-03-04T11:21:14Z,2012-03-04T11:21:14Z,"Currently home directory configuration magic is sort of handled via the CIFS global configuration area, but it really should be shuffled out into a general purpose user/authentication configuration area (hint: if it confuses Dru, you're probably doing something wrong!). It's not at all clear that specifying that implies that the pointer for /home should be directed to that location, until you dive into the code.",gcooper Active Tickets,1345,Need fine-grained logging channels,Backend,8.2.0-BETA1,,enhancement,,new,2012-03-04T19:11:02Z,2012-03-04T19:11:02Z,"One of the really slick things about IronPort appliances is their elegantly designed logging/alert system. In IronPort appliances you can setup multiple queues (hardware, updates, etc) and severity for the messages, along with deterministic subject tagging, such that multiple message queues could be used via the logging subsystem to funnel messages to appropriate email addresses. This is more of an enterprise feature than a SOHO feature, but I think it could be spun in such a way that SOHO users would benefit from it as well -- in particular, most folks care about volume health, but might not care about other pieces like the periodic emails, etc, whereas SOHO users might care about other things that enterprise users don't (transmission: ""can't contact the bittorrent tracker... fixme"" :)..). The current mechanism in FreeNAS unfortunately will not scale longterm and it needs to be improved / frozen in such a way that it's usable outside of the base system components.",gcooper Active Tickets,1347,Need better filtering mechanism with mfistatus.py,Backend,8.2.0-BETA1,,enhancement,,new,2012-03-04T19:38:50Z,2012-03-04T19:41:52Z,"There are some firmware ""critical level"" items that ultimately do not belong in the logs as it results in noise from an end-user perspective (example: fan failure noise for non-existent fans), and there are other messages that we might want to capture at other levels as well (fatal, some warn). A document is attached from SGI provided by LSI [1] which describes some of the different levels and messages available to developers that can be filtered out (see Appendix A). These messages might need massaging / fudging as they come straight from the firmware image and not directly from a driver, etc. We might need to obtain more up-to-date documentation from LSI in order to properly integrate our software into MegaRAID controllers (probably a good idea as iXsystems has a really good working relationship with LSI :)..). 1. http://techpubs.sgi.com/library/manuals/0000/860-0488-001/pdf/860-0488-001.pdf",gcooper Active Tickets,1366,Rethinking of disk choices in volume creation screen and proposed improvements,GUI,8.2.0-BETA1,,enhancement,,new,2012-03-07T01:08:07Z,2012-03-09T06:04:22Z,"Currently, the disks are sorted with sorted() which does not take capacity into account. For a system administrator, it would be quite handy if the disks are shown in a better way. For short term, it would be desirable to show disks by sorting them by their size first, then their device number, and finally their type (da, ada). For long term, it would be nice if we can have a smarter wizard which can guess a solution from the disks that present in the system (""easy button""). Here is a sample workflow of the code: - Traverse available devices and collect their sizes; - Sort disks by size, find the majority's size (e.g. if there are 9 x 3TB ada's and 2 x 320GB ada's, then the majority's size would be 3TB and the number of majority would be 9). - Find out optimal configuration from the disk number. This is essentially a form of Knapsack problem but we could use a pre-set table for small numbered ones (as disk numbers is limited by hardware, we could probably consider only cases when disks are less than 140). 1. For 1 disk, there is no choice and just use that one disk; 1. For 2 disks, offer mirror and stripped configurations; 1. For 3 disks, offer RAID-Z, 3 way mirror, 2 way mirror + 1 hot spare and stripped configurations; 1. For 4 disks, offer 2x2 way mirror, RAID-Z2, and 1 spare + 3 way RAID-Z configurations; 1. For 5 disks, offer RAID-Z, and 1 spare + 2x2 way mirror configurations; 1. For 6 disks, offer RAID-Z2, and 2x3 way mirror configurations; 1. For 7 disks, offer 1 spare + 6 way RAIDZ2 and 1 spare + 2x3 way mirror configurations; 1. For 8 disks, offer 4x2 way mirror configuration; 1. For 9 disks, offer RAID-Z, RAID-Z3, and 1 spare + 4x2 way mirror configurations; 1. For 10 disks, offer RAID-Z2, 1 spare + 9 way RAID-Z3 configurations; 1. For more than 10 disks, divide the disk numbers by 9 [raidz], 10 [raidz2], 11 [raidz3] and find the remainder, use the remainder as spare disks. - If the user choose not to use the pre-set configuration, they can use ""Custom"" to get to the current configuration window. In addition it would be valuable to teach the interface to give the user an estimation of ""How much space would be available if I go this route"".",delphij Active Tickets,1370,Active Directory Users in Account Management,GUI,8.0.4-RC1,,enhancement,,new,2012-03-07T16:59:41Z,2012-03-07T16:59:41Z,"I would like to be able to add an active directory user to a local user group in the account management system. ",uutzinger Active Tickets,1431,Add ability to specify more than one server to the AD/LDAP global config,Backend,8.0.4-RELEASE,,enhancement,,new,2012-03-29T22:47:31Z,2012-03-29T22:47:31Z,"A user has requested that the ability to specify more than one AD PDC or LDAP server be added to the GUI so in the event that the PDC tanks or is taken down for maintenance, the administrator can fallback to another server and access to the NAS/SAN can be maintained. Seems like specifying LDAP/PDCs can be done via the ""password server"" directive in smb.conf, but more work will probably need to be done for the AD_* macros in rc.freenas.",gcooper Active Tickets,1490,Configurable individual CHROOT for SFTP access,FreeBSD,8.0.4-RELEASE,,enhancement,william,accepted,2012-04-27T12:14:45Z,2012-06-28T14:32:05Z,"Hi, I´m used to connect and transfer files via SSH, since it's much more secure than SSL/TLS. When I SFTP connect with my login/password or auth keys there's no problem in seeing all NAS files because I'm it's owner, but when I decide to create a user for friends's SFTP access, I want them to be confined in their home directory. I know there are some ""extras"" that can be configured in SSHD GUI for that, but they didn't worked for me, and I tought that feature could be configurable in the USER GUI, not whole SSHD GUI for all users. I'm reporting on my actual 8.0.4, but it would be great to see this available on future versions, too.",loganderson Active Tickets,1537,local rsync option in FreeNAS 8,Backend,8.0.2-RELEASE,,enhancement,,new,2012-05-25T13:26:23Z,2012-05-25T13:26:23Z,"The legacy FreeNAS had a ""local"" rsync option that would allow you to automatically back up all newly created files (or do a full backup) to a physically connected internal or external drive. To me, this feature is extremely valuable since it's really a ""set it and forget it"" type of thing when it comes to automated backups. I'm stunned that this feature isn't present in FreeNAS 8 by now and quite honestly, it's the only thing that's keeping me from moving off the legacy FreeNAS. From the amount of questions I've seen in the forums for people asking how to use rsync to backup locally, I'm not the only one that's missing this feature.",axel_2078 Active Tickets,1577,Feature request: Add sanity check for volume member,GUI,8.0.4-RELEASE-p2,,enhancement,,reopened,2012-06-13T20:59:35Z,2012-11-23T20:41:17Z,"Currently there is no check done in the volume wizard to make sure that: a) A spare disk has to be equal or larger than the largest, existing disk, or, the largest disk in the new volume; b) A new group of vdev has to have same rows of existing vdevs; (*) c) Disk size within the same vdev should have same size; (*) It's desirable for users to ""force"" inconsistent but that's not a high priority feature.",delphij Active Tickets,1702,Active Directory/LDAP Authentication through webGUI/SSH,Backend,8.2.0-RELEASE-p1,,enhancement,jhixson,accepted,2012-08-03T01:52:35Z,2012-08-03T02:09:08Z,"The ability to authenticate both to the webGUI and SSH via Active Directory or an LDAP server would be a great feature to have. Ideally a feature much like ESXi has where you can type in a user or group to search.",tonysathre Active Tickets,1709,Option to disable usage of swap partitions,Backend,,,enhancement,,new,2012-08-06T12:53:00Z,2012-12-30T02:48:49Z,"There should be an option to disable the usage of swap partitions on individual member drives. I'm not talking about preventing their creation entireley which is already possible. I want to keep swap as a measure against varying disk sizes but I don't want the swap space mounted. That's because on a drive crash the swap becomes inaccesible and prevents the device from being properly closed as described in bug #493. When manually disabling swap with swapoff -a the hotswapping scenario described there works as expected. I'm for example imagining a ""Disable raw device swap usage"" switch in the Settings Advanced menu. In my opinion it would even be a good idea to make disabled swap the default. It's creation as a reserve is perfectly valid. But the system is unable to unmount/swapoff a lost device and thus blocks the drive slot with an unclosed device. This makes zero downtime hotswapping after a drive failure impossible. By disabling swap by default hotswapping would become possible which is a great benefit and highly needed for a professional NAS solution. Should anybody really need swap, which you probably don't on a NAS anyway, he could still toggle the switch and use the unsafe swap devices, which reside directly on the raw disk. Alternatively FreeNAS could be extended to offer safer solutions like Swap on ZFS or Swap on gmirror for systems that need swap but also don't want to loose hotswapping or risk system/application crashes due to drive failure. Swap on gmirror has already been mentioned in #208.",Shador Active Tickets,1724,Web interface should only allow logins from same subnet when password is empty,GUI,,,enhancement,,new,2012-08-14T21:48:38Z,2013-01-22T22:25:52Z,"It would be desirable to limit automatic login to the web GUI when password is not set, that the client must come from a ""local"" network, that is something like: permitted = False if not allow_remote_web_access_with_password: for x in configured_interfaces: # need IPv6 as well. if (client_ip & x.netmask == x.ip & x.netmask): permitted = True break else: permitted = True if permitted and admin_password = """": (allow to proceed)",delphij Active Tickets,1745,Add support for a boot-time USB key stick,Backend,,,enhancement,,new,2012-08-23T00:08:58Z,2012-08-23T00:08:58Z,"Make it possible to use a USB stick for unlocking encrypted disks, should the global key is not present. If on boot a volume is not present, a script is started which watches new disk attach event and tries to mount if the USB key have the expected format. The script mounts the USB key, attaches all encrypted disks, initiate the zpool import and unmounts the USB key, then play a few tones to indicate that the key is loaded, then it terminates. The alert system is extended to warn if the USB key is not removed for extended time. The Web interface is extended to add ""Export system-wide GELI key to USB stick"".",delphij Active Tickets,1817,Default Windows ACL,Backend,,,enhancement,,new,2012-09-29T19:28:38Z,2012-09-29T19:28:38Z,"Setting a Windows ACL type from the storage view in the web GUI and granting full permissions for owner, group and other results in the actual ACL not having full permissions outside of the owner. This can be verified using getfacl: {{{ [root@freenas] getfacl /mnt/fs01 # file: /mnt/fs01 # owner: root # group: wheel group@:rwxp--a-R-c--s:fd----:allow everyone@:rwxp--a-R-c--s:fd----:allow owner@:rwxpDdaARWcCos:fd----:allow }}} I'm not sure if this is by design as a security feature, or just an oversight, but there is no way to change this default behavior from the GUI or even know it's there. I've seen a lot of forum posts and had my own issues with CIFS access and use of ROBOCOPY with the /MIR switch because the everyone group doesn't have the ability to write extended file attributes (e.g. the time stamp) even though it can write and delete files. Using the following commands at the shell will fix the issue for any new files on a specified volume: {{{ [root@freenas] setfacl -m group@:rwxpDdaARWcCos:fd----:allow /mnt/fs01 [root@freenas] setfacl -m everyone@:rwxpDdaARWcCos:fd----:allow /mnt/fs01 }}} Since I haven't joined FreeNAS to a domain yet, I'm not sure if this would help as it would be possible to map users access differently, but for the home user this would be invaluable.",maglaubig Active Tickets,1851,ZFS Replication to Named ZFS Dataset,Backend,,,enhancement,,new,2012-10-21T16:57:28Z,2012-10-21T16:57:28Z,"Include capability to replicate to a ZFS Dataset that does not have the same name as the source ZFS Dataset. The web GUI allows the user to specify a remote ZFS file system name, however it doesn't translate it properly. In the docs ZFS Datasets are not mentioned specifically by name, perhaps this use case was not intended in the original design? In attempts to replicate from ZFS named src/local to a destination pool named dest/remote, the actual name the autorepl.py script attempts to use is dest/remote/local. Starting on line 85 in autorepl.py, there is some logic to check on and set the remotefs_final and remotefs_parent fields. Since it is not possible to select the root ZFS volume in the web GUI, the else clause is never used which would actually produce the desired result of this enhancement request. Specifically, setting both remotefs_final and remotefs_parent to the variable remotefs yields the desired result, snapshot names are the same as the local side on the remote side save for the beginning ZFS dataset name. In the testing I have done thus far with the modification detailed above, it works as expected but would need further regression testing. Lastly, it may be necessary to add a requirement that the destination must be a ZFS dataset and not a root ZFS volume.",maglaubig Active Tickets,1852,ZFS Restartable Replication,Backend,,,enhancement,,new,2012-10-21T17:11:10Z,2012-10-21T17:11:10Z,"Some WAN connections are not very reliable and as such, larger snapshots don't always complete a transfer for replication and must start over from the beginning on the next iteration of replication. Including an option for restartable replication could be employed at the cost of temporary disk space to hold a copy of a file generated with ""zfs send"" and the use of FTP or SFTP that allows for restartable transmissions. The FTP included with FreeNAS 8.3.0-BETA3 has such an FTP service, however it unknown to me if the same is true of SFTP, which would be a preferable transport method. Requirements to add would be a remote and local file system to store the file generated with ""zfs send"" with some possible checksum to ensure the file was transmitted successfully. Once the transfer is complete, apply the snapshot to the destination dataset, verify the task completed successfully and remove the file generated with ""zfs send"" from both the source and destination temporary file locations.",maglaubig Active Tickets,1894,Replication Speed over WAN,Backend,8.3.0-RELEASE,,enhancement,,new,2012-11-08T21:03:10Z,2012-11-09T17:50:13Z," == Short: == Replication setup via the GUI over a WAN is slow. == Long: == I've setup replication via the GUI for 3 different servers. 2 PUSH & 1 PULL(using your terminology from the Wiki). 1 PUSH server is local to the pull server and is able to clock over 800Mbs. The 2nd PUSH is remote and can only push 6Mbs(I've got a 100Mbs internet connection locals and remote is in a data center with multiple 40 Gbs fiber connections). I do nightly snapshots on the this server that produce about 50GB a data a night(so this isn't going to work out so good at 6Mbs). With this setup I'm using NAT on my pfSense appliance to hit FreeNAS. I do have the High Speed Cipher checkbox checked. TOP is showing virtually no CPU usage going on. If I manually replicate using NetCAT from the CLI and run it through my VPN tunnel that exists between the 2 networking going through the same pfSense appliances I'm able to average about 24Mbs, so that cuts out most networking issues. Here are the commands I'm using to do this: {{{ On Push: zfs send -i san/softlayer/esxi_store@auto-20121016.2000-2m san/softlayer/esxi_store@auto-20121017.2000-2m | nc 192.168.100.111 8023 On Pull: nc -l 8023 | zfs recv san/lancaster/backup/softlayer/esxi_store }}} Also is a set of pings show latency to the network. {{{ 64 bytes from 174.59.203.232: icmp_seq=0 ttl=51 time=60.951 ms 64 bytes from 174.59.203.232: icmp_seq=1 ttl=51 time=74.206 ms 64 bytes from 174.59.203.232: icmp_seq=2 ttl=51 time=65.651 ms 64 bytes from 174.59.203.232: icmp_seq=3 ttl=51 time=57.853 ms 64 bytes from 174.59.203.232: icmp_seq=4 ttl=51 time=77.802 ms 64 bytes from 174.59.203.232: icmp_seq=5 ttl=51 time=108.533 ms 64 bytes from 174.59.203.232: icmp_seq=6 ttl=51 time=95.087 ms 64 bytes from 174.59.203.232: icmp_seq=7 ttl=51 time=62.734 ms }}} == Work Around: == Ideally it would be great if netcat could be a check box option for going over secured networks. Esp because my local replication is going over a patch cable between the servers using 10Gb ethernet and I'm CPU bound on the SSH. ",pbucher Active Tickets,1910,Better TLS/SSL options for proftpd in FreeNAS web GUI,Backend,8.3.0-RELEASE,,enhancement,william,accepted,2012-11-20T18:33:08Z,2012-11-21T10:50:21Z,"I have just implemented FTPeS with FreeNAS and there were a few things I had to resort to the command line to get it working properly. 1) This is probably a bug, but when I first checked the enable SSL box it didn't auto generate a certificate. Hence proftpd failed to start. Going back into the settings and unchecking, saying OK, turning off proftpd, enabling SSL checkbox then starting up again fixed this. 2) ftprush and several other clients don't support FTP SSL sessions, meaning the directive ""TLSOptions NoSessionReuseRequired"" had to be set. This should be configurable from the web GUI, perhaps under advanced mode if you don't want to concern users about its meaning. 3) Many FreeNAS servers are generally underpowered old desktops or laptops. Hence, enabling SSL for anything beyond login might be unnecessary. I like to secure the AUTH because when using local user authentication my Active Directory password is being sent. BUT for large binary file transfers on the LAN, I'm not too concerned about the data being encrypted. You can significantly speed up transfers by setting: TLSRequired Auth (http://www.proftpd.org/docs/directives/linked/config_ref_TLSRequired.html) This requires only the authentication be encrypted, allowing data to transfer in plaintext (tripling throughput and reducing CPU utilisation by a factor of 5 in my case). Set as major-Backend due to point 1) appearing to be a bug.",deed02392 Active Tickets,1982,Update to samba 4,Build System,8.3.0-RELEASE-p1,,enhancement,,new,2013-01-02T11:28:25Z,2013-03-25T11:29:37Z,"As samba 4 is out, can you include/upgrade with AIO support it to the next release of Freenas ? Thanks in advance ",DarkPower Active Tickets,2044,Grow file extents and iSCSI process dynamically recognize the change,Backend,8.3.1-BETA3,,enhancement,,new,2013-02-15T20:57:45Z,2013-02-18T12:18:24Z,"I was setting up some iSCSI clients and needed to increase the volume sizes they were originally allocated. I made the change in the FreeNAS server GUI to each of the file extents and re-scanned on the clients hoping that would work. It did not, it wasn't until I stopped and start the iSCSI service that the change to the file extends were picked up by the iSCSI service. It was nice that it eventually worked but had a bad side effect. The issue is all clients are disconnected from there iSCSI target losing there disk.",rfutch Active Tickets,2071,configuration of hardware watchdog,Backend,,,enhancement,,new,2013-03-03T12:49:17Z,2013-03-03T12:49:17Z,"Got a hard freeze from a freenas remote machine and realized how handy hardware watchdog support could be. So having this functionality and the ability to configure it from the web gui would be nice. Reference on how to configure it manually: http://koitsu.wordpress.com/2010/07/13/freebsd-and-hardwaresoftware-watchdogs/",rm Active Tickets,2077,Show/log NFS users and activity,Backend,,,enhancement,nfs,new,2013-03-08T19:42:16Z,2013-03-08T19:42:16Z,"Feature request for a means to record information related to NFS mounts. Specifically, we would like the ability to record all access, duration of access, and transfer information for analysis and reporting purposes.",jsa Active Tickets,2140,Enabling pf causes a kernel panic,FreeBSD,8.3.1-RELEASE,,enhancement,,new,2013-04-18T13:43:15Z,2013-04-18T13:43:15Z,"We would like to use a firewall on a remote FreeNAS server (FreeNAS-8.3.1-RELEASE-p2, 64-bit). The pf.ko module is loaded successfully but loading any pf rules causes a kernel panic. It is very easy to reproduce this panic, just try to load any pf rules. ",krassi Active Tickets,2147,FreeIPA v3 + FreeNAS w/CIFS?,Backend,8.3.1-RELEASE,,enhancement,jhixson,accepted,2013-04-23T21:56:53Z,2013-04-24T10:47:43Z,"Hi. I administer an environment in which I use FreeIPA v3 (aka Red Hat Identity Management) as my SSO solution. While most of my hosts are Linux, a few are Windows and Mac. I'm hoping to configure FreeNAS to authenticate CIFS to the LDAP + Kerberos exposed by FreeIPA, preferably without modifying the LDAP structure. Here is some documentation from their side: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/Identity_Management_Guide/#cifs Please consider this a feature and/or documentation request on how to authenticate FreeNAS (with CIFS) to FreeIPA v3. Thanks, Joshua",josh-wrale Active Tickets,2161,web GUI access control,GUI,8.3.1-RELEASE,,enhancement,,new,2013-04-29T18:49:51Z,2013-04-29T18:49:51Z,"1. ip prefix filter on WebGUI (necessarily on Internet facing interface) 2. disable port 80 302 redirect if only https is enabled and the port has been changed (or it just defeats the purpose of changing the port and causes SSL error) 3. listen on IPv6 address",realdreams Active Tickets,2163,Move add user link to the top of users menu,GUI,8.3.1-RELEASE,,enhancement,,new,2013-04-30T17:08:21Z,2013-04-30T17:11:09Z,"I have more then 80 users on server and I everytime need to scrol down the list of users ro reach the ""add user"" link or button (in users page). The most frequent operation is adding a new user rather than editing it.",beezone Active Tickets,2177,Export DVD-R burner,GUI,8.3.1-RELEASE-p2,,enhancement,,new,2013-05-11T21:21:50Z,2013-05-20T11:43:24Z,"I have looked around the web and the forums and I can't find a clear answer to make this happen. I have a lot of notebooks that connect wirelessly to my freenas appliance I built. Many notebooks now do not have optical drives. I have a DVD Burner installed in my Freenas appliance. Is there any way to make it so I can share that DVD Drive to the machines on my network? If not, would this be happening any time in the future with an update? I think it would be great to just have a central optical drive for my machines, rather than having to lug around external optical drives for the notebooks. Also I do have a few Macs that no longer have optical drives. That feature would be useful for those as well. Thanks!",pichu Active Tickets,1098,"2 FreeNAS units, 2 seperate locations, Snapshot writing not keeping up",Backend,8.0.2-RELEASE,,task,Eiric,new,2011-12-14T13:41:54Z,2011-12-14T13:41:54Z,"Good morning. I have 2 identical machines, both running FreeNAS 8.02/64 bit. Each machine has 32GB ram, 24TB of disk space, Intel(R) Xeon(R) CPU E5504 @ 2.00GHz. 101 has 6 NICS and 102 has 4 NICS. 101 and 102 are the machine names. When they are in the same building, everything runs great. Snapshots get taken on 101 and written to 102 in a timely fashion. Of course, they are in the same 1GB network. When we move 102 offsite to it's permanent location, the snapshot will not keep up. There is less bandwidth at the permanent location, but the system maintains a 4 MB/sec speed. We are taking snap shots every 15 minutes, most fall into the less than 1 MB size, with the exception a few that can be much larger. My questions is, is there a better way to link the machines together then over a VPN to ensure the files transfer quickly? Thanks for your assistance. ",eshriner Active Tickets,1540,Unable to import UFS mirror after crash (dirty volume),GUI,8.0.4-RELEASE,,task,,new,2012-05-29T03:16:48Z,2012-05-31T05:56:44Z,"The USB stick holding my install failed and the system locked. Restarting with a fresh install on a new stick worked. However, now the volume (two mirrored ufs drives) is dirty and will not auto import. Documenting in the GUI help file how the data on the volume can be recovered is important. ",rammerplex Active Tickets,2006,Wireless driver,Build System,8.3.1-BETA2,,task,,new,2013-01-17T10:56:16Z,2013-03-17T21:38:53Z,"Hello, Is it possible to add wireless driver to Freenas 8? I want to use my wifi card as wireless access point. Indeed, it could be useful to have access to the NAS via wireless. If this is not possible, how can I add the driver by myself if_run.ko. Sincerely, Julien",MotorSport Active Tickets,26,Need an initial setup wizard,GUI,,8.0-RELEASE,enhancement,gcooper,accepted,2010-11-17T18:12:49Z,2011-08-25T00:13:49Z,"We should have an initial setup wizard. This wizard would walk you through things like the windows setup wizard does. What time zone, IP info, passwords, etc. It should then generate the proper entries in all the database tables.",bsdimp Active Tickets,91,Hybrid Flash+HD install option,Backend,,8.0-RELEASE,enhancement,,new,2010-12-14T12:39:15Z,2012-11-20T00:19:35Z,"''While installing FreeNAS, we should be allowed to install it on multiple Disks and/or Partitions (like most Linux installers currently do):'' It should be possible (and easy) to install ""/"" on an (USB or compact) flash disk while having ""/var/"" , ""/tmp/"" and Swap installed on Hard Drive Partitions. The GUI should then allow to easely: - reinstall either the flash device, either the Hard Drive - backup/restore configuration(s) between the flash device and the Hard Drive This would allow to get an almost indestructible system on an (easely interchangeable and update-able) flash disk, while keeping files that need frequent and fast accesses, on the Hard Drive. The goal is no have a NAS that you can ""setup and forget"" while stilll being able to easely and fastly repair when anything goes wrong (update brokes everything, hard disk failures, bad plug-in...). This is even more important if you include home-automation plug-ins, as recently announced! ''(Sorry for my English)''",wxop Active Tickets,759,Error trying to import USB msdos (FAT) and NTFS devices,Backend,8.0.1-RC2,8.0.1-RELEASE,defect,,new,2011-09-09T03:55:04Z,2011-10-23T07:01:19Z,"When trying to import a FAT32 formatted 1GB USB Flash drive, da4s1, I get error in GUI saying ""Some error ocurred while labelling the disk."" I can't seem to find anything in /var/log/messages or console. What is the error, why can't the disk be imported?",protosd Active Tickets,792,FreeNas Halts/stops transfer halts,FreeBSD,8.0.1-RC1,8.0.1-RELEASE,defect,,new,2011-09-17T17:58:20Z,2011-12-19T07:32:26Z,"[13:32] hey guys, I was transfering ~8tb of data last night (Freenas RC1 64BIT) from 6 Windows boxes --> Freenas via CIFS. I got an error, same as I got yesterday when I was xfering some files from two computers as well. yesterday I believe it was the same type of error but I did not write it down. [13:32] Swap Pager : indefinite unit buffer:bufobj:0,blkmo:3671427, size:16384 [13:33] I tested ram last night, it isnt that. One common factor that I noticed : on both occasion, one of the windows box had a copy halted because it asked if I was sure I wanted to copy this file without its properties (the file has properties that can't be copied to the new location it said) [13:34] my guess is that the windows boxes halts the xfer for a response from us to continue the xfer, but then since it takes a long time for me to respond to that dialog, something must go wrong on the freenas end? like it's waiting for it to resume or it keeps the connection up but then sees no activity and it crashes? [13:35] it transfered flawlessly 3TB of data before halting. Right now, the box is still up, it didn't reboot, it is also still reachable via the network but all xfers from all boxes seemed to have halted at the same time. I couldn't do a ""try again"" on the xfer, but if I close the dialog then used a prog to compare what was left to transfer (examdiff) it allowed me to transfer again without a reboot. The Windows boxes are windows 7 with pretty much all updates up to date. Freenas shares/ownership is set to NOBODY and allowing blank password/guests access for easy sharing. connecting to freenas via a mapped drive on windows 7 mounted via the static ip I set for freenas. network is on a domain (windows 2008). the gateway is a PFSense, dns are handled by domain. I hope I provided you with all the avail info for debugging, but if not, feel free to ask Oh, the freenas is on a Core2Duo I believe, 4 GB ram. the volume is consisting of 2 stripped 4X2.5TB RaidZ ",magnatique Active Tickets,1214,fatal trap at shutdown at 8.0.3 p1,FreeBSD,8.0.3-RELEASE-p1,8.0.3-RELEASE-p1,defect,,new,2012-01-25T11:16:22Z,2012-12-10T23:51:47Z,"hello, I face this fatal trap since 8.0.2 and 8.0.3. Now with 8.0.3 p1 is still happening( see enclosed photo). It is ramdom and not all times appears at shutdown. Normally if the HDDs are sleeping and I shutdown the system it could appears. But what appears all the time is the second line of the photo in diferent HDD: (ada1:ata3:0:0:0): Spin-down disk failed some times finish shutting down and other times it hangs. Apart of last error, I receive 4 mensages ""ataidle: the device does not support advanced power management"" but I have 8 HDD. 4 HDD´s are connected to one promise and the other 4 to the other promise card. My HW is: motherboard Asus P4p800 with latest BIOS 4GB memory 2x promise sata300 TX4 4x seagate 1,5 TB (with latest fw) 4x seagate 2tb OS at usb stick, Freenas i386 version ",glich Active Tickets,1467,Snapshot replication issues,Backend,8.0.4-RELEASE,8.0.4-RELEASE,defect,,new,2012-04-18T09:33:36Z,2012-04-23T15:14:08Z,"My main production machine is replicating it's snapshots to another machine running an identical FreeNAS version. While the pre-production tests worked great and the replication worked flawless until a scrub came in and I had to forcefully close the remote replication process in order to save IOPS on the production machine, following that the replication never worked again as it should. The production stopped exporting the snapshots until I've selected ""Initialize remote side for once"" option. It did initiated successfuly, yet I had to cancel it one more time as the production machine was not coping out with exporting the datasets, serving usual I/O for the VPS nodes and be the target for the nightly backups. I've switched the snapshot export target machine's switchport to 100Mbps, selected the ""Initialize remote side for once"" and the export started OK but it took almost 4 days to transfer about 5TB to the target machine over the 100Mbps line. After it was complete, the initial snapshots from the production machine were there alright but no replication was performed follwoing the initial one. Without this bugfix the only way to have everything like it was before is to buy a new server, offload the current production server to the new one, setup the replication over 1Gbps line and roll back the VPS's from the new one. However I think that a minor fix could spare me from doing that.",newhost Active Tickets,1470,ability to create a bridged network,GUI,8.0.2-RELEASE,8.0.4-RELEASE,enhancement,,new,2012-04-18T22:15:37Z,2012-04-18T22:15:37Z,"I just installed more network cards in a Freenas 8.0.4, and followed this how-to http://atwin.blogspot.com.br/2010/12/using-freenas-80-as-bridge.html to bridge all network interfaces in one, and it works just fine, but all work are lost after a reboot ! This feature could be very useful, create bridged networks within web interface, so everything gets saved and persists after a reboot !",madtrek Active Tickets,359,FreeNAS 8 do not use a spare HDD in RAIDz2 for replacing a failed HDD on the WebUI,Backend,8.0-RELEASE,8.2.0-RELEASE,defect,,new,2011-05-18T00:00:43Z,2011-12-16T20:35:24Z,"FreeNAS 8 seems not to use a spare HDD in RAIDz2 for replacing a failed HDD on the WebUI. I write down my operation and results in order. After that I propose 2 improvement plans. 1) I created a zfs RAIDz2 pool with 7HDDs(for RAIDz2), 2SSDs(for cache and logs)and 1HDD for spare. All storage is connected by SATA, AHCI mode. And I set ""-m root"" to ""S.M.A.R.T. extra options"" on the WebUI. 2) After creating the pool, I remove a HDD(for RAIDz2) from a hot-swapable bay instead of the HDD failure. 3) Reading/writing the pool, I checked zpool status command on SSH. The zpool status of the removed HDD indicated that read/write errors are increasing, still the removed HDD state is ""ONLINE"". 4) After that smartd daemon sends a report mail indicating ""unable to open device"" error, still the removed HDD state is ""ONLINE"". 5)Next day, zpool status of the pool became ""DEGRADE"" but the spare HDD was not used.(I guess that daily scrub job detected the removing HDD.) 6)I tried to replace the removed HDD to the spare HDD on the WebUI. But I couldn’t. Only the WebUI showed that pool is degrade and ""View Disks"" page is the same before removing HDD. There were no ways to replace the removed HDD to the spare HDD on the WebUI. I think that No.3-5 result is limitation/feature of zfs and FreeBSD. But I believe No.6 is a FreeNAS' bug. Improvement plan 1 (better function and higher cost, I hope this plan.) Implementing an error detection mechanism like Solaris FMA for automaticaly-replacing. This plan will bring high-availability, and it is user-friendly. And implementing cost is higher. Improvement plan 2 (minimum function and lower cost) Implementing a suggestion function to replace a failed HDD. And implementing a replace function to use the spare HDD from WebUI. This plan is minimum function for using zfs spares on WebUI. And implementing cost is lower than plan 1.",Order Foots Active Tickets,656,ntp server failures not reported in alerts,Backend,8.0-RELEASE,8.2.0-RELEASE,defect,,new,2011-08-26T19:36:32Z,2011-08-31T19:30:44Z,"Procedure: - Ensure that the system is in a healthy state. - Follow setup steps in ticket # 655. Alternatively, ntp.conf should be modified to point to a different (nonexistent) NTP server. Expected result: - Alerts related to setting up NTP server should be logged in the alerts subsystem. - The stop-light should change from green to yellow. Obtained result: - The alert isn't logged. - The alert stop-light doesn't change from green to yellow.",gcooper Active Tickets,688,Performance hit when adding/modifying users and groups in GUI,Backend,8.0.1-BETA4,8.2.0-RELEASE,defect,,new,2011-08-27T02:31:21Z,2011-08-27T02:31:21Z,"There's a performance hit (several seconds) in the most recent betas when adding / modifying users and groups because several of the services are being explicitly restarted (with some fixed sleeps between) in order to work around interoperability issues. This needs to be fixed so that the GUI no longer hangs when committing operations, as this can leave the system in an unusable / funky state if impatient users cancel operations mid-stream.",gcooper Active Tickets,773,Store NFS share information in ZFS,Backend,8.0.1-RC1,8.2.0-RELEASE,defect,,new,2011-09-12T20:33:24Z,2011-09-12T20:33:24Z,"ZFS supports attribute 'sharenfs'. Ideally, NFS shares on a ZFS dataset should be stored in ZFS itself rather than in database. Proposed change: - When a NFS share is being added, test if the path is a ZFS dataset (note: NFS shares should reject non-mountpoint shares). If so, issue a 'zfs set sharenfs="""" ' command; in database, a magic value or a flag is used to indicate that the field is actually stored in ZFS - When a NFS share is being viewed, test if the field have the magic value and grab data from ZFS; - When a NFS share is being changed or removed, make corresponding change in ZFS;",delphij Active Tickets,782,Feature request: ZFS dataset rename,Backend,8.0.1-RC1,8.2.0-RELEASE,defect,,new,2011-09-15T08:27:07Z,2012-08-10T01:03:53Z,"Inspired by #261, ZFS dataset rename should be implemented. (Note: this should invoke a remote rename if replication is enabled, or at minimum, corresponding replication should be invalidated; services referencing the dataset should be notified when this happen).",delphij Active Tickets,1091,FTP aborting transfer: Broken pipe,FreeBSD,8.0.2-RELEASE,8.2.0-RELEASE,defect,,new,2011-12-13T00:03:52Z,2011-12-13T00:04:31Z,"I have the same error as this : https://sourceforge.net/tracker/?func=detail&aid=3139564&group_id=151951&atid=782616 OS Version: FreeBSD 8.2-RELEASE-p1 USER guestftp: Login successful. Dec 13 02:57:15 freenas proftpd[2807]: localhost (::ffff:192.168.1.1[::ffff:192.168.1.1]) - notice: user guestftp: aborting transfer: Broken pipe Dec 13 02:57:24 freenas proftpd[2848]: localhost (::ffff:192.168.1.1[::ffff:192.168.1.1]) - USER ftp: no such user found from ::ffff:192.168.1.1 [::ffff:192.168.1.1] to ::ffff:192.168.1.34:21 Dec 13 02:57:24 freenas proftpd[2849]: localhost (::ffff:192.168.1.1[::ffff:192.168.1.1]) - USER guestftp: Login successful. Dec 13 02:57:27 freenas proftpd[2852]: localhost (::ffff:192.168.1.1[::ffff:192.168.1.1]) - USER ftp: no such user found from ::ffff:192.168.1.1 [::ffff:192.168.1.1] to ::ffff:192.168.1.34:21 ",lexeek Active Tickets,1234,Replace Disk fails from GUI in 8.0.3-p1 due to inconsistent swap partition size,GUI,8.0.2-RELEASE,8.2.0-RELEASE,defect,william,accepted,2012-02-03T03:58:46Z,2012-02-10T22:16:29Z,"Replace disk from GUI fails without explanation when using identical 2TB disk. After doing replace disk from GUI, there is no apparent resilvering activity taking place or message in the GUI about the failure. After trying replace command from the command line, I got the error ""disk is too small"". When doing a gpart show, I discovered the problem was that 8.0.3-p1 created a 2GB swap partition as opposed to the 1GB swap partition that was created when I initially created my pool from the GUI in version 8.0. So it seems that the GUI needs to check existing swap partition size and makes sure it creates the new one consistent with the size on the other disks. I manually wiped the disk and recreated the partitions and did the replace from the command line using the same command that was issued from the GUI in the log file. Here is the forum thread with log files etc. [http://forums.freenas.org/showthread.php?5810-Replace-Disk-fails-from-GUI-in-8-0-3-p1&p=21033#post21033]",protosd Active Tickets,1270,Don't Waste Screenspace,GUI,8.0.3-RELEASE-p1,8.2.0-RELEASE,defect,,new,2012-02-12T09:52:17Z,2012-02-12T09:52:17Z,"Even these day's screen space should not be wasted,I'm Still using a 17"" for example.",bubulein Active Tickets,1525,istgt socket wedge,Backend,8.2.0-BETA2,8.2.0-RELEASE,defect,,new,2012-05-16T13:32:00Z,2012-05-16T13:32:00Z,"When using istgt with ZFS, I have had problems with the istgt becoming wedged requiring a hard reboot. As the process will not respond to a kill, nor will it clear tcp connections that have somehow become wedged. Found this patch: http://osdir.com/ml/freebsd-scsi/2012-03/msg00034.html I have seen others report this type of problem, but no real solution. Seems to happen more if there is a hardware drive problem, bad lba, or if smart is running. I also see that the sockets get stuck in a closed state and will continue to pile up. I have several hundred stuck in the closed state.... The process state is stuck in ""uncond"" 1583 root 688 44 0 1631M 76072K ucond 0 30:06 0.00% istgt 2379 root 7 44 0 75604K 13284K ucond 2 0:30 0.00% collectd tcp4 0 0 192.168.149.147.3260 192.168.149.130.51982 CLOSED tcp4 0 0 192.168.149.147.3260 192.168.149.130.51981 CLOSED tcp4 0 0 192.168.150.147.2323 192.168.128.200.65246 ESTABLISHED I have not tested the above patch yet but it may make it possible to at least kill the process. ",MDP Active Tickets,1596,FreeNAS 8.04 not handling ACLs quite right,Backend,8.0.4-RELEASE-p2,8.2.0-RELEASE,defect,,new,2012-06-21T14:28:27Z,2012-07-24T19:24:06Z,"Short version, recursive robocopy from FreeNAS CIFS share joined to domain including permissions fails. Same process worked in 8.02 See http://forums.freenas.org/showthread.php?7564-Something-Subtle-Breaks-in-ACLs-after-upgrade-from-8-02-to-8-04 for more background. Recreate by simply putting a folder full of files onto share, then copy back off via {{{ robocopy \\freenas\share\ C:\Users\Administrator\Desktop\test /copyall /mir /fft /r:1 /w:1 /v }}} Results in {{{ ERROR 5 (0x00000005) Copying NTFS Security to Destination Directory }}}",furicle Active Tickets,1679,LACP lagg with 4 interfaces broken,FreeBSD,8.2.0-RELEASE-p1,8.2.0-RELEASE,defect,,new,2012-07-25T19:41:24Z,2012-11-25T22:04:19Z,"After getting a LACP lagg with two interfaces working, I decided to add my remaining two interfaces to the lagg, bringing the total to four. The relevant portions of ifconfig, after adding the intf's and rebooting is as follows: {{{ igb0: flags=8843 metric 0 mtu 1500 options=1bb ether 00:25:90:6b:80:46 media: Ethernet autoselect (1000baseT ) status: active igb1: flags=8843 metric 0 mtu 1500 options=1bb ether 00:25:90:6b:80:46 media: Ethernet autoselect (1000baseT ) status: active em0: flags=8843 metric 0 mtu 1500 options=219b ether 00:25:90:6b:80:46 media: Ethernet autoselect (1000baseT ) status: active em1: flags=8843 metric 0 mtu 1500 options=219b ether 00:25:90:6b:80:46 media: Ethernet autoselect (1000baseT ) status: active lagg0: flags=8843 metric 0 mtu 1500 options=19b ether 00:25:90:6b:80:46 media: Ethernet autoselect status: active groups: lagg laggproto lacp lag id: [(8000,00-25-90-6B-80-46,00D0,0000,0000), (8000,00-24-C4-74-59-00,0006,0000,0000)] laggport: igb1 flags=1c state=3D [(8000,00-25-90-6B-80-46,00D0,8000,0002), (8000,00-24-C4-74-59-00,0006,8000,0009)] laggport: igb0 flags=1c state=3D [(8000,00-25-90-6B-80-46,00D0,8000,0001), (8000,00-24-C4-74-59-00,0006,8000,0008)] laggport: em1 flags=1c state=3D [(8000,00-25-90-6B-80-46,00D0,8000,0004), (8000,00-24-C4-74-59-00,0006,8000,0007)] laggport: em0 flags=1c state=3D [(8000,00-25-90-6B-80-46,00D0,8000,0003), (8000,00-24-C4-74-59-00,0006,8000,0006)] vlan147: flags=8843 metric 0 mtu 1500 options=3 ether 00:25:90:6b:80:46 inet 10.209.147.58 netmask 0xffffff00 broadcast 10.209.147.255 media: Ethernet autoselect status: active vlan: 147 parent interface: lagg0 vlan145: flags=8843 metric 0 mtu 1500 options=3 ether 00:25:90:6b:80:46 inet 10.209.145.57 netmask 0xffffff00 broadcast 10.209.145.255 inet 10.209.145.58 netmask 0xffffff00 broadcast 10.209.145.255 media: Ethernet autoselect status: active vlan: 145 parent interface: lagg0 vlan146: flags=8843 metric 0 mtu 1500 options=3 ether 00:25:90:6b:80:46 inet 10.209.146.58 netmask 0xffffff00 broadcast 10.209.146.255 media: Ethernet autoselect status: active vlan: 146 parent interface: lagg0 }}} You can see that all four interfaces are active in the lagg. My Cisco Catalyst 4948 also reports all four interfaces active in the 'bundle'. So, everything looks fine. However, the problem is that when all four interfaces are live, network connectivity is incomplete - some source IP's can talk to only some IP's on the FreeNAS. Using any combination of switch ports and NIC's, if there are four active interfaces, things are busted. If only three are active, things work fine. Here's the output of ifconfig when only 3 of the 4 interfaces are up (the scenario that works): {{{ lagg0: flags=8843 metric 0 mtu 1500 options=19b ether 00:25:90:6b:80:46 media: Ethernet autoselect status: active groups: lagg laggproto lacp lag id: [(8000,00-25-90-6B-80-46,00D0,0000,0000), (8000,00-24-C4-74-59-00,0006,0000,0000)] laggport: igb1 flags=1c state=3D [(8000,00-25-90-6B-80-46,00D0,8000,0002), (8000,00-24-C4-74-59-00,0006,8000,0009)] laggport: igb0 flags=0<> state=41 [(8000,00-25-90-6B-80-46,8001,8000,0001), (FFFF,00-00-00-00-00-00,0000,FFFF,0000)] laggport: em1 flags=1c state=3D [(8000,00-25-90-6B-80-46,00D0,8000,0004), (8000,00-24-C4-74-59-00,0006,8000,0007)] laggport: em0 flags=1c state=3D [(8000,00-25-90-6B-80-46,00D0,8000,0003), (8000,00-24-C4-74-59-00,0006,8000,0006)] }}} I'm almost certain that my switch is configured properly and we another four-member LACP lagg working fine with a Windows host. Here's the relevant switch config bits: {{{ interface Port-channel6 switchport switchport trunk encapsulation dot1q switchport mode trunk ! interface GigabitEthernet1/5 description to gtfiler2 switchport trunk encapsulation dot1q switchport mode trunk speed auto 10 100 1000 channel-protocol lacp channel-group 6 mode active spanning-tree portfast ! interface GigabitEthernet1/6 description to gtfiler2 switchport trunk encapsulation dot1q switchport mode trunk speed auto 10 100 1000 channel-protocol lacp channel-group 6 mode active spanning-tree portfast ! interface GigabitEthernet1/7 description to gtfiler2 switchport trunk encapsulation dot1q switchport mode trunk speed auto 10 100 1000 channel-protocol lacp channel-group 6 mode active spanning-tree portfast ! interface GigabitEthernet1/8 description to gtfiler2 switchport trunk encapsulation dot1q switchport mode trunk speed auto 10 100 1000 channel-protocol lacp channel-group 6 mode active spanning-tree portfast ! }}} I don't know if this is a FreeNAS-specific problem, though I doubt that it is. Any ideas? ",tomrich82 Active Tickets,1681,HDD standby does not work if plugin-jail is running,FreeBSD,8.2.0-RELEASE-p1,8.2.0-RELEASE,defect,,new,2012-07-26T09:11:15Z,2013-01-15T14:39:58Z,"I have the following setup (running on a x64 machine): /mnt/tank (consisting of 3 Seagate disks in a raidz) /mnt/tank/pub (data set for all my stuff) /mnt/tank/jail (data set for plugins/jail) /mnt/tank/software (data set for plugins/jail) /mnt/tank/pub is exported via nfs and cifs and there is one plugin mount point to access stuff from pub in the jail. The three disks are configured to go to standby after 5 mins, which worked perfectly. Jail/Plugins (in my case MiniDLNA) work perfect, but if the jail is running - even if the MiniDLNA plugin is disabled - my disks do not spin down any more. If I then stop the jail, the disks go to standby as intended. I'm not sure if it is a ""bug"" or if it can be fixed, but it kinda sucks that the disks are spinning all the time.",nox Active Tickets,71,add partitioning,Backend,8.0 Beta (r5606),8.2.0-RELEASE,enhancement,,new,2010-11-30T17:23:44Z,2011-02-10T10:49:24Z,Please add partitioning of disk to the GUI. It'd be nice if I can nfs-export to different host/subnets with different privileges. Also it'd be nice if I can make raidz only on part of my disks - not on whole devices.,tmf Active Tickets,116,Mount management missing in web GUI,GUI,8.0 Beta (r5698),8.2.0-RELEASE,enhancement,,new,2011-01-02T14:19:32Z,2011-09-29T01:14:59Z,"There is no mount management in the web GUI, which is an important feature regression/lack (cannot mount usb drives)",sfchris7 Active Tickets,333,Creating SAMBA NT-Domain,Backend,8.0-RELEASE,8.2.0-RELEASE,enhancement,,new,2011-05-08T15:47:02Z,2011-05-08T15:47:02Z,"Thanks to iX for this great release; for replacing a server machine in small workgroups it would be a great thing to authenticate users and machines (NT-Domain, create machine acocunts)to store profles and support CUPS (RAW printing would be nice). logan54",logan54 Active Tickets,613,Save / Restore settings from console,Backend,8.0.1-BETA4,8.2.0-RELEASE,enhancement,,new,2011-08-16T03:04:55Z,2011-09-29T01:14:31Z,There may be certain situations where access to the GUI may not be possible and it would be useful to restore settings saved from the GUI or backup settings from the console,protosd Active Tickets,626,Automatic update system,Backend,8.0-RELEASE,8.2.0-RELEASE,enhancement,delphij,new,2011-08-19T04:55:51Z,2011-09-29T02:25:00Z,"It's desirable to make the system be able to download updates automatically and use the notification system ('alert.py') to notify the fact that there is update available. Required components: - Description about the update (new version, size, sha256) plus signature - Downloader (transmission-daemon? plus SF based HTTP?) - Validator Operation: - Daily or weekly periodic check update availability; - When update is available, add a torrent to transmission-daemon task, or fetch the file directly if a small service pack, or specified by user; - The system uses a hourly cron job to check the availability, which is added at the time of adding the task; - When download complete, validate and copy the file to a pre-defined temporary place and give user notification; - ""Install downloaded update"" would do update with the downloaded and validated update file. This feature should be off by default. [System summary should have an update checker as well?]",delphij Active Tickets,770,Kernel core support,FreeBSD,8.0.1-RC1,8.2.0-RELEASE,enhancement,,new,2011-09-12T18:22:46Z,2011-09-12T21:22:42Z,"It's impossible debugging some situations where the kernel goes south in customer configurations if there's a kernel bug, the system runs out of memory due to a rogue process, etc. We really need support for kernel coredumps. This would require the following items: 1. Swap support is required. 2. A persistent backing store needs to be provided, in lieu of /var/crash . Minidumps should be sufficient for most issues.",gcooper Active Tickets,861,Support for Adaptec RAID card driver 6405,Build System,8.0.1-RELEASE,8.2.0-RELEASE,enhancement,,new,2011-10-01T10:45:57Z,2011-10-02T02:41:39Z,"Hi, Can you include the drivers for the Adaptec RAID card 6405 in the distribution. The drivers are available on the adaptec website http://www.adaptec.com/en-us/downloads/unix/freebsd/productid=sas-6405&dn=adaptec+raid+6405.html. I have currently have the RAID card working on the latest 8.0.1RC2 after manually adding the driver. Thanks Paul",spe109 Active Tickets,986,Need a watchdog feature for replication runs,Backend,8.0.2-RELEASE,8.2.0-RELEASE,enhancement,,new,2011-11-08T00:20:13Z,2012-12-12T04:36:03Z,"Reported by iXsystems. Currently the replicator skips replication if it detects that a replication is already running. However, if the remote side stuck (but not dead), the local side zfs send would never get a chance to end and no warning is issued. The replicator needs to check how long the existing instance have been started and issue warning in an hourly (or user configurable) manner until the replicator disappeared.",delphij Active Tickets,1132,Enable UFS SU+J by default?,Backend,8.0.2-RELEASE,8.2.0-RELEASE,enhancement,,new,2011-12-27T21:38:32Z,2011-12-27T21:38:32Z,As title. We need to consider once we migrated to FreeBSD 9.0 base as it would almost eliminate the on boot fsck.,delphij Active Tickets,1256,Online Upgrade,GUI,,8.2.0-RELEASE,enhancement,,new,2012-02-06T19:45:08Z,2012-02-06T19:50:27Z,"Would be nice to have the posibillity for ""online upgrades"". Like: Select available versions, download image in sha, backup config, install, restore config... == Gooddies == Storing the config with every version, so switching between several version is just a boot away. Would make support much nicer, also there will be some kind of config versioning.Rollbacks are more comfortable. A list below the ""Upgrade"" with custom comments would make it perfect. Perhaps I sometimes expect to much, but as long there are so many hackers available why not trying to push as much as possible :)",bubulein Active Tickets,1293,@reboot in Crontab,GUI,8.0.4-BETA1,8.2.0-RELEASE,enhancement,,new,2012-02-21T18:05:51Z,2012-02-21T18:05:51Z,"the @reboot option for the crontab would be nice to quick execute something on boot, while a command section like on .7 would be even better (preinit/postinit)",bubulein Active Tickets,2176,Mounting NTFS USB Harddisk fails,Backend,8.3.1-RELEASE-p2,8.3.1-RELEASE-p3,defect,,new,2013-05-11T13:26:32Z,2013-05-11T13:26:32Z,"Trying to mount an external NTFS USB Disk (WD 320GB) fails. GUI reports mount success (including mount point /mnt/wd320gb), but console login shows that mounting failed. Device: /dev/da0a After a kldload geom_mbr everything works fine.",andreas Active Tickets,878,Wake On Lan (with several NICs) not working,FreeBSD,8.0.2-RELEASE,9.1.0-RELEASE,defect,,new,2011-10-04T08:46:14Z,2012-08-28T13:28:31Z,"With two Intel nics 82579LM and 82574L (freenas recognizes as Intel(R) PRO/1000 Network Connection) WakeOnLan is not working correctly. ifconfig -m lists wol compatibles: capabilities=1399b ""ifconfig em0 wol_magic"" and ""ifconfig em0 wol"" enables the wol support. I shut down the nas via ""shutdown -p now"" and try to wake up the system from a ubuntu linux again (with ""etherwake"" and some things like ""wakeonlan -i 192.168.100.10 00:30:48:XX:XX:XX"" I could configure three different ways to power on the system via wol: WOL_MAGIC, WOL_MCAST and WOL_UNICAST. I tried them in different combinations. WOL_MAGIC > no boot ->> not working WOL_MAGIC,WOL_MCAST > boots direct after shutdown (without any command to boot the system) ->> not working WOL_MAGIC,WOL_UNICAST > doesn´t wake up the box The problem is that the preferred method (Magic_Packet) is completely not working. With MCAST the system boots immediately after shutdown. >> There are a few posts in the forum (english and german) about WOL and nobody get it working correctly. http://forums.freenas.org/showthread.php?2339-Wake-On-Lan-WOL-with-Supermicro-C7Q67-and-2x-Intel-NICs&highlight=WOL http://forums.freenas.org/showthread.php?2426-Freenas-8-wol",vanhaakonnen Active Tickets,1588,Web Shell: word wrapping seems to be wrong,GUI,8.2.0-BETA4,9.1.0-RELEASE,defect,william,accepted,2012-06-19T20:55:12Z,2012-11-29T11:27:03Z,"When pasting a long line (for instance, ssh-keyscan IP), it seems that the web shell will wrap the line when copying by adding a line feed at the wrap point. It's desirable to change this behavior to something like, have the console display wrap the lines instead.",delphij Active Tickets,1589,Feature request: make SSH key fields smarter,GUI,8.0.2-RELEASE,9.1.0-RELEASE,defect,william,accepted,2012-06-19T20:58:20Z,2012-12-24T07:30:52Z,"Currently these fields (when modifying user, when setting up replication, etc.) will access the input without validation. It would be nice if it can remove unneeded spaces/line feeds that renders the key unusable, or at least bail out. For instance, this: """""" 10.2.1.25 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIb mlzdHAyNTYAAABBBAkEu2+8U+Vjf06RSDJKgLDhUYLJ3jy/NFqeIqQKYRKd5V63gRgw Gq4aBUcd57EpD5HH9twC6Wd2WRasICfmkDo= """""" Should be changed to this: """""" 10.2.1.25 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBAkEu2+8U+Vjf06RSDJKgLDhUYLJ3jy/NFqeIqQKYRKd5V63gRgwGq4aBUcd57EpD5HH9twC6Wd2WRasICfmkDo= """"""",delphij Active Tickets,1646,Problem replicating multiple Snapshots,Backend,8.0.4-RELEASE-p3,9.1.0-RELEASE,defect,william,accepted,2012-07-14T11:09:20Z,2012-08-17T20:11:17Z,"I want to keep different Snapshots for a different time, i.e. keep 15 min snapshots for 24h, 1h snapshots for 24 hours, 1d snapshots for 1 week an so on. The Problem starts, when the snapshots are created at the same time: {{{ [root@master] ~# /sbin/zfs list -t snapshot -o name,freenas:state -S creation NAME FREENAS:STATE data@auto-20120714.1240-8h NEW data@auto-20120714.1225-24h NEW data@auto-20120714.1225-8h NEW data@auto-20120714.1225-1w NEW data/store@auto-20120714.1225-24h NEW data/store@auto-20120714.1225-8h NEW data/store@auto-20120714.1225-1w NEW data/testufs@auto-20120714.1225-24h NEW data/testufs@auto-20120714.1225-8h NEW data/testufs@auto-20120714.1225-1w NEW }}} Logfile: {{{ Jul 14 12:26:01 master autorepl[16797]: Destroying remote data Jul 14 12:26:01 master autorepl[16797]: Executing: /usr/bin/ssh -i /data/ssh/replication -o BatchMode=yes -o StrictHostKeyChecking=yes -q 192.168.109.133 /sbin/zfs destroy -rRf data Jul 14 12:26:01 master autorepl[16797]: Creating data on remote system Jul 14 12:26:01 master autorepl[16797]: Executing: /usr/bin/ssh -i /data/ssh/replication -o BatchMode=yes -o StrictHostKeyChecking=yes -q 192.168.109.133 /sbin/zfs create -o readonly=on -p data Jul 14 12:26:02 master autorepl[16797]: Executing: (/sbin/zfs send -R data@auto-20120714.1225-1w | /usr/bin/ssh -i /data/ssh/replication -o BatchMode=yes -o StrictHostKeyChecking=yes -q 192.168.109.133 ""/sbin/zfs receive -F -d data && echo Succeeded."") > /tmp/repl-16797 2>&1 Jul 14 12:26:03 master autorepl[16797]: Popen()ing: /usr/bin/ssh -i /data/ssh/replication -o BatchMode=yes -o StrictHostKeyChecking=yes -q 192.168.109.133 ""zfs list -Hr -o name -S creation -t snapshot -d 1 data | head -n 1 | cut -d@ -f2"" Jul 14 12:26:03 master autorepl[16797]: Remote and local mismatch after replication: data@auto-20120714.1225-24h vs data@auto-20120714.1225-1w Jul 14 12:26:03 master autorepl[16797]: Popen()ing: /usr/bin/ssh -i /data/ssh/replication -o BatchMode=yes -o StrictHostKeyChecking=yes -q 192.168.109.133 ""zfs list -Ho name -t snapshot data | head -n 1 | cut -d@ -f2"" Jul 14 12:26:03 master autorepl[16797]: Replication of data@auto-20120714.1225-1w failed with Succeeded. }}} Calling this on slave side gives {{{ [root@slave] ~# zfs list -Ho name -t snapshot data cannot open 'data': operation not applicable to datasets of this type }}} ",tmueko Active Tickets,1767,tw_cli /c0/e0 show all crash,Backend,8.3.0-BETA1,9.1.0-RELEASE,defect,,new,2012-08-31T10:43:54Z,2012-09-28T15:42:38Z,see attached screenshot,hellweiss Active Tickets,1843,Replicated zvol fail to auto determine size in iSCSI,Backend,8.3.0-RELEASE-p1,9.1.0-RELEASE,defect,william,accepted,2012-10-17T15:01:53Z,2013-04-05T20:39:41Z,"Replication of ZFS volume fails with ""I/O"" error Oct 17 07:40:06 freenas autorepl.py: [common.pipesubr:49] Executing: (/sbin/zfs send -R corpsan1/corpsan1vm1@auto-20121016.1731-2w | /usr/bin/ssh -i /data/ssh/r eplication -o BatchMode=yes -o StrictHostKeyChecking=yes -q -p 22 corpsan2 ""/sbin/zfs receive -F -d corpsan2repl1 && echo Succeeded."") > /tmp/repl-34834 2>&1 Oct 17 07:40:06 freenas autorepl.py: [common.pipesubr:42] Popen()ing: /usr/bin/ssh -i /data/ssh/replication -o BatchMode=yes -o StrictHostKeyChecking=yes -q -p 22 corpsan2 ""zfs list -Hr -o name -S creation -t snapshot -d 1 corpsan2repl1/corpsan1vm1 | head -n 1 | cut -d@ -f2"" Oct 17 07:40:06 freenas autorepl.py: [tools.autorepl:323] Replication of corpsan1/corpsan1vm1@auto-20121016.1731-2w failed with cannot send 'corpsan1/corpsan1vm 1': I/O error Oct 17 07:41:05 freenas autorepl.py: [tools.autorepl:258] Destroying remote corpsan2repl1/corpsan1vm1 Oct 17 07:41:05 freenas autorepl.py: [common.pipesubr:49] Executing: /usr/bin/ssh -i /data/ssh/replication -o BatchMode=yes -o StrictHostKeyChecking=yes -q -p 2 2 corpsan2 /sbin/zfs destroy -rRf corpsan2repl1/corpsan1vm1 Oct 17 07:41:05 freenas autorepl.py: [tools.autorepl:264] Creating corpsan2repl1/corpsan1vm1 on remote system Oct 17 07:41:05 freenas autorepl.py: [common.pipesubr:49] Executing: /usr/bin/ssh -i /data/ssh/replication -o BatchMode=yes -o StrictHostKeyChecking=yes -q -p 2 2 corpsan2 /sbin/zfs create -o readonly=on -p corpsan2repl1/corpsan1vm1 Oct 17 07:41:05 freenas autorepl.py: [common.pipesubr:49] Executing: (/sbin/zfs send -R corpsan1/corpsan1vm1@auto-20121016.1731-2w | /usr/bin/ssh -i /data/ssh/r eplication -o BatchMode=yes -o StrictHostKeyChecking=yes -q -p 22 corpsan2 ""/sbin/zfs receive -F -d corpsan2repl1 && echo Succeeded."") > /tmp/repl-34884 2>&1 Oct 17 07:41:05 freenas autorepl.py: [common.pipesubr:42] Popen()ing: /usr/bin/ssh -i /data/ssh/replication -o BatchMode=yes -o StrictHostKeyChecking=yes -q -p 22 corpsan2 ""zfs list -Hr -o name -S creation -t snapshot -d 1 corpsan2repl1/corpsan1vm1 | head -n 1 | cut -d@ -f2"" Oct 17 07:41:05 freenas autorepl.py: [tools.autorepl:323] Replication of corpsan1/corpsan1vm1@auto-20121016.1731-2w failed with cannot send 'corpsan1/corpsan1vm 1': I/O error ",amirn Active Tickets,1866,Can't remove log device,GUI,8.3.0-RC1,9.1.0-RELEASE,defect,william,accepted,2012-10-25T18:04:38Z,2012-11-01T09:44:06Z,"Got the following errors when I tried to remove or offline the log device in the GUI. {{{ Oct 25 10:11:42 sanbox manage.py: [middleware.exceptions:38] [MiddlewareError: Disk could not be removed: ""cannot remove gptid/c769df18-1ea6-11e2-ac6c-005056ac0e70: no such device in pool, ""] Oct 25 10:12:19 sanbox notifier: swapoff: /dev/da1p1: Invalid argument Oct 25 10:12:19 sanbox manage.py: [middleware.exceptions:38] [MiddlewareError: Disk could not be removed: ""cannot remove gptid/c769df18-1ea6-11e2-ac6c-005056ac0e70: no such device in pool, ""] Oct 25 10:12:57 sanbox notifier: swapoff: /dev/da1p1: Invalid argument Oct 25 10:12:57 sanbox manage.py: [middleware.exceptions:38] [MiddlewareError: Disk offline failed: ""cannot offline gptid/c769df18-1ea6-11e2-ac6c-005056ac0e70: no such device in pool, ""] }}} {{{ zpool status pool: san state: ONLINE scan: scrub repaired 0 in 0h36m with 0 errors on Thu Aug 9 02:33:18 2012 config: NAME STATE READ WRITE CKSUM san ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 da2 ONLINE 0 0 0 da6 ONLINE 0 0 0 da3 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 logs gptid/c769df18-1ea6-11e2-ac6c-005056ac0e70 ONLINE 0 0 0 errors: No known data errors }}} {{{ glabel status Name Status Components ufs/FreeNASs3 N/A da0s3 ufs/FreeNASs4 N/A da0s4 ufs/FreeNASs1a N/A da0s1a gptid/c769df18-1ea6-11e2-ac6c-005056ac0e70 N/A da1p2 gptid/c7661b6a-1ea6-11e2-ac6c-005056ac0e70 N/A da1p1 }}} This worked at 1 point during the 8.3.x series but it's not working now for some reason. I may have changed someone that caused this but I believe I have a fairly clean setup at this point. The only thing I can think of is this time there was a reboot between adding & trying to remove the log and in the past there wasn't(don't ask why I keep add & removing the log unless you'd like more detail then this report probably needs). ",pbucher Active Tickets,2056,ESXi with LSI Cards,FreeBSD,8.3.0-RELEASE-p1,9.1.0-RELEASE,defect,,new,2013-02-21T17:09:23Z,2013-02-22T01:08:31Z,"Out of the box you can not boot FreeNAS in a VMware ESXi VM if you have a physical LSI card passed through to the VM. This is mainly ESXi's fault with having some kind of limitation related to msix interrupts(I don't understand it but it's been that way through multiple ESXi releases so I'm guessing it's either impossible to fix or really low on the todo list). Anyways if you simple bring up FreeNAS before adding the LSI card and add the tuning variable""hw.pci.enable_msix=0"" life is great and everything is good. The bug/problem is when you upgrade FreeNAS is, it boots up with a generic setup to do the db upgrade and finalize things and it doesn't have the customized loader.conf file in place yet and you get a hung system. '''Work Around:''' 1. Install update, catch it at the boot prompt and pause boot cycle at the boot prompt. 2. Power Off VM and remove LSI card from VM. 3. Power Up VM, after the 1st boot does the database upgrade and reboots pause it again at the boot prompt. 4. Power Off VM add back LSI card to VM. 5. Power Up and enjoy your upgraded FreeNAS server. '''Ideas/Thoughts:''' 1. If it's possible to detect your booting in a VM, automatically add ""hw.pci.enable_msix=0"" to rc.conf with the other VMware lines. 2. I'm guessing it would be considered undesirable to add that line across the board. 3. Produce a VMWare only upgrade that has that automatically added to rc.conf or loader.conf. 4. Some how save the working loader.conf.local file from the existing setup and boot up with that for the upgrade and then overwrite it. Note: I'm been running a slight mod of this this(hw.mps.disable_msix=""1"") in production since the Beta2 days of 8.3 with great results. I'm able to hit 500MB per sec writes to disk(not OS cached or ZIL cached) on my ZFS vol without a problem(3x5 drive Raid1Z) inside the VM. I'm going to switch my test SAN over to ""hw.pci.enable_msix=0"" to validate it before I move it to production. ",pbucher Active Tickets,2068,Mounting NFS share inside jail broken by VIMAGE,FreeBSD,8.3.0-RELEASE-p1,9.1.0-RELEASE,defect,,new,2013-02-27T08:37:35Z,2013-02-28T09:16:42Z,"Previous to the use of VIMAGE and the plugin jail, you could mount an NFS share inside a jail on FreeNAS. (mount -t nfs host:/share /mnt/path). The share I'm trying to mount is exported from FreeNAS (it worked before VIMAGE & plugin jail was added to FreeNAS). This seems to have broken with the use of VIMAGE. Now when trying the above mount command, you get: mount_nfs: /mnt/share, : Operation not permitted Trying to start nfsiod also gives the error: nfsiod -n 4 nfsiod: sysctlbyname(""vfs.nfs.iodmax""): Operation not permitted I've tried installing/using ports/net/unfs3, but it doesn't work, maybe because I'm not using it correctly. I've also tried adding the following entries to the rc.conf inside the jail without success (stopped & restarted plugin service): nfs_client_enable=""YES"" rpcbind_enable=""YES"" rpcbind_flags=""-h 10.0.10.30"" mountd_enable=""YES"" mountd_flags=""-h 10.0.10.30""",protosd Active Tickets,2087,SSH key issues with importing config and factory restore,Backend,8.3.0-RELEASE-p1,9.1.0-RELEASE,defect,,new,2013-03-15T03:36:05Z,2013-05-20T17:11:09Z,"I recently did an import of my configuration and I noticed that my root ""SSH Public Key"" was not migrated as expected. I have verified that the old USB key really does have the key and it has functioned for a couple of months. Additionally Skymonkey on the forums said that he did a ""factory restore"" in the GUI and his root SSH key remained in the config. This would constitute a security risk and should be fix for the next version. Listed this as a blocker as it has potential serious security implications. The issue was identified in 8.3.0-p1-x64",noobsauce80 Active Tickets,2112,Proftpd error,Backend,,9.1.0-RELEASE,defect,,new,2013-04-03T20:53:01Z,2013-05-21T10:47:19Z,"freenas proftpd[3340]: 127.0.0.1 - error opening scoreboard: Operation not permitted I have just install a clean install of this lastest version of freenas and I have a error when I start the FTP service. Version = FreeNAS 9.1.0 alpha c86e8f4-x64",MotorSport Active Tickets,2172,Some error ocurred plugin error,GUI,,9.1.0-RELEASE,defect,,new,2013-05-07T23:42:55Z,2013-05-07T23:45:54Z,"FreeNAS-9.1.0-ALPHA-8c9ebb9-x64 The error used to occur on 8.x when you hadn't edited/saved the plugin settings before trying to start the plugin because it hadn't updated the database. Since installing a plugin (JDownloader) isn't updating the treemenu, there's not icon/edit button. I'm not sure if the previous problem I just reported (bad gateway) is related.",protosd Active Tickets,45,Information lacking about drive when creating volumes,GUI,8.2.0-RELEASE-p1,9.1.0-RELEASE,enhancement,,assigned,2010-11-21T18:36:41Z,2012-08-10T11:45:33Z,"The user is presented only with 'ad0' for a disk, rather than giving more details such as size, manufacturer, etc.",bsdimp Active Tickets,147,Add SMART graphing (collectd modules?),Backend,8.2.0-RELEASE-p1,9.1.0-RELEASE,enhancement,jpaetzel,accepted,2011-02-21T16:37:50Z,2012-07-31T13:21:04Z,"i' would be great to keep this 0.7 feature in the new 0.8 release. Especiall, monitoring HDD temperature is a noticeable added value when one runs a fanless system. Ideally, a graphing(RRD ?) and alerting(email ?) capability for the SMART temperature would also be nice to make sure temp don't go too high too long. ",pierrep Active Tickets,398,Need for critical real-time read-outs in the GUI,Backend,8.0-RELEASE,9.1.0-RELEASE,enhancement,william,accepted,2011-06-06T02:59:03Z,2012-08-01T13:22:50Z,"I find it quite difficult to troubleshoot hardware issues without knowing almost instantaneously what's the CPU load, its temperatue, HDD's temperatures and memory utilization. Please bring back the near-real time read-outs in the GUI",globus999 Active Tickets,482,Backup/Restore RRD stats,Backend,8.2.0-RELEASE-p1,9.1.0-RELEASE,enhancement,,new,2011-06-29T22:38:46Z,2012-08-14T11:48:43Z,"When installing a new build the RRD stats history is lost. It would be useful if these stats could be downloaded as a backup and then subsequently restored in a similar way to the system config.",MilhouseVH Active Tickets,950,Web UI request: Include information about scrubbing and spares when doing a zpool status,GUI,8.0.2-RELEASE,9.1.0-RELEASE,enhancement,william,accepted,2011-10-24T05:34:09Z,2013-03-08T01:14:18Z,"This request is for the Web UI. When checking on the status of a ZFS volume (zpool status) it should: * show the status of the scrub (if there is one in progress) * show the state of the spares When viewing the disks in a ZFS volume (view disks): * list spares in addition to the other disks in the pool I upgraded from 8.0 to 8.0.2 today. I am running the latest version. At this time I have to run 'zpool status volume_name' from the command line to find this information. Thank you.",gh5046 Active Tickets,1052,Need CLI for editing and removing static routes,Backend,8.0.2-RELEASE,9.1.0-RELEASE,enhancement,william,accepted,2011-11-29T22:11:43Z,2012-07-31T13:17:21Z,"Right now one can provide a bad static route that can make a system unreachable via the network and requires one to go onto the CLI and nuke the routes manually. It would be nice if the static routes were completely configurable on the CLI, or at least halfway configurable like interfaces are today so the user wouldn't have to go into the shell to delete the bad routes, then go into the GUI and delete the routes for good. One way I found that really messes up the proverbiable apple cart is if I add a static route to 10.2.50.0/24 via 10.2.0.1, then add a default route to 10.2.0.1 (note the overlap in the destinations). Eventually a number of services get cranky tossing around packets and the system becomes unreachable. This isn't a very good repro case.. I'll try to come up with something better.",gcooper Active Tickets,1183,Console feature to reset only network settings to factory default,Backend,,9.1.0-RELEASE,enhancement,william,accepted,2012-01-13T00:34:01Z,2012-11-29T11:13:36Z,"I think there should be an option to reset network settings and interfaces to factory default, out there in the console. This is needed when for whatever reason one is no longer able to access the FreeNAS machine over the network and a reconfiguration is appropriate to do via the console. So in short, the same as the current factory default, but only for the networking.",rawtaz Active Tickets,1272,Login-Modes,Backend,8.0.3-RELEASE-p1,9.1.0-RELEASE,enhancement,william,accepted,2012-02-12T11:39:46Z,2012-11-29T11:29:04Z,"Here I like to describe a “MultiUser-Like” UI The Current Situation: Currently it is only possible to login to the UI as “admin/root”. You have access to all settings. == What are Login-Modes? == Currently I have 3 different Login-Modes in mind. == Admin/root == The Admin have access to all Settings on the system. == Operator == The Operator-Mode hide all settings which are not essential for everyday-tasks. Usually there is no need to change network config, devices connected to a pool or basic settings of the services. (The Drive Caddy should do this without the need to access the UI) This Login-Mode provide only access to things like managing user permissions, creating and deleteing share or just check logs/status (perhaps an additionl Monitoring-Mode(readonly). == User == User usually only need access if they like to browse Files (a service is down and he like to download it via WebUI).also it would be nice if you can change passwords and personal informations. ",bubulein Active Tickets,1301,iSCSI Initator built into FreeNas with GUI,Backend,8.0.4-RC1,9.1.0-RELEASE,enhancement,,new,2012-02-27T12:21:54Z,2013-03-08T00:28:15Z,Pleas add iSCSI support with GUI so I can mount my storage device in FreeNas to increase the storage capacity.,FireBIade Active Tickets,1488,Feature Request: Enable sharing of home folders (~/) via afpd,GUI,8.2.0-BETA3,9.1.0-RELEASE,enhancement,william,accepted,2012-04-25T22:22:57Z,2012-11-29T11:28:49Z,"Netatalk/afpd allows sharing all home folders based on user login credentials by simply adding tilde (~) to the AppleVolumes file. Please provide an option for afpd, preferably in the afp settings within the services tab, to enable sharing of home folders. This will allow users to share all home folders, without having to create a new home folder share for each user. It is certainly possible that there could be some negative interaction if a user's home folder is defined as /nonexistent. I haven't been able to test, since I can't enable the ~ share.",johnstonjs Active Tickets,2014,Infiniband support for Mellanox cards (OFED),Backend,,9.1.0-RELEASE,enhancement,,new,2013-01-22T13:34:51Z,2013-01-22T13:34:51Z,"Recently, the OFED stack was merged in March 2011 and is available in FreeBSD 9.0 and later. (https://wiki.freebsd.org/InfiniBand) It would be great having FreeNas supporting Infiniband!",juel Active Tickets,2039,rsync should use ZFS snapshot,Backend,,9.1.0-RELEASE,enhancement,,new,2013-02-12T01:01:46Z,2013-02-12T01:44:46Z,"The current rsync does not use snapshot. The proposed procedure would be: - For each path, find whether it's on a ZFS dataset. If so, create a temporary snapshot called ""_freenas_rsync_snapshot"", destroy if one pre-esists. - Use dataset's .zfs/snapshot/_freenas_rsync_snapshot/path/to/actual/path as source. This way, the rsync will be able to make consistent image at the remote side, which is useful for e.g. virtualization environment, etc.",delphij Active Tickets,2082,Feature request: Integrate AoE (ATA over Ethernet) support into Core Services interface,Backend,8.3.1-RC1,9.1.0-RELEASE,enhancement,william,accepted,2013-03-13T07:27:24Z,2013-03-13T11:34:50Z,"AoE is a fast and lightweight layer 2 protocol that allows for access to SATA storage devices over Ethernet networks. It's very easy to configure and scales linearly. I have created a howto guide on the forums that shows users how to implement AoE support on FreeNAS via the Plugins/jails feature. http://forums.freenas.org/showthread.php?11446-HOWTO-AoE-(ATA-over-Ethernet)-setup-using-Plugins-jail&p=54166#post54166 I think that AoE support merits inclusion into FreeNAS as a core service. Please give it due consideration.",srf21c Active Tickets,2111,UNIX Permissions versus ACLs,GUI,8.3.1-RELEASE,9.1.0-RELEASE,enhancement,william,accepted,2013-04-03T20:39:11Z,2013-04-22T18:02:20Z,"It's quite common that we see users who use AD to manage ACLs with CIFS. A lot of times, users will attempt to troubleshoot access via the FreeNAS unit's permission check boxes. This breaks the ACLs and leads to more problems. Suggestion is: When ACLs are enabled, set chmod 0777 on the pool or dataset and grey out all check box access. If moved back to UNIX permissions, run run `setfacl -b` to remove the ACLs and chmod to 0755 as sane default. Doing this should keep the state sane and unambiguous from the FreeNAS perspective, allowing users to troubleshoot setups without loosing total access.",jsa Active Tickets,2181,Allow cache for distfiles & src in do_build.sh,Build System,,9.1.0-RELEASE,enhancement,,new,2013-05-13T07:34:22Z,2013-05-16T01:57:33Z,"Some of the plugins I've made for FreeNAS 8.x have a lot of dependencies (java/x11 etc.). I've tried to create my plugins to fit into the standard build framework like Firefly etc. (do_build -t my_plugin). Waiting for distfiles and pulling source from the svn every time I rebuild a plugin is a waste of time and resources. I thought the point of caching Trueos source and ports was to help, but watching the logfile as the plugin builds, I'm seeing source and distfiles being downloaded again for the chroot. Having to start from scratch every time the build bombs sucks, can some variables be added for distfile cache directories etc. and maybe a build flag or something? As always, thanks for the dedication and nice work.",protosd Active Tickets,127,cannot install to a RAID mirror boot drive,Backend,8.0 Beta (r5698),,defect,,new,2011-01-18T03:45:09Z,2012-11-29T11:43:48Z,"I can't install to a mirrored boot drive on an SuperMicro X7SPA-H-O board. It's a 510 Atom server board with a Intel ICH9R controller. The mirror is recognized by FreeNAS 7.2.5739 as a single RAID drive and installs without a problem. The mirrored SSD's Kingston 16 GB V100 ",UrbanVoyeur Active Tickets,208,"Swap space is always striped, even on mirrored volumes",Backend,8.0-RC3,,defect,jpaetzel,accepted,2011-03-27T19:43:47Z,2011-08-29T21:23:51Z,"When creating a mirrored volume, FreeNAS currently creates an independent swap partition on every drive, resulting in the swap space effectively being striped. This completely eliminates the availability benefits of mirroring, as a drive failure will now result in the unexpected disappearance of swap space, panicking the system if that swap space was in use. For mirrored volumes, if you absolutely must create swap partitions on all drives (see #207), please create them on top of a gmirror so drive failure can be tolerated as one would expect from a mirrored volume.",razzfazz Active Tickets,252,NIC Interface changes drop zeroconf/bonjour functionality,Backend,8.0-RC5,,defect,,new,2011-04-15T08:26:04Z,2011-04-15T08:27:12Z,"Hello, when an NIC interface is changed in the GUI (for instance changing name only also) the triggered network restart seems to make bonjour/zeroconf lose the available services. maybe zeroconf services need to be restarted/regeistered also after interfaces are restarted ? regards, bjoern.",pille Active Tickets,534,Web GUI | configuration enhancement,GUI,8.0-RELEASE,,defect,,new,2011-07-20T13:21:01Z,2011-08-16T09:41:49Z,"I find it very cumbersome to reboot every time I make a small change to the network configuration. This reboot is not really needed as all can be accomplished on the cli. When you make a change via the web gui it freezes on apply and needs to be rebooted from the console. This could possibly be better served by using an configure and apply settings method.",daxroc Active Tickets,651,INADDR_ANY/in6addr_any should be rejected for cifs shares,GUI,8.0-RELEASE,,defect,,new,2011-08-26T01:02:01Z,2011-08-26T01:02:01Z,"Entering in INADDR_ANY for hosts allow rejects all possible connections instead of permitting them. The GUI needs to either inform the user that the input was invalid, or replace it with '*' (this form is accepted in smb.conf). The bug in samba was filed upstream as https://bugzilla.samba.org/show_bug.cgi?id=8408 .",gcooper Active Tickets,657,Confirmation notification dialog incorrectly placed on small displays,GUI,8.0.1-BETA4,,defect,,new,2011-08-26T20:04:13Z,2011-08-26T20:04:13Z,"Long story short, I'm running 800x600 (xorg.conf hasn't been fully configured for my box yet). The location of the confirmation notification dialog whenever I commit data is improperly placed (it's running over into some of the buttons on the right hand side). The screenshot is attached. Procedure: 1. Login to box. 2. Go to ""System"" -> ""General"". 3. Click ""Save"". Expected behavior: - Confirmation dialog should be properly placed either in the top panel, or another location where it's visible but non-intrusive. Obtained behavior: - Confirmation notification runs over into the top buttons on the right hand side of the screen.",gcooper Active Tickets,664,UI does not display list of items after saving,GUI,8.0.1-BETA4,,defect,,new,2011-08-26T21:53:08Z,2011-08-26T21:53:08Z,"For example, when you click System->Cron Jobs->Add Cron Job, then save, the 'View All Cron Jobs' tab should be displayed, currently the dialog closes and nothing is updated. If the tab is already open it should be reloaded. Rsync Tasks, S.M.A.R.T. Tests, as well as other items added from the tree should behave in the same manner. ",james Active Tickets,667,"Move/Mirror ""Control Services"" on/off toggles",GUI,8.0.1-BETA4,,defect,,new,2011-08-26T22:10:45Z,2011-08-26T22:10:45Z,I would like the on/off toggles in Services->Control Services to either be moved from this tab and displayed on the individual service's configuration dialog- or to display them in both places. It is cumbersome to configure SSH and then have to navigate somewhere else to turn it on. ,james Active Tickets,691,Inconsistency when deleting volume attached to iSCSI target,GUI,8.0.1-BETA4,,defect,william,accepted,2011-08-28T23:59:13Z,2011-11-29T13:13:16Z,"Deleting an iSCSI target with a volume that's currently in use warns the user that it's in use instead of providing a ""are you sure you wish to delete this extent"", kind of error. This is inconsistent with deleting volumes, ZFS volumes, and datasets, where the user is given an option to cascade delete all shares associated with the volume(s). Procedure: 1. Go to ""Storage"" -> ""Volumes"" -> ""Create Volume"". 2. Add a volume of type ""ZFS"" named ""test"". 3. Go to ""Create ZFS Volume"". 4. Create a ZFS volume named ""test2"" using the ""test"" ZFS pool. 5. Go to ""iSCSI"" -> ""Device Extent"". 6. Add an extent named ""test3"", pointing to the ZFS volume ""test2"". 7. Go to ""View all Volumes"". 8. Try and delete ""test2"" (this will fail citing that the ZFS volume is in use by ""test3""). 9. Try and delete ""test"" zpool. Click ""Yes"" (this will succeed). Expected result: The user should be presented with a dialog asking if they wish to disable all services associated with the ""test2"" ZFS volume (i.e. the ""test3"" extent). If they press no, nothing should occur. Otherwise, it should cascade down and delete the iSCSI extent as well. Actual result: The user is blocked from deleting the iSCSI extent, but not when deleting the ""test"" ZFS pool.",gcooper Active Tickets,703,"Diskspace report does not show ""diskspace""",Backend,8.0.1-RC1,,defect,,new,2011-09-02T00:11:29Z,2011-09-19T17:40:41Z,"When I moved files from a volume to a dataset the reporting page ""disk space"" no longer shows the actual size of the pool and no longer shows how much of the pool is used. [[Image(http://imageshack.us/photo/my-images/846/dfzfsarray1w.png/)]]",mcavity Active Tickets,835,Diskspace graph inaccurate,Backend,8.0.1-RC2,,defect,,new,2011-09-26T19:05:14Z,2011-10-02T03:04:12Z,"The Diskspace graph in reporting is inaccurate in my case. df -h shows 7.1T size, 657G used, while the graph says 7.1 TB size, 35.9 kB used. The ""used"" line is flat, while the used space grows. ",ubellavance Active Tickets,844,shadow copy support not toggled on/off unless share is manually retriggered,Backend,8.0.1-RC2,,defect,,new,2011-09-28T05:08:03Z,2011-09-28T05:14:44Z,"The shadow_copy2 attribute isn't automatically regenerated unless one modifies the share. So if I do one of the following scenarios, the shadow copy state will be incorrect: Scenario one: 1. Create a snapshot task for 'tank'. 2. Enable CIFS. 3. Add a share for 'tank'. 4. Verify that 'vfs objects' for 'tank' /usr/local/etc/smb.conf contains 'shadow_copy2'. 5. Remove the snapshot task. If you look at smb.conf, shadow copy support is still enabled. Scenario two: 1. Enable CIFS. 2. Add a share for 'tank'. 4. Verify that 'vfs objects' for 'tank' /usr/local/etc/smb.conf doesn't contain 'shadow_copy2'. 4. Create a snapshot task for 'tank'. 4. Verify that 'vfs objects' for 'tank' /usr/local/etc/smb.conf contains 'shadow_copy2'. If you look at smb.conf, shadow copy support isn't enabled. Reproduced on a nightly, but the difference between the 8.0.1 branch and trunk doesn't account for this behavior. The workaround for this is to click the share and press ok again after creating the snapshot task. This regenerates the share with the desired shadow copy attributes. The catch is that if there are any snapshots leftover on the system, shadow copy should remain on (unless the number of snapshots -> 0). This should really be fixed by modularizing smb.conf into smaller files, then restarting smbd at the end to set the shadow copy state appropriately, depending on the number of available snapshots.",gcooper Active Tickets,874,AD controller disappearing causes random issues with modifying CIFS shares/user info,Backend,8.0.1-RELEASE,,defect,,new,2011-10-03T19:41:17Z,2012-01-13T20:00:12Z,"- Customer took AD offline for a while. - Didn't point it to the new AD server. - Brought AD server back online. - Cached data was out of synch. Editing the CIFS share was throwing exceptions because it couldn't map the owner for the share. I had to manually run cachetool expire, then cachetool fill to ameliorate his share issue. The two bugs are: 1. Not finding user/group info shouldn't traceback in the GUI. 2. cachetool shouldn't need to be manually invoked when the AD cache and the AD backend get out of synch.",gcooper Active Tickets,875,remounting of root rw causes system unbootability in certain circumstances,FreeBSD,8.0.4-BETA1,,defect,,new,2011-10-03T19:52:24Z,2012-07-11T16:38:51Z,"My environment: hp proliant microserver http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/15351-15351-4237916-4237918-4237917-4248009.html usb flash: Sandisk Cruzer 4G (from costco) SDCZ36-004G http://www.amazon.com/SanDisk-Cruzer-Flash-Drive-SDCZ36-004G-A11/dp/B001T9EYFI steps to duplicate behavior install / upgrade login as root mount -urw / mount -ur / reboot end result: F1 FreeBSD F2 FreeBSD F5 Drive 1 F6 PXE Boot: F1 \ it will happily sit there forever. The only solution I've found is reupgrading via CD.. which is.. less than optimal. I have tried this with multiple jumpdrives of the same type, however these are all i happen to have, so I didn't try something else. I first noticed this behavior in the 8.01 RCs... it's still there. it's LIKELY something upstream, but I don't know. I'm happy to help debug this but I don't really know where to start. ",loiosh Active Tickets,977,NTPd Bind for IPv6 broken?,FreeBSD,8.0.2-RELEASE,,defect,,new,2011-11-02T21:52:49Z,2012-08-01T12:45:00Z,"This might be a rather weird error, however I though I should submit it. My home network is almost completely IPV6. The NAS box is connected to a switch with to 1000Mbit links that load balance over a Lagg interface. The IPV6 addresses are assigned automatically. What I see is this Nov 2 17:46:46 freenas ntpd[1647]: bind() fd 29, family 28, port 123, scope 0, addr 2001:470:1f15:120:222:15ff:feda:c2ed, in6_is_addr_multicast=0 flags=0x11 fails: Can't assign requested address Nov 2 17:46:46 freenas ntpd[1647]: unable to create socket on lagg0 (223) for 2001:470:1f15:120:222:15ff:feda:c2ed#123 I was ondering whether that is an issue with the ntpd used in Freenas (Freebsd) or a config error?",dmalloc Active Tickets,1012,Failed authentication attempts not added in daily email from the GUI,Backend,8.0.2-RELEASE,,defect,,new,2011-11-15T08:18:26Z,2011-11-15T20:24:40Z,"Hi, I am using 8.0.2 and have been receiving the daily email which is brilliant. However it doesn't seem to track failed login attempts at the web GUI. I have changed the name of the admin account, that could be a reason? Thanks, Toby.",tsatchell Active Tickets,1084,FreeNAS 8.0.2 AHCI driver issues with Marvell 88SE9128,FreeBSD,8.0.2-RELEASE,,defect,,new,2011-12-10T03:57:50Z,2012-11-29T11:33:29Z,"Hi, I recently purchased a HighPoint Rocket 620 PCI-Express 2.0 x1 SATA III (6.0Gb/s) controller to extend the number of SATA ports on my NAS. I installed the card on a Supermicro X7SPA-HF-D525-O Intel Atom D525 1.8GHz motherboard with 8GB of RAM. See all setup details [http://forums.freenas.org/showthread.php?1310-My-new-NAS-box-running-on-8-0-2 here]. When tested on FreeBSD, the card is detected properly as SATA2, confirmed also by a [http://forums.freebsd.org/showthread.php?p=118967#post118967 FreeBSD developer]. However, when set on FreeNAS, it shows as SATA1. Is the AHCI driver identical, or do you recommended me to add anything to loader.conf file? Thank you for your help.",TECK Active Tickets,1122,Problem with Hp Ml110 G6,FreeBSD,8.0.2-RELEASE,,defect,,new,2011-12-23T17:17:31Z,2012-07-25T12:29:01Z,"Hello from Greece I have purchased an HP ML110 G6 server and i am planning to use it as a file server for my windows network. I also purchased 4 x 2 TB WD HDD an my plans is to use them for RAID 1+0, I also installed 8gb dd3 1333 Ram FreeNas is to be installed on a usb memory stick 4gb Hp ML110 G6 has an on-board Raid controler (B110i) that gives you the ability to perform raid 0,1,1+0 i succesfully installed freeNas but i realized that it doesent recognizes the b110i and it sees 4 drives allthough the onboard raid controller is enabled. From the storage section of freenas i created a ZFS volume and created a Raid z2 that gives me a total of 3,5 Terrabytes. i changed the bios setting to ahci, so that the zfs can direct manage the disks! i have copied about 100 gbytes of data for testing issues and here is what happens: after finished copying... i unplugged 1 of my 4 drives to test the raidz efficiency and then got the message: (ada0:ahcich0:0:0:0): Lost Device i could still see my data all was working fine... but once i reconnected the drive back i got the following messages: (ada1:ahcich1:0:0:0): Lost Device (ada2:ahcich2:0:0:0): Lost Device (ada3:ahcich3:0:0:0): Lost Device and my data is no more browsable i check the storage tab and in the view disks tab all my drives are marked as unknown i perform a reboot and system hungs up and then i perform a hard reset and when my system is back online everything is working fine (my data is browsable again) and my drives are shown again is that normal ?? did i missed some part of the initial configuration ?? i thought that if i reconect the drive it should start rebuilding raid ?? i think that maybe i am experiencing a bug here. my version is 8.0.2.release amd64(8288) ",titisk Active Tickets,1166,"iSCSI Unit types {passthrough,tape,DVD} not implemented in istgt",Backend,8.0.3-RELEASE,,defect,william,accepted,2012-01-11T23:05:23Z,2012-01-30T12:31:35Z,"If I try and change the iSCSI unit type from Disk to passthrough, tape, or DVD, istgt fails to start, similar to the following output because the unit types aren't implemented in istgt (or we're populating the .conf file incorrectly): {{{ Jan 11 14:48:26 truenas istgt[14656]: istgt_lu_dvd.c: 489:istgt_lu_dvd_init: ***ERROR*** LU1: unsupported type Jan 11 14:48:26 truenas freenas: istgt_lu_dvd.c: 489:istgt_lu_dvd_init: ***ERROR*** LU1: unsupported type Jan 11 14:48:26 truenas istgt[14656]: istgt_lu.c:2007:istgt_lu_init: ***ERROR*** LU1: lu_dvd_init() failed Jan 11 14:48:26 truenas istgt[14656]: istgt.c:1667:main: ***ERROR*** istgt_lu_init() failed Jan 11 14:48:26 truenas freenas: istgt_lu.c:2007:istgt_lu_init: ***ERROR*** LU1: lu_dvd_init() failed Jan 11 14:48:26 truenas freenas: istgt.c:1667:main: ***ERROR*** istgt_lu_init() failed Jan 11 14:48:26 truenas freenas: LU1 DVD UNIT }}} Procedure: 1. Go to Services -> iSCSI on the tree menu. 2. Go to the Portals configuration pane. 3. Click Add Portal. 4. Click Ok. 5. Go to the Authorized Initiator configuration pane. 6. Click Add Authorized Initiator. 7. Click Ok. 8. Go to the Authentication configuration pane. 9. Enter in User: foo, Secret: foo. Click Ok. 10. Go to the Targets configuration pane. 11. Click Add Target. 12. Enter in Target Name: test, Target Alias: test, Type: Pass, the Portal Group ID and Initiator Group ID for the Portal created in step 3. Click Ok. 13. Go to the Device Extents configuration pane. 14. Click Add Extent. 15. Enter in Extent Name: test, for Disk Device, choose a ZVol or disk of interest. Click Ok. 16. Go to Services -> Control Services. 17. Turn the slider on for iSCSI. Expected result: - iSCSI should turn on. Actual result: - iSCSI fails to turn on as shown above.",gcooper Active Tickets,1167,".freenas folder not 'locked'; can cause issues with multiple operations (plugins, firmware updates, service packs) being performed to volume",Backend,8.0.3-RELEASE,,defect,,new,2012-01-12T00:10:34Z,2012-04-04T12:49:24Z,"If I run more than one upgrade operation in parallel, nothing is done today in 8.0, etc to ensure that I'm restricted from doing that. Problem was discovered on 8.0.2 when jason and I accidentally started 2 firmware updates in parallel. Procedure: 1. Go to System -> Advanced. 2. Click Firmware Update. 3. Point the update dialog to a dataset/volume that you want to upload it to and press Ok. 4. Put in the SHA and the build image. 5. Press Ok. 6. Open up another browser [tab] and repeat steps 1-5 while the upload/update is occurring in the background. Expected result: - Every successive attempt to upgrade/upload files to the volume/dataset should be rejected. Actual result: - Successive attempts are allowed. - Update operation (in this case) produced a failed update, but instead of bricking the system it booted back into the last partition and everything was 'sane'.",gcooper Active Tickets,1201,Gmultipath and Glabel Devices Don't Show in Gui,GUI,8.0.2-RELEASE,,defect,,new,2012-01-17T22:58:27Z,2012-01-17T23:08:14Z,"When configuring multipath SCSI/SAS links with gmultipath or using glabel to label devices, said devices do not appear in the gui for use. As such, no way to provide multipath direct attached storage. Related to the adding of gmultipath in http://support.freenas.org/changeset/5040/freenas. ",jstillwa Active Tickets,1248,Usernames with spaces in them cannot run cronjobs,FreeBSD,8.0.3-RELEASE-p1,,defect,william,accepted,2012-02-05T23:29:38Z,2012-02-06T17:17:04Z,"Windows users can have spaces in their usernames. Unfortunately this doesn't work with the system crontab because spaces are used as field delimiters and the username isn't tokenized properly with either octal/hex escaped characters or by quoting the username (I tried). crontab -u 'DOMAIN\user name' -e works though. Filed upstream here: http://www.freebsd.org/cgi/query-pr.cgi?pr=164808 Procedure: 1. Join machine to AD domain. 2. Create a user on the PDC called 'DOMAIN\user name'. 3. Attempt to create an cronjob that does 'echo hello > /tmp/iwuzhere' that runs every minute of every day. Expected result: - 'cat /tmp/iwuzhere' should say 'hello'. Actual result: - The command isn't executed.",gcooper Active Tickets,1302,"""Login error: incorrect user name or bad password"" error on Windows clients if FreeNAS rebooted",Backend,8.3.0-RELEASE,,defect,,new,2012-02-28T01:09:26Z,2012-11-13T06:11:31Z,"On an Active Directory network, if the FreeNAS server is rebooted, either planned or due to a crash, Windows clients currently logged in with mapped CIFS drives display the titled error and fail to connect to the drive. Using different credentials to connect fail as well. This goes for accessing the currently mapped network drive as well as trying to access the share using either NetBIOS or IP address names. The only way to access the drives again is to log out of Windows and log back in again, which allows access again. This error doesn't seem to occur on Linux clients, which reconnect as soon as FreeNAS is loaded.",ColonelPanic Active Tickets,1439,NTFS can't display files encoded in some charsets,Backend,8.2.0-BETA2,,defect,,new,2012-04-01T07:17:02Z,2012-10-31T13:16:54Z,"It's weird and never happened on 0.7.x. when I tested CIFS/Samba in FreeNAS 8(8.0.4 & 8.2b) from a win7 client to the imported exsiting ntfs drive, the file and directory were not listed if there is any Chinese characters in this file or directory, only listed those files in english. Console shows ""ntfsmount[3847]: skipping unpresentable filename (inode xxx) Illegal byte sequence"" I'm not sure if it's a configuration issue, but it never happened in my FreeNAS 0.7.x installation, which is ""install and run"" without this problem. Please check.",andysongxt Active Tickets,1485,web-gui alert light/message does not synchronize fast enough with state of system,Backend,8.2.0-BETA3,,defect,,new,2012-04-23T15:56:56Z,2012-04-23T16:30:46Z,"On a freshly installed FreeNAS-8.2.0-BETA3-x64 (vmware workstation, 6Gig RAM, 4 disks in a RaidZ1) if one simulates the failure of a disk like following: 1. hard power off freenas (not shutdown) 2. delte one disk (after power failure one disk broke) 3. power back on (good: web-gui alert shows message of Raid being degraded) 4. shutdown freenas 5. add new disk (replacing old disk) 6. power on freenas 7. on ""volume status"" tab * replace removed disk with new one * detach removed disk 8. reload storage tab (no indication of raid being rebuild or anything!) 9. after some waiting reloaded storage tab reports raid being healty but the web-gui alert light is still on and message unchanged (see attached screenshot) 10. after a lot more waiting web-gui alert light also changes back to green For unexperienced users it is very confusing to not get a status update after replacing the disk (such as raid is being rebuilt). If zfs does not deliver this a hint in the web-gui would be good. Even more confusing is the web-gui alert light/message not changing as soon as the raid is rebuilt. ",tamada Active Tickets,1518,Reporting disappeared after reboot,Backend,8.0.3-RELEASE,,defect,,new,2012-05-12T03:07:20Z,2012-06-08T22:09:16Z,"Here is my info. System Information Hostname freenas.local FreeNAS Build FreeNAS-8.0.3-RELEASE-x64 (9395) Platform Intel(R) Xeon(R) CPU 5140 @ 2.33GHz Memory 24561MB System Time Fri May 11 22:59:48 2012 Uptime 10:59PM up 12:16, 1 user Load Average 0.00, 0.00, 0.00 OS Version FreeBSD 8.2-RELEASE-p5 Here is the problem. I have seen this happen in the past but it didn't matter to me. But I am about to rely on this to charge a customer. :-) So I need the reporting to work correctly, and I need to make sure that the charts are accurate. The Charts were working just fine, then today I rebooted the machine from the web gui. When things came back the graphs were all gone. I now only have data from after the reboot. Is there a way to recover the charts? Is there a way to archive the data so that it can be used later? Thanks. PS I did a bunch of searching and looking before I put this report in. I seemed that most of the reports were for older versions. ",kdbaumann Active Tickets,1569,"istgt configuration is a pain, and doesn't report PEBCAK properly",Backend,8.0.4-RELEASE-p2,,defect,,new,2012-06-08T00:48:45Z,2013-01-04T19:54:13Z,"So I've been through the process of configuring iSCSI on FreeNAS and ESXi a bunch of times now. I'd like to make the following observation: It's a pain to configure. You kind of need to step into Target Global Configuration to set the Base Name, but you cannot complete that screen because setting up CHAP requires other tabs to be configured first. So usually I wind up going to Portals, then working backwards a bit through Authentication and then forward to Authorized Initiators, then back to TGC to set up the CHAP options, then once I've set up what's to me the ""login/user"" stuff, I switch into ""device"" mode and go to ""Extents"", set up the extent, then to ""Targets"" to set up a target, then over to ""Associated Targets"". This is admittedly not the only way one could do this, but it's logical, and if you look at it, it's a messy bunch of hopping around. So that's only outlining the FreeNAS end of things; at the same time, one is also setting up stuff on ESXi in lockstep. More stuff that has to be got-right. Not sure what to suggest about that, except that I wanted to point out that it feels completely wrong, but anyways, on to my bug report. I was grinding through that for about the dozenth time this year, and I had my ESXi hosts rescan for new targets. One of them (and only one of them) was kicking up a Jun 7 18:49:35 freenas istgt[9615]: istgt_iscsi.c:2088:istgt_iscsi_op_login: ***ERROR*** lu_find_target() failed error. Obviously something not right; the fact that only one of them was causing the FreeNAS box to throw this made me re-walk through the CHAP stuff several times looking for stupid spaces and other errors, which can eat up a fair bit of time. When I became convinced that this couldn't be the problem, I dug some other ways and discovered that I hadn't committed the ""Associated Targets"" screen, and as a result istgt.conf ended with # LogicalUnit section ...and nothing more... So, since this is clearly a configuration-generated file, could someone please add some sanity checking to iSCSI configuration? It's obviously not possible to catch all possible errors, but it might be nice to generate a warning if a target was unused, or an extent was unused, or the resulting iSCSI configuration lacked a mandatory section, or stuff like that.",jgreco Active Tickets,1719,Synchronize cache failed on shutdown only,Backend,8.2.0-RELEASE-p1,,defect,,new,2012-08-13T10:45:23Z,2012-12-10T23:02:31Z,"Every time I reboot my FreeNAS box, the last line printed before shutdown is ""(some numbers) synchronize cache failed"". Please let me know if you need any detailed specs. You can find my build hardware details here: http://forums.freenas.org/showthread.php?1310-My-new-NAS-box-running-on-8-0-2",TECK Active Tickets,1736,"Removing aliases from interface slow, can crash box",Backend,8.3.0-BETA1,,defect,,new,2012-08-18T19:09:15Z,2012-12-23T03:43:23Z,"Hi guys, I have been running a pair of Intel NICs in a lacp lagg with a static IP & 3 aliases for a while. Last night I added a dual port Intel PT card to my filer. The plan was to move my iSCSI traffic (2 of the aliases) off the lagg onto their own interfaces. I installed the card (one port of the lagg came up, ports were detected in an odd order) so I was able toy edit the lagg to include the proper ports. So far, so good. The next step was to delete the aliases from the lagg interface, and this is where I ran into trouble. Editing the lagg configuration and selecting ""delete"" on the alias\aliases would result in the dialog hanging (for up to 20 minutes...the longest I waited). Thus began a number of attempts to remove the aliases from the interface via the GUI. I then moved to trying to remove the aliases via the CLI menu. I tried a number of combinations of deleting interface and reconfiguring\assigning IP addresses and found that I could actually cause the box to generate a Fatal Trap 12 by resetting an interface (see attached image ""network_config_core.jpg""). I eventually worked myself into a corner where I had all 4 interfaces unconfigured & getting addresses from DHCP, the only problem was they were for ""https://10.56.56.(100-103):80""...I was not able to connect to the GUI like that (I use HTTP for GUI access). At one point my lagg even came up with 67.215.65.132 as an address, which resolves to ""hit-nxdomain.opendns.com""...I cannot fathom how that wound up happening! I was able to eventually get the aliases unconfigured, but I actually had to restore an older config to get all the network back to where I could access the GUI, I just had to delete them, confirm they were deleted via the console over IPMI, kill the GUI config window and reboot the box for each alias. -Will",survive Active Tickets,1779,Use of VMXNET2 under ESXI5.0U1 causes unresponsive GUI,FreeBSD,8.3.0-BETA2,,defect,,new,2012-09-07T12:40:45Z,2012-09-07T12:40:45Z,"When using a VMXNET2 adapter under ESXi5.0u1, from the console it appears that everything is working fine. Address configuration, DHCP and network reachability are all fine. When trying to reach the GUI via HTTP, the GUI will not load. It makes it far enought to chance the title in the broswer but the page never loads. I do not know about other revisions of VMWare.",cmessin1 Active Tickets,1832,Firewire Lacy Drive in NTFS not showing files.,GUI,8.3.0-BETA3,,defect,,new,2012-10-10T09:15:48Z,2012-10-10T11:18:38Z,"Dear Support. We have a Lacy Fire Wire Drive which we have connected up via Firewire 400. It has 2 1TB drives of which FreeNAS can see, but our problem is that FreeNAS is unable see the NTFS contents of these drives. Do you have any idea why? Driver support maybe? We are using Version 8.3.0 RC1 X86. I look forward to reading your reply. Regards, Dan.",Dan ATR Active Tickets,1834,Active Directory AD username can't handle a space character,Backend,,,defect,,new,2012-10-11T17:02:12Z,2012-10-11T17:05:57Z,"My AD admins create all administrator accounts with a space in them, to absolutely prevent conflicts with institutional accounts, which cannot contain a space. When trying to turn on AD service in FreeNAS 8.2.0-r11950, /var/log/messages: freenas notifier: kinit: krb5_get_init_creds: Client (jo\@DOMAIN.EDU@DOMAIN.EDU) unknown The AD administrator account I entered is: jo raff",joraff Active Tickets,1842,USB Flash Drive not properly recognized,FreeBSD,8.3.0-RC1,,defect,,new,2012-10-17T00:23:24Z,2012-10-17T00:23:24Z,"When moving from 8.0.4 to 8.3.0-RC1 my HP 32GB Flash drive is not recognized properly and mounted. I have ruled out a defective drive as was suggested to me. These are messages that I get when plugging in the HP 32 from the console messages in the footer of the GUI: Oct 16 19:58:42 freenas kernel: ugen7.2: at usbus7 Oct 16 19:58:42 freenas kernel: umass2: on usbus7 On the actual console I get the following messages: ugen 7.2: at usbus7 umass2: on usbus7 What I'm missing is a mounting of the drive. The fix that I have found is: # usbconfig -d 7.2 add_quirk UQ_MSC_NO_INQUIRY # usbconfig -d 7.2 reset This will give me the following messages on the GUI console: Oct 16 20:07:12 freenas kernel: umass2: at uhub7, port 2, addr 2 (disconnected) Oct 16 20:07:12 freenas kernel: umass2: on usbus7 Oct 16 20:07:15 freenas kernel: da2 at umass-sim2 bus 2 scbus9 target 0 lun 0 Oct 16 20:07:15 freenas kernel: da2: < > Removable Direct Access SCSI-2 device Oct 16 20:07:15 freenas kernel: da2: 40.000MB/s transfers Oct 16 20:07:15 freenas kernel: da2: 30960MB (63406080 512 byte sectors: 255H 63S/T 3946C) From what I understand, the problem is in the scsi software and may still exist in FreeBSD 9.0 but that is so far outside of my understanding of FreeBSD right now. So I'm not sure if the ""fix"" is really a fix or really just a way to manually mount the flash drive. I'd like to have the drive be recognized during the boot time processing as I want to place my jails back on it. Since this likely only impacts a select few people, I don't think this is an urgent issue. It is for me but I'll live.",JoeSchmuck Active Tickets,1884,Warning unclear/misleading in Sharing/AFP popup dialog,GUI,8.3.0-RELEASE,,defect,,new,2012-10-31T21:45:40Z,2012-10-31T21:45:40Z,"The information button for the Disk Discovery Mode pulldown says: Note! Selecting 'Time Machine' on multiple shares may cause unpredictable behavior in MacOS. Default mode exports the volume as a data volume for users. It is unclear what this means. * is Time Machine necessary if the volume will be used for Time Machine backups? (Yes, it seems to enable the Time Machine specific switch in AppleVolumes.default). * Does this mean that a FreeNAS box can only provide TimeMachine backups for a single Mac? * Is this a server side problem (netatalk, bonjour?) shortcoming or a client side (Mac OS X) problem? * What does 'unpredictable behavior' mean? Will some volumes fail to show up in Time Machine's System Preferences dialog? Will backsups fail mysteriously part way through? * If it appears to be working, is it safe or am I living dangerously? It would be great if a. someone who knew what this meant described it better b. the info dialog was made less FUD-ish. Thanks! ",hartzell Active Tickets,1891,Samba share refuse to accept user login from Windows 7,Backend,8.3.0-RELEASE,,defect,,new,2012-11-06T01:26:23Z,2012-11-06T15:09:46Z," Hi, I am trying to set up password-protected and anonymous samba shares on the same FreeNAS boxes. My Windows 7 clients can connect to anonymous samba shares without any problem, but it can not connect to password-protected shares correctly without any patch. I found two problems: First, I have to comment out the line with ""smb passwd file = /var/etc/private/smbpasswd"" in order to make FreeNAS accept user login . It only works if the user name on the FreeNAS box is different from the one on Windows 7, Secondly, if the user name is the same on both FreeNAS and Windows 7, I have to use the same password on both Windows and FreeNAS so the user can connect. By the way, /var/etc/private/smbpasswd never exists on my FreeNAS box. ",cysu Active Tickets,1899,autoremove Snapshots recursive,Backend,8.3.0-RELEASE,,defect,,new,2012-11-12T08:32:30Z,2012-11-12T08:32:30Z,"I have configured recursive Snapshots and Replication. As you can see, the Snapshots of the datasets below the vdi dataset did not get automatically destroyed. Here is the /var/log/messages Nov 12 09:14:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/lka@auto-20121105.0823-1w Nov 12 09:14:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/akclone-xp@auto-20121104.0823-1w Nov 12 09:14:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/akclone-xp@auto-20121105.0823-1w Nov 12 09:14:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/lka@auto-20121104.0823-1w Nov 12 09:14:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/lka@auto-20121103.0823-1w Nov 12 09:14:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/akclone-xp@auto-20121103.0823-1w Nov 12 09:15:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/lka@auto-20121105.0823-1w Nov 12 09:15:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/akclone-xp@auto-20121104.0823-1w Nov 12 09:15:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/akclone-xp@auto-20121105.0823-1w Nov 12 09:15:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/lka@auto-20121104.0823-1w Nov 12 09:15:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/lka@auto-20121103.0823-1w Nov 12 09:15:03 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/akclone-xp@auto-20121103.0823-1w Nov 12 09:16:02 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/lka@auto-20121104.0823-1w Nov 12 09:16:02 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/lka@auto-20121105.0823-1w Nov 12 09:16:02 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/akclone-xp@auto-20121105.0823-1w Nov 12 09:16:02 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/akclone-xp@auto-20121104.0823-1w Nov 12 09:16:02 nas0 autosnap.py: [tools.autosnap:42] Popen()ing: /sbin/zfs get -H freenas:state nas0/vdi/lka@auto-20121103.0823-1w vol1/vdi@auto-20121106.0823-1w 2.44K - 73.1K - vol1/vdi@auto-20121107.0823-1w 2.44K - 73.1K - vol1/vdi@auto-20121108.0823-1w 2.44K - 73.1K - vol1/vdi@auto-20121109.0823-1w 2.44K - 73.1K - vol1/vdi@auto-20121110.0823-1w 2.44K - 73.1K - vol1/vdi@auto-20121111.0823-1w 2.44K - 73.1K - vol1/vdi/akclone-xp@auto-20121103.0823-1w 79.9M - 167M - vol1/vdi/akclone-xp@auto-20121104.0823-1w 110M - 1.28G - vol1/vdi/akclone-xp@auto-20121105.0823-1w 85.0M - 1.28G - vol1/vdi/akclone-xp@auto-20121106.0823-1w 402M - 1.94G - vol1/vdi/akclone-xp@auto-20121107.0823-1w 450M - 2.31G - vol1/vdi/akclone-xp@auto-20121108.0823-1w 138M - 2.86G - vol1/vdi/akclone-xp@auto-20121109.0823-1w 164M - 3.79G - vol1/vdi/akclone-xp@auto-20121110.0823-1w 156M - 3.80G - vol1/vdi/akclone-xp@auto-20121111.0823-1w 194M - 4.19G - vol1/vdi/lka@auto-20121103.0823-1w 14.4G - 367G - vol1/vdi/lka@auto-20121104.0823-1w 13.1G - 367G - vol1/vdi/lka@auto-20121105.0823-1w 14.0G - 367G - vol1/vdi/lka@auto-20121106.0823-1w 15.5G - 367G - vol1/vdi/lka@auto-20121107.0823-1w 15.7G - 367G - vol1/vdi/lka@auto-20121108.0823-1w 15.4G - 368G - vol1/vdi/lka@auto-20121109.0823-1w 15.7G - 368G - vol1/vdi/lka@auto-20121110.0823-1w 12.6G - 368G - vol1/vdi/lka@auto-20121111.0823-1w 12.4G - 368G - ",hellweiss Active Tickets,1912,WebGUI more accessible,Backend,8.3.0-RELEASE,,defect,,new,2012-11-23T19:38:21Z,2012-11-23T19:38:21Z,"For reference: http://forums.freenas.org/showthread.php?9980-Administering-freenas-from-the-commandline",william Active Tickets,1940,Samba VFS module dirsort not being loaded,Backend,8.3.0-RELEASE,,defect,,new,2012-12-09T04:38:43Z,2012-12-09T04:38:43Z,"When {{{ vfs objects = dirsort }}} is added to the auxiliary parameters section of the CIFS settings dialog, dirsort fails to load for Windows clients. I can get it to load by manually adding it to the specific share section after zfsacl as shown below: {{{ vfs objects = zfsacl, dirsort }}} A manual restart is needed of the samba service as restarting it via the GUI causes FreeNAS to overwrite the manual edit. The logs below show what happens when a Mac and Windows client connect. Windows: {{{ [2012/12/08 19:30:55.295145, 2] auth/auth.c:309(check_ntlm_password) check_ntlm_password: authentication for user [root] -> [root] -> [root] succeeded [2012/12/08 19:30:55.299051, 2] lib/module.c:64(do_smb_load_module) Module '/usr/local/lib/samba/vfs/zfsacl.so' loaded [2012/12/08 19:30:55.299310, 1] smbd/service.c:1114(make_connection_snum) matthewlindstro (10.1.0.110) connect to service NAS initially as user root (uid=0, gid=0) (pid 92854) }}} Mac: {{{ [2012/12/08 19:31:24.726843, 2] smbd/reply.c:553(reply_special) netbios connect: name1=10.1.0.162 0x20 name2=JESSICANEWELL 0x0 [2012/12/08 19:31:24.726924, 2] smbd/reply.c:573(reply_special) netbios connect: local=10.1.0.162 remote=jessicanewell, name type = 0 [2012/12/08 19:31:24.735308, 2] lib/module.c:64(do_smb_load_module) Module '/usr/local/lib/samba/vfs/dirsort.so' loaded }}} As shown above, only the zfsacl module is loaded for Windows clients, whereas for Mac, only the dirsort module is loaded.",mrlindstrom Active Tickets,1952,Set ZFS Volume OFFLINE bug,Backend,8.3.0-RELEASE-p1,,defect,,new,2012-12-16T15:49:20Z,2013-03-17T20:49:08Z,"I created a zfs raidz with three disks. [[Image()]] and set one of the disk to offline via the gui. [[Image()]] When setting the disk to online again i get an error, because the drive is still mounted i guess. {{{ Error: Disk replacement failed: ""invalid vdev specification, use '-f' to override the following errors:, /dev/gptid/af6fcda1-4797-11e2-9bb4-000c29abb0a0 is part of active pool 'test', "" }}} This will also happen, if i click ""replace"" on one of the drives and choose the allready in-use. [[Image()]] This will set the volume to offline. [[Image()]]",LANopop Active Tickets,1955,Do Not delete the files in FreeNAS 8,FreeBSD,8.3.0-RELEASE,,defect,,new,2012-12-17T10:21:40Z,2013-01-18T03:27:31Z,"How do you do! FreeNAS 8.3.0, 3 HDD, RAIDZ, file with full access all user. If from Windows (XP, 7) in NAS to copy the files with attribute ""for reading"" Only, that their then impossible delete nor with one PC, including source. That this - a generic trauma or something not so do? In NAS4Free such problems no - possible was his(its) use (apropos there more high velocity of copying), but change HDD and extension vault is there organized at all - through command line only, but for user this critical.",alex5151 Active Tickets,1972,UPS not working Freenas 8.3 latest build,Backend,8.3.0-RELEASE-p1,,defect,,reopened,2012-12-28T08:01:04Z,2013-01-02T15:57:37Z,"Hi@all, i tried everything but my UPS will not work. Hardware: UPS Powerwalker Vi 850 LCD (BLAZER_USB Driver) I checked the usbport via console: ugen3.2 (i tried all ports, nothing). Pls. help me Tim I get the following messages: Dec 28 08:52:20 freenas notifier: nut not running? (check /var/db/nut/upsd.pid). Dec 28 08:52:20 freenas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid). Dec 28 08:52:20 freenas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid). Dec 28 08:52:20 freenas notifier: Will not 'restart' nut because nut_enable is NO. Dec 28 08:52:20 freenas notifier: Will not 'restart' nut_upsmon because nut_upsmon_enable is NO. Dec 28 08:52:20 freenas notifier: Will not 'restart' nut_upslog because nut_upslog_enable is NO. Dec 28 08:52:42 freenas notifier: nut not running? (check /var/db/nut/upsd.pid). Dec 28 08:52:42 freenas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid). Dec 28 08:52:42 freenas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid). Dec 28 08:52:42 freenas notifier: nut not running? (check /var/db/nut/upsd.pid). Dec 28 08:52:42 freenas notifier: Permissions problem: Input/output error Dec 28 08:52:42 freenas notifier: Network UPS Tools - Megatec/Q1 protocol USB driver 0.09 (2.6.5) Dec 28 08:52:42 freenas notifier: Driver failed to start (exit status=1) Dec 28 08:52:42 freenas notifier: Network UPS Tools - UPS driver controller 2.6.5 Dec 28 08:52:42 freenas root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut Dec 28 08:52:42 freenas notifier: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut Dec 28 08:52:43 freenas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid). Dec 28 08:52:43 freenas notifier: Starting nut_upsmon. Dec 28 08:52:43 freenas notifier: kill: No such process Dec 28 08:52:43 freenas notifier: UPS: ups (master) (power value 1) Dec 28 08:52:43 freenas upsmon[22099]: UPS [ups]: connect failed: Connection failure: Connection refused Dec 28 08:52:43 freenas upsmon[22099]: Communications with UPS ups lost Dec 28 08:52:43 freenas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid). Dec 28 08:52:43 freenas notifier: Starting nut_upslog. Dec 28 08:52:43 freenas notifier: Warning: initial connect failed: Connection failure: Connection refused Dec 28 08:52:43 freenas notifier: Stopping nut_upslog. Dec 28 08:52:44 freenas notifier: Stopping nut_upsmon. Dec 28 08:52:44 freenas upsmon[22098]: upsmon parent: read Dec 28 08:52:44 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).",tim_s007 Active Tickets,1991,Snapshot expiry is not working on all zfs devices,Backend,8.3.0-RELEASE,,defect,,new,2013-01-07T08:32:55Z,2013-02-18T16:27:06Z,"I've got a FreeNAS 8.3 system, with hourly snapshots and 12-hour expiry. On the main pool, this works (I have the right number of snapshots), but on a zvol underneath this pool it has snapshots all the way back to Friday when I configured it. I've attached a list of all snapshots on this system, the images filesystem is fine (snapshots are being expired after 12 hours correctly) whereas the images/xen zvol snapshots remain indefinitely even though they're tagged -12h.",gac Active Tickets,1992,zfs scrub UI schedule does not match actual behavior,Backend,8.3.0-RELEASE-p1,,defect,,new,2013-01-07T12:39:54Z,2013-01-14T23:59:08Z,"After configuring an automated ZFS scrub last month (likely entered into the UI on 26 Dec), I have noticed that the automated ZFS scrub is occurring outside dates that I have specified. My clue is that I am receiving automated email messages from the freenas system to my email account configured for root. I so far have received two undesired scrubs (31 Dec and 7 Jan). At precisely 12:00am each monday night, freenas sent an email as follows: {{{ subject: Cron PATH=""/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/root/bin"" /usr/local/sbin/scrub -t 1 dale-mirror1 Body: starting scrub of pool 'dale-mirror1' }}} My desired scrub occurs only once/month. I desire the scrub to occur on the monday within the inclusive date range of 15-21 (the 3rd monday in the month). In the freenas UI on or around 26 Dec, I added a ZFS scrub as follows: Volume: dale-mirror1 (ZFS) Threshold days: 1 Minute: 00 Hour: 00 Day of month: 15,16,17,18,19,20,21 Month: every month Day of week: Monday Short description: None The crontab entry I find in /etc/crontab (mod date 26 dec 2012) is: {{{ 00 00 15,16,17,18,19,20,21 * 1 root PATH=""/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/root/bin"" /usr/local/sbin/scrub -t 1 dale-mirror1 }}} By running zpool status, I can see that the undesired scrub did actually occur last night.",diablodale Active Tickets,2018,fresh install without dhcp takes a long time,Backend,8.3.1-BETA2,,defect,,new,2013-01-28T08:39:58Z,2013-01-28T10:40:02Z,"I installed 8.3.1 beta2 on an empty box. Installation went fine, but the first boot took quite a long time (5+ minutes) and stalled several times. After setting a proper network address and a default gateway the delays in the boot sequence were gone (therefore I assume the initial delays might be network setting related).",Michael Moerz Active Tickets,2032,GUI Footer data not listed in window,GUI,8.3.1-BETA3,,defect,,new,2013-02-07T17:51:01Z,2013-02-13T14:22:29Z,"When upgrading from 8.3.0-Release to 8.3.1-Beta3, having the footer displaying console message data, when clicking on the footer it opens up a window typically used to copy data. The data which is last listed in the footer is not actually displayed in the window so the user cannot copy the last few lines of data. This was repeated twice on a VMWare version of the software. This problem is not present in 8.3.0-Release.",JoeSchmuck Active Tickets,2036,Screensaver crash,Backend,8.3.1-BETA2,,defect,,new,2013-02-11T14:34:11Z,2013-02-13T14:22:40Z,"When activating / deactivating the screensaver via webgui, the system hangs up. I activated the screensaver via webgui and hit save. Gui is saying please wait and nothing will happen anymore. Reentering webgui - no response of the system anymore, console will still accept user commands but with no reaction. Only way is to force a reboot to the system. After that, screensaver is enabled. Tried to disable screensaver again - same problem. System hangs up and needs reboot to disable the screensaver.",Firebird Active Tickets,2043,CIFS can't find user in passdb,Backend,8.3.0-RELEASE,,defect,,new,2013-02-15T18:02:22Z,2013-03-13T12:48:33Z,"Hey guys; I spent a lot of time asking this question in the IRC channel, and I really do appreciate your time, but I feel like we would all gain by having just the facts posted in one area. I have LDAP configured on my freenas box. It works with SSH/AFP, but does not work with CIFS. Here is my smb.conf file: [global] encrypt passwords = yes dns proxy = no strict locking = no read raw = yes write raw = yes oplocks = yes max xmit = 65535 deadtime = 15 display charset = LOCALE max log size = 10 syslog only = yes syslog = 1 load printers = no printing = bsd printcap name = /dev/null disable spoolss = yes smb passwd file = /var/etc/private/smbpasswd private dir = /var/etc/private getwd cache = yes guest account = nobody map to guest = Bad Password obey pam restrictions = Yes # NOTE: read smb.conf. directory name cache size = 0 netbios name = freenas workgroup = workgroup server string = freenas use sendfile = yes store dos attributes = yes security = user passdb backend = ldapsam:ldap://stork.example.com ldap admin dn = cn=ldapadmin,o=maya ldap suffix = o=maya ldap user suffix = ou=mayans ldap group suffix = ou=groups ldap ssl = off ldap replication sleep = 1000 ldap passwd sync = yes #ldap debug level = 1 #ldap debug threshold = 1 ldapsam:trusted = yes idmap uid = 10000-39999 idmap gid = 10000-39999 create mask = 0666 directory mask = 0777 client ntlmv2 auth = yes dos charset = CP437 unix charset = UTF-8 log level = 3 [mayans] path = /mnt/roc/mayans printable = no veto files = /.snap/.windows/.zfs/ writeable = yes browseable = yes inherit owner = no inherit permissions = no vfs objects = zfsacl guest ok = no inherit acls = Yes map archive = No map readonly = no nfs4:mode = special nfs4:acedup = merge nfs4:chown = yes When I try to authenticate and ""tail -f /var/log/samba"" I get this: [2013/02/15 09:09:39.362092, 3] ../libcli/auth/ntlmssp_server.c:348(ntlmssp_server_preauth) Got user=[mingo] domain=[FREENAS] workstation=[workstation] len1=24 len2=178 [2013/02/15 09:09:39.362187, 3] auth/auth.c:219(check_ntlm_password) check_ntlm_password: Checking password for unmapped user [FREENAS]\[mingo]@[workstation] with the new password interface [2013/02/15 09:09:39.362224, 3] auth/auth.c:222(check_ntlm_password) check_ntlm_password: mapped user is: [FREENAS]\[mingo]@[workstation] [2013/02/15 09:09:39.362377, 2] lib/smbldap.c:1018(smbldap_open_connection) smbldap_open_connection: connection opened [2013/02/15 09:09:39.364021, 3] lib/smbldap.c:1240(smbldap_connect_system) ldap_connect_system: successful connection to the LDAP server [2013/02/15 09:09:39.364506, 3] auth/check_samsec.c:399(check_sam_security) check_sam_security: Couldn't find user 'mingo' in passdb. [2013/02/15 09:09:39.364539, 2] auth/auth.c:319(check_ntlm_password) check_ntlm_password: Authentication for user [mingo] -> [mingo] FAILED with error NT_STATUS_NO_SUCH_USER [2013/02/15 09:09:39.364575, 3] smbd/sesssetup.c:63(do_map_to_guest) No such user mingo [FREENAS] - using guest account [2013/02/15 09:09:39.364629, 3] smbd/password.c:298(register_existing_vuid) register_existing_vuid: User name: nobody Real name: [2013/02/15 09:09:39.364672, 3] smbd/password.c:308(register_existing_vuid) register_existing_vuid: UNIX uid 65534 is UNIX user nobody, and will be vuid 100 http://pastebin.com/Y8DuR1rN It appears that it is failing to check my password. Would you like to me to post the log of when somebody authenticates to an AFP share? We want to finish evalutating freeNAS this month so we can purchase a box dedicated to it, but LDAP not working with CIFS is a deal breaker for my boss. Thank you for your time guys. ",mingo Active Tickets,2049,Too Large Footer,GUI,8.3.0-RELEASE-p1,,defect,,new,2013-02-17T19:15:48Z,2013-02-17T19:15:48Z,Please reduce the size of the GUI footer. FreeNAS otherwise becomes unusable on screensizes of smaller or equal 10 inches.,cs Active Tickets,2055,re-import of NTFS fails after intial import/export,Backend,8.3.1-BETA3,,defect,,new,2013-02-21T07:13:42Z,2013-02-22T06:32:07Z,"I've seen this now with multiple SATA drives and a USB stick as well. Order of operations is roughly: a. import NTFS drive A b. detach c. import NTFS drive B d. detach e. import NTFS drive A *fails* The second import of drive A will fail with ""Error getting available space"". I'm not sure if the intervening import of drive B is required to reproduce this, since the same thing happens with a USB stick after a couple imports/exports of it alone. Other factoids which may or may not be relevant: 1. The USB stick still works fine when plugged into a Windoze box, but remains impossible to import into FreeNAS. I'm not sure I can say the same for the hard drives but will check tomorrow at work where I have a computer I can easily plug them into. 2. In some cases, I may have been re-using the same name for the volume/mount points. Maybe that's confusing FreeNAS somehow. 3. The hard drives are always winding up at ada7 4. The hard drives are identical models (Seagate Barracuda 7200.11 1.5 TB) Maybe FreeNAS is caching some kind of disk info incorrectly and getting confused when another similar disk appears at the same /dev? That doesn't explain the USB stick though. Perhaps it's not detaching the drive correctly the first time around and is leaving some kind of broken state or signature on the drive that causes it to fail the second time around? If it's doing so, it's nothing I can obviously see on the USB stick from within windows. Maybe it's something in the partition table or some such. For now I'd call this a ""major"" defect, but might be inclined toward ""critical"" if in fact the drive has been rendered inoperable on any other OS as well, whihc I'll know tomorrow. Thanks much.",bertrem Active Tickets,2076,amdtemp kernel module not functional for C60-class Fusion core,FreeBSD,8.3.0-RELEASE-p1,,defect,,new,2013-03-08T03:47:52Z,2013-03-08T03:47:52Z,"According to kldstat, the kernel module ""amdtemp.ko"" is preloaded in the kernel, and indeed, ""kldload -v ./amdtemp.ko"" claims that the file exists. However, for an AMD C60 processor, such as is found in the ASUS C60M1-I, the amdtemp module does not appear in the output from ""sysctl -a"".",wanders Active Tickets,2091,nginx tcp/80 redirect cannot be permanently disabled,GUI,8.3.0-RELEASE,,defect,,new,2013-03-17T22:02:19Z,2013-03-17T22:45:27Z,"After changing web port a redirection on tcp/80 is created in #more /etc/local/nginx/nginx.conf server { listen 0.0.0.0:80; server_name localhost; rewrite ^ https://$server_addr:8080$request_uri? permanent; } This should be optional. It will be recreated on every reboot.",realdreams Active Tickets,2137,odd duplication of characters in log,GUI,8.3.1-RELEASE,,defect,,new,2013-04-17T19:26:00Z,2013-04-17T21:14:14Z,"I'm not sure exactly when this started occurring but it wasn't always like this... In the console logs, I'm getting seeing a strange duplication of characters in the log messages. I'm not even sure where to start troubleshooting this other than I'm still seeing it after a reboot. This ticket is in regards to the duplication of characters, not the actual message contents. {{{ Apr 17 14:22:43 dl1-filer1 kernel: <<66>>aarrpp:: 1100..2244..11..1144 mmoovveedd ffrroomm 0000::1100::ff33::2244::ee22::2288 ttoo 0000::1100::ff33::2244::ee22::5500 ono nb cbec1e Apr 17 14:22:43 dl1-filer1 kernel: 0 Apr 17 14:22:43 dl1-filer1 kernel: Apr 17 14:22:44 dl1-filer1 kernel: <<66>>aarpr:p : 1100..2244..11..1144 mmoovevde d ffrroomm 0 000::1100::ff33::224:4:e2e:25:05 0t ot o0 00:01:01:0f:3f:32:42:4e:e22::2288 oonn bbccee10 Apr 17 14:22:44 dl1-filer1 kernel: Apr 17 14:22:44 dl1-filer1 kernel: <<66>>aarrpp:: 1100..224.41..11.41 4m omvoevde df rformo m0 00:0:1100::ff33::2244::ee22:2:82 8t ot o0 00:01:010:f:3f:32:42:4e:2e:25:05 0o no nb cbec1e Apr 17 14:22:44 dl1-filer1 kernel: 0 Apr 17 14:22:44 dl1-filer1 kernel: Apr 17 14:22:49 dl1-filer1 kernel: <<6>a6>rapr:p : 110.02.42.41..114. 14 momvoveedd ffrrom om 0000::1100:f:3f:324::2e42:e:25:500 t too 0000::1100:f:3f3::2244::ee22::282 8o no n bbcce1 Apr 17 14:22:49 dl1-filer1 kernel: e Apr 17 14:22:49 dl1-filer1 kernel: 0 Apr 17 14:23:05 dl1-filer1 kernel: <<66>>araprp:: 1100..242.41..11.144 mmoovveedd ffrroomm 0000::1100::ff33:2:424::e2e2::2288 ttoo 000:010::1f03::f32:42:4:ee2:25:05 0on obcne 1 Apr 17 14:23:05 dl1-filer1 kernel: bc Apr 17 14:23:05 dl1-filer1 kernel: e0 Apr 17 14:23:10 dl1-filer1 kernel: <<66>>aarrp:p : 101.02.42.41..11.144 mmoovevde df rfroomm 0000::1100::f3f:3:2244::e2e:520 :t5o 00 0t:o1 000::f31:024::fe32::242:8e2: 28o no bnc ebc1e Apr 17 14:23:10 dl1-filer1 kernel: 0 Apr 17 14:23:10 dl1-filer1 kernel: Apr 17 14:23:12 dl1-filer1 kernel: <<66>>aarrpp:: 101.204..12.41.41 .m1o4v emdo vferdo m f00r:o1m0 :f03:02:41:0e:2f:32:82 4to: e020::2180 :tfo3: 2040::1e02::f503: 2o4n: eb2c:e500 }}} ",scubaaadan Active Tickets,2146,"syslog full of ""avahi-daemon: Invalid response packet from host"" messages",Backend,8.3.1-RELEASE,,defect,,new,2013-04-23T11:59:54Z,2013-04-23T11:59:54Z,"I have FreeNAS with CIFS and AFP shares exported. All running smoothly, but my syslog is full of messages like that: Apr 23 12:01:23 x48svr61xfreenas avahi-daemon[84639]: Invalid response packet from host 192.168.200.68. There are few messages like this every minute. Various IP addresses are reported, but all refer to Mac OS X machines. Is there any way to decrease avahi log-level not to report it?",macmac Active Tickets,2157,usbhid-ups periodically disconnects due to driver conflict,Backend,8.3.1-RELEASE-p1,,defect,,new,2013-04-26T14:33:06Z,2013-05-01T04:33:34Z,"Subsequent to my upgrade from 8.3.1-beta3 to 8.3.1-p2, the log and console are full of: {{{ usbhid-ups[1928]: Got disconnected by another driver: Device busy }}} I'm 95% certain that this did not happen in 8.3.1-beta3. I'd wager a couple donuts this is probably related to one of the following in the release notes: Changes since 8.3.1-BETA3: 3. Fix a bug that shut down FreeNAS unnecessarily when UPS status was LowBattery but Online. Changes since 8.3.1-RC1: 1. Improve handling of UPS events. Not sure exactly what those mean. Maybe the version of nut was bumped, and then it's more likely their issue? Much of what's online seems to suggest that I could get this message if there were more than one usbhid process running, but that doesn't seem to be the case. I do have two instances of upsmon running, but I gather that's expected behavior. FWIW, here's my full process list: {{{ [root@casa] /var/log# ps ax PID TT STAT TIME COMMAND 0 ?? DLs 0:05.44 [kernel] 1 ?? ILs 0:00.00 /sbin/init -- 2 ?? DL 0:00.24 [g_event] 3 ?? DL 0:01.11 [g_up] 4 ?? DL 0:01.33 [g_down] 5 ?? DL 0:00.00 [crypto] 6 ?? DL 0:00.00 [crypto returns] 7 ?? DL 0:00.00 [xpt_thrd] 8 ?? DL 0:00.00 [g_mp_kt] 9 ?? DL 0:00.01 [pagedaemon] 10 ?? DL 0:00.00 [audit] 11 ?? RL 1183:07.33 [idle] 12 ?? WL 0:36.57 [intr] 13 ?? DL 0:00.50 [yarrow] 14 ?? DL 0:01.38 [usb] 15 ?? DL 0:00.00 [vmdaemon] 16 ?? DL 0:00.00 [pagezero] 17 ?? DL 0:00.06 [bufdaemon] 18 ?? DL 0:00.06 [vnlru] 19 ?? DL 0:01.15 [syncer] 20 ?? DL 0:00.08 [softdepflush] 39 ?? DL 0:00.03 [md0] 49 ?? DL 0:00.00 [md1] 59 ?? DL 0:00.67 [md2] 193 ?? DL 0:01.05 [zfskern] 275 ?? DL 0:00.01 [g_eli[0] ada0p1] 276 ?? DL 0:00.01 [g_eli[1] ada0p1] 278 ?? DL 0:00.01 [g_eli[0] ada1p1] 279 ?? DL 0:00.01 [g_eli[1] ada1p1] 281 ?? DL 0:00.01 [g_eli[0] ada2p1] 282 ?? DL 0:00.01 [g_eli[1] ada2p1] 284 ?? DL 0:00.01 [g_eli[0] ada3p1] 285 ?? DL 0:00.01 [g_eli[1] ada3p1] 287 ?? DL 0:00.01 [g_eli[0] ada5p1] 288 ?? DL 0:00.01 [g_eli[1] ada5p1] 290 ?? DL 0:00.01 [g_eli[0] ada6p1] 291 ?? DL 0:00.01 [g_eli[1] ada6p1] 1169 ?? Is 0:00.05 /sbin/devd 1395 ?? Ss 0:00.08 /usr/sbin/syslogd -s -C 1818 ?? Ss 0:00.53 /usr/sbin/ntpd -g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntpd.drift 1928 ?? Ss 0:00.71 /usr/local/libexec/nut/usbhid-ups -a cp900 1930 ?? Ss 0:00.45 /usr/local/sbin/upsd 1933 ?? Is 0:00.03 /usr/local/bin/upslog -s cp900 -l /var/log/ups.log -i 300 1936 ?? Is 0:00.00 /usr/local/sbin/upsmon localhost 1938 ?? S 0:00.36 /usr/local/sbin/upsmon localhost 2079 ?? Ss 0:00.23 /usr/local/sbin/nmbd -D -s /usr/local/etc/smb.conf 2082 ?? Is 0:00.21 /usr/local/sbin/smbd -D -s /usr/local/etc/smb.conf 2087 ?? I 0:00.04 /usr/local/sbin/smbd -D -s /usr/local/etc/smb.conf 2090 ?? I 0:00.02 /usr/local/sbin/smartd -i 1800 -c /usr/local/etc/smartd.conf -p /var/run/smartd.pid 2127 ?? I 0:01.04 /usr/local/bin/python /usr/local/www/freenasUI/manage.py runfcgi method=threaded host=127.0.0.1 port=90 2186 ?? Is 0:00.00 nginx: master process /usr/local/sbin/nginx 2187 ?? I 0:00.00 nginx: worker process (nginx) 2216 ?? Is 0:00.00 /usr/local/bin/dbus-daemon --system 2220 ?? I 0:00.19 avahi-daemon: running [casa.local] (avahi-daemon) 2256 ?? Ss 0:07.04 /usr/local/sbin/collectd 2353 ?? Is 0:00.00 /usr/sbin/sshd 2376 ?? Ss 0:00.11 /usr/sbin/cron -s 2588 ?? Ss 0:00.04 /usr/sbin/rpcbind 2592 ?? Is 0:00.01 /usr/sbin/mountd -r /etc/exports /etc/zfs/exports 9094 ?? I 0:02.12 /usr/local/sbin/smbd -D -s /usr/local/etc/smb.conf 9095 ?? Ss 0:00.02 sshd: root@pts/0 (sshd) 2742 v0 Is+ 0:00.30 python /etc/netcli 2743 v1 Is+ 0:00.00 /usr/libexec/getty Pc ttyv1 2744 v2 Is+ 0:00.00 /usr/libexec/getty Pc ttyv2 2745 v3 Is+ 0:00.00 /usr/libexec/getty Pc ttyv3 2746 v4 Is+ 0:00.00 /usr/libexec/getty Pc ttyv4 2747 v5 Is+ 0:00.00 /usr/libexec/getty Pc ttyv5 2748 v6 Is+ 0:00.00 /usr/libexec/getty Pc ttyv6 2749 v7 Is+ 0:00.00 /usr/libexec/getty Pc ttyv7 9098 0 Ss 0:00.01 -csh (csh) 9241 0 R+ 0:00.00 ps ax }}} If there's anything I can do to help diagnose/debug please let me know. Thanks. ",bertrem Active Tickets,2158,Correct FAT32 mounting command,GUI,8.3.1-RELEASE,,defect,,new,2013-04-26T22:53:39Z,2013-05-03T16:10:58Z,"Today I've tried to mount my 750GB FAT32 External HD, with FreeNAS interface, in ""IMPORT DISK"". At first it seemed that the import was successful, but nothing was visible inside the mounted path. And worst: in the ""Active Volumes"" screen, it showed that my drive had only 3kb used and 700kb available. I exported the volume and searched for a command that could mount my FAT32 HDD. I've found the mount_msdos command, and with a single ""-o large"" parameter my disk was perfectly mounted. So please change the FAT32/MSDOS Freenas importing with the following command: mount_msdos -o large /dev/XXXXXX /DESTINATION_PATH thanks!",loganderson Active Tickets,2182,zfs snapshot list is not displayed correctly in some browsers,GUI,8.3.1-RELEASE-p2,,defect,,new,2013-05-13T15:10:16Z,2013-05-13T15:11:29Z,"List of snapshots for a zfs volume is not displayed correctly in Safari and Chrome. Only with Firefox list is displayed correctly. With Safari and Chrome only six snashots are displayed. Tested on OS X, naturally. Please see attached screenshots.",shpokas Active Tickets,2193,Give nicer error message when can not contact jails FTP site,GUI,9.1.0-ALPHA,,defect,,new,2013-05-17T19:44:52Z,2013-05-17T19:44:52Z,"Currently, if the mirror for jails is down the error message is that the jail does not exist. This is un-illuminating and misleading, please improve the message.",bmilman Active Tickets,2194,Adjust initial position of new jail dialog,GUI,9.1.0-ALPHA,,defect,,new,2013-05-17T19:46:25Z,2013-05-17T19:46:25Z,"Currently, clicking ""add jail"" and then ""advanced mode"" causes the bottom of the dialog to be pushed off the bottom of the browser window in a full screen browser on 1440x900 desktop resolution.",bmilman Active Tickets,60,Add support for High Availability with HAST/uCARP,Backend,,,enhancement,,new,2010-11-23T12:49:10Z,2012-06-07T00:49:53Z,"Recently the HAST (Highly Available STorage) framework has been added to FreeBSD 8.1 [1]. In combination with uCARP [2] it should be possible to provide HA functionality to FreeNAS. I think it would be a great addition and of huge benefit if FreeNAS would support HA by using 2 FreeNAS servers/VM's. An example configuration for HAST+uCARP can be found at the FreeBSD Wiki [3]. [1] http://www.freebsd.org/releases/8.1R/relnotes.html [2] http://www.freshports.org/net/ucarp/ [3] http://wiki.freebsd.org/HAST",fraenki Active Tickets,102,Installer should check for the size of the destination disk.,Backend,8.0 Beta (r5698),,enhancement,,new,2010-12-19T11:03:42Z,2011-10-07T15:28:35Z,"Hello, The current FreeNAS 8 installer doesn't check for the size of the destination disk/usb stick resulting in a hang like the following: ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Start FreeNAS installation ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ FreeNAS installer for Flash device or HDD. ³ ³ ³ ³ WARNING: There will be some limitations: ³ ³ 1. This will erase ALL partitions and data on the destination disk ³ ³ 2. You can't use your destination disk for sharing data ³ ³ ³ ³ Installing on USB key is the preferred way: ³ ³ It saves you an IDE, SATA or SCSI channel for more hard drives. ³ ³ ³ ÃÄProceed with the installation onto ad0?ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ [ Yes ] No ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ File Sanity Check -> OK /cdrom/FreeNAS-amd64-embedded.xz (1/1) 55.5 % 33.7 MiB / 248.6 MiB = 0.135 3.8 MiB/s 1:04 1 min 0 s The destination disk was only 256 MB.",tnkflx Active Tickets,125,Energy plan; Suspend to RAM; Suspend to Disk; WOL,FreeBSD,8.0 Beta (r5698),,enhancement,,new,2011-01-16T10:05:44Z,2012-07-30T22:37:11Z,"The normal homeusers (95% of the users) use the nas for backup and filestorage. Normaly they do not need 24/7 Freenas service. To save energy and money, it would be fine, if freenas has some configurable energy save plans. In the Supend to RAM Mode (S3), normaly you reduce power consumption by 90% So the requested features are: 1. wake up on lan (wol) 2. power off the disks after some time 3. suspend to RAM (S3) 4. suspend to disk (or usb stick) Wake up on Lan: Nearly all Linux versions using ethtool to config the Networkcards with the following params: p - Wake on phy activity u - Wake on unicast messages m - Wake on multicast messages b - Wake on broadcast messages a - Wake on ARP g - Wake on MagicPacket(tm) s - Enable SecureOn(tm) password for MagicPacket(tm) d - Disable (wake on nothing). This option clears all previous options It would be fine, if you add this functionality to your development plan. BR Rainer",wumpus Active Tickets,295,Include Refresh/Reload button for all tabs/views/etc.,GUI,8.0-RC5,,enhancement,,new,2011-04-26T20:08:24Z,2011-04-26T20:08:24Z,"Once you have clicked on a node in the tree view and opened a tab (eg. View All Volumes => Storage), it's not possible to reload the latest information/state without removing the tab (by clicking on the X) and then clicking on the node once again. It would seem sensible to add a ""Refresh"" or ""Reload"" button for EVERY tab (probably in the header, ie. Refresh/Account/Help/Log Out) so that the latest information can be re-loaded without having to kill tabs and re-open them.",MilhouseVH Active Tickets,313,GUI: nfs port range (portmapper),GUI,8.0-RELEASE,,enhancement,,new,2011-05-03T13:35:11Z,2011-08-27T01:56:37Z,"At the moment, it's currently not possible to specify the ports that various NFS services should use, either via the GUI or via the standard /etc/nfs.conf. Being able to specify this would be useful for firewall rules etc.",mwhitworth Active Tickets,342,Add ability to grow/resize a volume (ZFS),Backend,8.0-RELEASE,,enhancement,,new,2011-05-11T10:24:07Z,2011-05-13T18:06:22Z,"I've got a (virtual) FreeNAS 8.0 appliance with 200 GB disk space. Lately I've grown the (virtual) disk to 500 GB, but FreeNAS does not provide a way to grow the logical volume. It should be possible to resize or at least grow a ZFS volume with FreeNAS. (I know it's not possible for UFS, but ZFS should work.) Is there a way to grow the volume on the CLI? Just asking for a workaround until resize is offcially supported :)",fraenki Active Tickets,439,8.0.1-beta3 feature request monitor cpu temp in web ui,Backend,8.0.1-BETA2,,enhancement,,new,2011-06-17T05:28:37Z,2011-08-27T06:15:23Z,has everything else why not add cpu temp as well ;).,dw5304 Active Tickets,440,8.0.1-beta3 feature request display smart output of last diag test,Backend,8.0.1-BETA2,,enhancement,,new,2011-06-17T05:30:49Z,2011-06-22T21:17:55Z,would like to see the output of the smart test via webif,dw5304 Active Tickets,446,Ability to mount a .iso,Backend,8.0-RELEASE,,enhancement,,new,2011-06-17T13:58:12Z,2011-06-17T13:58:12Z,"It would be nice to be able to mount an iso from the web. I guess we can do it in command line, though.",ubellavance Active Tickets,633,change default freenas cron jobs in gui,Backend,8.0.1-BETA4,,enhancement,,reopened,2011-08-19T14:23:05Z,2013-03-01T16:47:03Z,"Freenas runs default cron tasks. They start running scheduled at 3 am. My nas is not on 24/24, so these tasks never run. I tried editing and saving the cron file, but after reboot its back to original.These scheduled tasks are not visible in the gui These default tasks are daily/weeklymonthly reports, cachetool things etc.. Would be nice if these tasks would be editable in the gui.",lyzanxia Active Tickets,668,Tree Menu & Tab consistency issues,GUI,8.0.1-BETA4,,enhancement,,new,2011-08-26T22:21:23Z,2011-08-26T22:21:23Z,"There are operations that can be performed in the tree menu that cannot be performed using the ""tabbed"" section of the UI. The first place that comes to mind is 'System->Cron Jobs', 'System->Rsync Tasks', and 'System->S.M.A.R.T. Tests', these operations can only be launched within the tree menu. The opposite can also be true; some operations like 'Factory Restore', and 'Rebuild LDAP/AD cache' can only be performed within the tabbed section of the UI and not in the tree. We should consider consolidating UI operations like these ones to a central location, or display in both the tree and the tab. It feels very difficult to locate things at times and I believe this to be the cause. ",james Active Tickets,670,User should be warned when changing network configuration,GUI,8.0-RELEASE,,enhancement,,new,2011-08-26T22:47:51Z,2011-08-26T22:47:51Z,Many appliances warn folks when changing their network configuration that it will potentially drop their existing connections // they will need to reconnect to IP/hostname w.x.y.z. FreeNAS should do the same.,gcooper Active Tickets,680,UPS service test diag needs to be added to the CLI and/or GUI,Backend,8.0.1-BETA4,,enhancement,,new,2011-08-27T00:40:06Z,2011-08-27T00:40:32Z,Users have complained about UPSes not working out of the box. A diag command should be added to the GUI and/or CLI to verify that UPS functionality is sane.,gcooper Active Tickets,728,FEATURE - Identifying failed disks,GUI,8.0.1-RC1,,enhancement,,new,2011-09-05T09:00:51Z,2011-10-06T20:57:50Z,"I run a NAS system with 16 SATA disks. Sometimes i changed the physical order of the disks moving them also to other SATA ports. No problem because FreeNAS is identifying the disk via the uuid of the disk and not via the device name of FreeBSD (like /dev/da5). But is there any chance to identify them for me? How do I identify a failed disk in my system? ",willytenner Active Tickets,739,Enhance serial console option in CLI,Backend,8.0.1-RC1,,enhancement,,new,2011-09-07T01:50:23Z,2011-09-07T01:50:23Z,"I can login to the box today and choose Use Serial Console, but there are two catches: 1. It favors the VGA console over the serial console (/boot/loader.conf: comconsole=""vidconsole,comconsole""). 2. It hardwires the port that's on to com1. Some servers and machines have more than one port (e.g. Dells and Supermicros) because one port is reserved for the BMC SOL console, whereas the other port is available for the physical RS232 port. That and some hackers might have a NIC with more than one port installed in their machine.. Please watch out for potential conflicts between UPS configuration and 2.",gcooper Active Tickets,772,Log rollover required,FreeBSD,8.0.1-RC1,,enhancement,,new,2011-09-12T18:29:40Z,2011-09-12T21:29:33Z,"/var's space is limited, and with boxes that have a large amount of uptime, /var will fill up with useless logs and other files, causing potential issues related to system access, daemon operation, etc. One way this can be prevented is by implementing syslog rollover to ensure that /var/log/ doesn't get clogged up with stale data in excess of X number of megabytes.",gcooper Active Tickets,775,Installer should present a list of time zones when doing a fresh install,Backend,8.0.1-RC1,,enhancement,,new,2011-09-12T22:25:17Z,2011-09-12T22:25:17Z,Feature request. Installer should present a list of time zones when doing a fresh installer and store that in database.,delphij Active Tickets,791,Add method to update/purge settings from database when using command line,GUI,8.0.1-RC1,,enhancement,,new,2011-09-16T22:27:31Z,2011-09-17T19:58:15Z,"It seems to becoming more common where people want to manage ZFS or other settings from the command line and settings get out of sync with the database or don't persist. For example doing a zpool import from the command line, or renaming your pool from the command line. It would be helpful to purge or update the settings in the database without knowledge of sqlite3 and the database structure. Even documenting those sqlite3 commands to delete certain objects/settings from the database would be helpful.",protosd Active Tickets,889,Better support for Samba shadow copy with multiple tier snapshots,Backend,8.0.1-RELEASE,,enhancement,,new,2011-10-06T14:47:46Z,2011-10-06T14:48:40Z,"Samba/shadow copy and ZFS snapshots, nice job guys. But there's one little problem. Some of us who are setting up long-term snapshot strategies will have several tiers of backups. For example, we might snapshot: every 15 minutes and retain 2 hours every hour and retain 12 hours every 6 hours and retain 2 weeks every week and retain 5 years Which is intended to allow both oops-style recovery and quiescent/stable versions of files, but not necessarily every edit ever made. The problem is that due to the format assigned in the smb.conf, Samba picks one of the tiers and offers just those to Samba users. It would be awesome if users could look at all available revisions. ",jgreco Active Tickets,890,Please add support for snapshots at greater intervals,Backend,8.0.1-RELEASE,,enhancement,,new,2011-10-06T14:51:53Z,2011-10-06T14:51:53Z,"It'd be really handy to have snapshot capability at greater intervals than just weekly. Any possibility of adding 2 weeks 1 month 2 months 3 months ? Thanks for consideration.",jgreco Active Tickets,936,Support for css themes,Backend,8.0.2-RELEASE,,enhancement,,new,2011-10-19T21:12:45Z,2011-10-19T21:12:45Z,"Allow for customization of the GUI CSS, offer hostname in header, possibly custom logo, etc. See forum http://forums.freenas.org/showthread.php?3268-feature-request-support-for-css-themes In particular, there's some confusion caused by the use of the short hostname; at some sites, 3LD is used for site and 4LD is used for service/hostname. For example, ""freenas0.iad.yahoo.com"" might be a FreeNAS box in Washington DC while ""freenas0.ord.yahoo.com"" might be one in Chicago. Very little is offered in the GUI to differentiate these two. Other people may want customization for different reasons.",jgreco Active Tickets,954,Allow to change ZFS mount point,Backend,8.0.2-RELEASE,,enhancement,,new,2011-10-26T10:05:59Z,2011-10-26T10:05:59Z,"The current GUI, if mount point changed, it will produce error on 'Storage/Active Volumes' tab. So, I am asking to allow mount point to change and this will also fix the bug. Reason: I can share a single folder and the underlying structure can be source from multiple pools/dataset.",erictam Active Tickets,963,Unable to make initial ip configuration of lagg interface without reboot,Backend,8.0.2-RELEASE,,enhancement,,new,2011-10-28T05:36:51Z,2011-10-28T06:51:46Z,"After clean installation of Freenas (8.0+)I configure lacp NIC bonding (em0 + em1) via console tool. After that I'm tying to configure new interface IP address but it is not listed untill I reboot. Another bug is that even after reboot when i sccuessfully configure ip address for lagg interface I still can't use it until I rebbot the server once again.",isirotin Active Tickets,1008,Difficult to change IP address and netmask via web UI,GUI,8.0.3-RELEASE-p1,,enhancement,,new,2011-11-14T01:54:37Z,2012-02-01T09:59:14Z,"Right now, if you have to change both the ip address of your management interface, and the default gateway, at the same time, due to IP renumbering/subnet migration or other reasons, it is as far as I can tell impossible to do it safely via the web UI, and its necessary to instead accomplish it via the console or a remote ssh connection. This could be easily changed if Network Settings > Global Configuration and Network Settings > Interfaces were moved into a single tab, so that these values could be easily and safely changed at the same time.",wgwilkins Active Tickets,1022,Better sort out reporting screens,GUI,8.0.2-RELEASE,,enhancement,,new,2011-11-19T01:11:28Z,2011-11-19T12:45:07Z,"A user commented that the following output would be better for the reporting GUI: 1. Group by functional group (interfaces, CPU, diskspace, etc). 2. Insert explicit 'newline' breaks for each functional group. That would make it possible for people with larger horizontal real estate to browse the reporting graphs without having to scroll excessively down the screen.",gcooper Active Tickets,1030,Blanks spaces in Usernames,Backend,8.0.2-RELEASE,,enhancement,,new,2011-11-21T20:31:13Z,2011-11-21T20:42:27Z,"All, Is there a way to include spaces in the username when setting up new users in the GUI. If there has been a request for this please forgive me. I searched and could not find anything on this. thanks",stanoc Active Tickets,1051,Need GUI for configuring what traps to send and per-trap configuration dialogs,GUI,8.0.2-RELEASE,,enhancement,,new,2011-11-29T06:56:58Z,2011-11-29T06:57:08Z,"There are a large number of SNMP traps in SNMPv2. We really need to define which notifications shall be supported and sent, and add an advanced GUI (I would argue a separate sub GUI) for this feature. We can map out the requirements at a later date, as the traps and their relative configuration are somewhat complex and the current GUI doesn't even support doing this today in an intuitive manner.",gcooper Active Tickets,1053,"Provide a means to configure rsync jobs, etc on a staggered basis",GUI,8.0.2-RELEASE,,enhancement,,new,2011-11-29T23:38:20Z,2011-11-29T23:38:20Z,"User requested that we provide a means for configuring the start times of jobs, e.g. rsync tasks, in order to stagger them and ensure that the system doesn't get slammed all at once.",gcooper Active Tickets,1090,Need to distinguish 'disabled/enabled' from 'starting/started/stopping/stopped' in the GUI under the services panel,GUI,8.0.2-RELEASE,,enhancement,,new,2011-12-12T19:06:40Z,2011-12-12T19:06:40Z,"Today the GUI overloads enabled/disabled with enabled/disabled + starting/started/stopping/stopped . What I would like is a modal that tells me whether or not a service is enabled/disabled (text that relays the state would be just fine -- no fancy images would be required), as well as what state the service is currently in (starting/started/stopping/stopped).",gcooper Active Tickets,1119,Need a dialog or checkbox for moving user home directories,Backend,8.0.2-RELEASE,,enhancement,,new,2011-12-22T00:34:41Z,2011-12-22T00:35:52Z,"If a user's home directory exists and a user is moved via 'modify user' it can leave the user orphaned, a bit and confuse some applications. So I propose that a checkbox where IFF the homedir changed, the directory should be moved. We shouldn't blindly use -m or move the home directory because it could be shared, but iterating through the entire user list in order to figure out whether or not a home directory is shared could be expensive as well. I would postpone this enhancement until user/group caching is polished up to the point where it's efficient to iterate through to determine whether or not a home directory is shared, etc.",gcooper Active Tickets,1131,Select Which E-Mail Notifications to Receive,Backend,8.0.3-RC1,,enhancement,,new,2011-12-27T11:45:41Z,2011-12-29T00:47:47Z,"Hello: I have FreeNAS 8.0.3 RC1 and every night it sends me two e-mails. It would be nice if you could choose to receive only critical e-mails. Otherwise, I have to turn it off completely.",gbentley111 Active Tickets,1134,Warn a user prior to making data inaccessible via mount,Backend,8.0.2-RELEASE,,enhancement,,new,2011-12-28T13:20:01Z,2011-12-29T00:42:14Z,"Pretty sure at this point that's what happened to this guy http://forums.freenas.org/showthread.php?5379-FreeNAS-8-0-2-ZFS-RAIDZ-Size-issue If a proposed mountpoint doesn't exist, go ahead and use it. If it exists but is empty, that's probably fine too, but there may be edge cases. If it exists and isn't empty, I suggest that this is a problem that should not be silently ignored. My preferred solution would probably be to refuse to create the mountpoint at all.",jgreco Active Tickets,1185,Setting to adjust reporting interval,GUI,8.0.2-RELEASE,,enhancement,,new,2012-01-13T00:51:22Z,2012-01-13T00:51:22Z,"When looking at the reporting/diagrams, it would be good to be able to adjust the frequency/interval at which the diagrams/charts are updated, so one doesn't have to wait for so long to see the current/new values. Preferrably easily accessible in the Reporting view, maybe as a complement to having this setting in the regular Settings view. If possible also having a button to refresh a given and/or all charts would be nice (perhaps one button per chart), in case there's one of particular interest.",rawtaz Active Tickets,1253,"CIFS [homes] ""hide dotfiles"" option missing",GUI,8.0.3-RELEASE-p1,,enhancement,william,accepted,2012-02-06T16:00:16Z,2012-02-28T13:55:06Z,It isn't possible to select whether the dofiles in the [homes]shares are hidden or not,bubulein Active Tickets,1257,Avoid reboots after upgrade,Backend,8.0.3-RELEASE-p1,,enhancement,,new,2012-02-06T22:56:15Z,2012-02-06T22:56:15Z,"(Just wanted to write this down so it won't get lost). Currently, after an upgrade from Web GUI, the system would reboot twice, one time is for booting from the new image, run migration, etc. It seems to me that the reboot after a *successful* migration is not really necessary unless we hit something special in the future and thus can be avoided. Marking this as 'minor' priority since this is not a frequently used feature.",delphij Active Tickets,1286,'compactor' functionality for zvols,Backend,8.0.4-BETA1,,enhancement,,new,2012-02-16T07:22:26Z,2012-02-16T09:42:21Z,"One of the things that was brought up in #freenas is that although we're using thin provisioning with zvols, there isn't a way to compact data and reclaim used space, either via ZFS or via iSCSI. A user (echorelay) asked that we add the functionality to have feature parity with VMware, etc. The chat log follows. {{{ 22:25 < echorelay> another question for ya - why do not re-gain free space after deleting data? 22:25 < dw5304> the pool size 22:25 < echorelay> do I not * 22:25 < gcooper> echorelay: depends on whether or not you are taking snapshots 22:25 < echorelay> I just built the server today 22:25 < echorelay> no chance to create snapshots 22:26 < gcooper> i honestly have no idea given the info i have so far 22:26 < gcooper> which isn't much TBH 22:26 < echorelay> do you guys have any idea how I CAN get that free space back ? 22:26 < gcooper> again, i have no idea what's 'using' the free space :) 22:27 < dw5304> u sure u dont have any shapshots ? 22:27 < echorelay> well, example, I copied some ISO's over to the iscsi target. Used space increased, free space decreased. I then deleted the ISO, however the free space and used space stayed the same 22:27 < dw5304> ah 22:28 < dw5304> cause windows really dont delete files ;P 22:28 < echorelay> what you mean? 22:28 < dw5304> or not fromwhat i have seen 22:28 < dw5304> on my end 22:28 < dw5304> works the same w/ vhd's 22:28 < gcooper> indeed 22:28 < echorelay> yep, I have seen that with vhd's... but there is a way to reclaim free space 22:28 < echorelay> i've seen that with apple time machine backups too 22:28 < dw5304> gcooper? 22:29 < dw5304> no idea on my end 22:29 < gcooper> well... that's because you have a second app that reclaims space 22:29 < gcooper> 22:28 < dw5304> works the same w/ vhd's 22:29 < gcooper> 22:28 < gcooper> indeed 22:29 < dw5304> no i mean to reclaim 22:29 < dw5304> :P 22:29 < dw5304> like u can do w/ the vhd compactor 22:29 < dw5304> app 22:29 < echorelay> ^^ this is what I am referring too 22:29 < dw5304> disk degrage 22:30 < dw5304> then compact the -- 22:30 < dw5304> 00 22:30 < dw5304> 00's 22:30 < echorelay> there is no ""compactor"" within freenas 22:30 < echorelay> as far as I can tell 22:30 < gcooper> if there was one, it would need to be between istgt and zfs 22:31 < echorelay> wasn't sure what ""scrub volume"" was so I clicked that and it didn't do anything either 22:31 < gcooper> i can say based on the former, it probably doesn't exist :) 22:31 < echorelay> gcooper: so what do you do when you fill up your volumes? 22:31 < dw5304> lol well theres something that needs to be created then :P 22:31 < gcooper> echorelay: delete? 22:31 < gcooper> but that's a very good question i suppose 22:31 < echorelay> I have, thats just it. I delete files, but the free space isn't regained 22:32 < gcooper> i'll raise it on the support tracker 22:32 < echorelay> you mean delete the volumes? }}}",gcooper Active Tickets,1324,Add configuration database versioning mechanism,Backend,8.0.1-RELEASE,,enhancement,,new,2012-03-04T11:11:56Z,2012-03-04T18:39:14Z,"Right now if one upgrades and doesn't save their config, they generally have to start from scratch and configure everything. Not really a big deal for most SOHO types, but it's a bigger deal for other folks with larger/more complex installs. The easy-button solution for life to be made easier for users IMHO would be to have multiple copies of the config database with versioning in the filename. This would be combined with some symlink magic, where the symlink would only be mangled when the configuration database is migrated (this is recommended to avoid munging with all of the /data/freenas-v1.db hardcoding around the source tree and also as a past of least development pain), or if a sequence number/versioning dump of the config file wasn't compatible with the running binaries. An example of the latter case is: freenas-v1.db was pointing to an 8.2.0 config and I booted 8.0.4 (this is purely hypothetical, but this is an example of what people would want). Eventually.. given the above observation, it might be a good idea to use a proper versioning scheme tied in between the source base, the build system, and our middleware, instead of just pasting v1.db on every configuration database. This will require additional work though in the build system and middleware to determine database versioning though, so I wouldn't recommend doing this.",gcooper Active Tickets,1328,Add configuration database versioning safety belts,Backend,8.0.1-RELEASE,,enhancement,,new,2012-03-04T11:33:29Z,2012-03-04T11:33:29Z,"Today if I load a configuration database from 8.2.0 in 8.0.4, things won't go well (let's just put it that way ;)..). What really would be nice is to have a safety belt that would prevent people from running an uprev config database in a downrev version of FreeNAS.",gcooper Active Tickets,1344,LOG_CRIT+ messages should be reported to root via alert system,Backend,8.2.0-BETA1,,enhancement,,new,2012-03-04T19:03:33Z,2012-03-04T19:03:33Z,"I'd have to doublecheck whether or not samba uses the right severity, but in general any items that are a certain syslog(3) log priority should be passed along to root, so critical items can be tracked (say, disk failure? mps channel droppage? etc) and there will be a proper audit log to help articulate that there's a problem that needs resolving on the host system. This is a touchy item as it can result in more support emails than necessary, so extensive testing with various failure conditions and soak testing will need to be applied. I do not recommend this for FreeNAS 8.2.0, but instead 8.3.0.",gcooper Active Tickets,1456,"Manually create a ""Periodic Snapshot""",GUI,8.2.0-BETA2,,enhancement,,new,2012-04-11T15:41:32Z,2012-04-11T15:41:32Z,"After posting in the forums for discussion ([http://forums.freenas.org/showthread.php?6661-Periodic-Snapshots-Create-snapshot-now&p=25735 here]), I was instructed to open a ticket directly. I'll copy paste it here. As the title explains, give users the possibility to manually create a automatic snapshot now. This is different from the normal ""create manual snapshot"" in that the newly created snapshot will be ""owned and managed"" by the periodic snapshot mechanism: IE: deleted at the end of its allotted lifetime. If the periodic task is replicated, it means the snapshot will also be automatically replicated. Also, it will show up on CIFS's shadow_copy2. It can also make sure your data is snapshotted on the spot if you just made an important modification (or right before, for that matter). Finally, it can also make testing your configuration easier. IMO, not a huge functionality, but probably not that hard to implement either, and part of those little plus-es that makes things friendlier, better, and more convenient. See the images for an idea of how to plug this in.",monarchdodra Active Tickets,1471,gui upgrade: no progress after upload firmware,GUI,8.3.0-RELEASE-p1,,enhancement,,new,2012-04-19T18:49:41Z,2012-12-27T16:01:26Z,"i see step2 progress bar while uploading the firmware in gui, but i think it would be good to open the console or see another progress of the gui upgrade. i just did this and it took about 7min before the system reboot screen showed up, always feels like a hold your breath moment when upgrading. system is rebooted 2 times and working otherwise. thanks!",labtopia Active Tickets,1472,IO Chart per DataSet,GUI,8.0.2-RELEASE,,enhancement,,new,2012-04-19T19:56:40Z,2012-04-19T19:56:40Z,"Would be very useful iostat charts on reporting menu, helping detect bottles from storage/disks.",alaska Active Tickets,1484,Alert user on hard reboot / power failure,Backend,8.2.0-BETA2,,enhancement,,new,2012-04-23T15:27:49Z,2012-04-23T15:27:49Z,"Currently (checked with FreeNAS-8.2.0-BETA3-x64 on vmware workstation with 4 disks in a RaidZ1) if the system is hard rebooted (due to a power failure or cord tripping ;) the user is not informed directly in the web-interface. I think as this can be a serious problem there should be a warning visible. Maybe yellow light instead of red. Currently only the console says: WARNING: /data was not properly dismounted",tamada Active Tickets,1507,Multi-folder MiniDLNA scan,GUI,8.2.0-BETA3,,enhancement,william,accepted,2012-05-03T19:24:24Z,2012-08-28T13:54:24Z,"I was testing the MiniDLNA plugin in 8.2 BETA3, and found that I needed to move every media folder into one to make them all available in MiniDLNA. Instead of ""CHOOSE ONE FOLDER"" for scanning, several folders should be configured. Wouldn't that be better?",loganderson Active Tickets,1584,Individual S.M.A.R.T. Temperature Triggers,GUI,8.0.4-RELEASE-p2,,enhancement,,new,2012-06-17T23:14:29Z,2012-07-31T12:37:50Z,"Hi. I've verified my HDD's manuals and noticed they work with different ""Operation Temperatures"", where one could go from 0º to 60º and other from 5º to 65º, for example. With that, I tought I'd choose which S.M.A.R.T. alarms would fire on which HDD on some temperatures, based on different Thresholds. We need those individual thresholds so I don't need to be worried for no reason, when one more resistant HDD triggers a temperature that would never be a problem for him. So, in short, there should be different temperatures SMART alarms/email for each HDD in ""View Disks"" tab, and not ""overall"" e-mail triggers for temperature alarms in ALL disks. What do you think?",loganderson Active Tickets,1698,Request for FreeNAS to make use of Csync2 to help make synchronization easier of a setup of more than two Freenas hosts.,Backend,,,enhancement,,new,2012-08-01T12:46:06Z,2012-08-01T12:46:06Z,"Good day I would like to make a suggestion of having a page / setup for the tool Csync2. The idea behind it is, to not have to many rsync modules, and really to make synchronization easier of a setup of more than two hosts. --- About csync2 ---- Csync2 is a cluster synchronization tool. It can be used to keep files on multiple hosts in a cluster in sync. Csync2 can handle complex setups with much more than just 2 hosts, handle file deletions and can detect conflicts. --------------------- http://oss.linbit.com/csync2/ Csync2 is created by the company that gave us DRBD. I hope you will give my suggestion some thought. Kindest Regards Brent Clark",BClark Active Tickets,1726,Ability to specify the SSL ciphers used,Backend,8.2.0-RELEASE-p1,,enhancement,,new,2012-08-15T18:05:19Z,2012-08-15T18:05:19Z,"Right now FreeNAS is using CAMELLIA ciphers by default. Is it possible to define a tunable that will allow to define in Nginx the ciphers used? For example: {{{ ssl_prefer_server_ciphers on; ssl_ciphers RC4:HIGH:!aNULL:!AESGCM:!CAMELLIA:!EDH:!MD5; ssl_session_cache shared:SSL:5m; ssl_session_timeout 10m; }}} This is an important aspect, related to securing https in Nginx.",TECK Active Tickets,1733,Make CD-ROM upgrader smarter,Installer,,,enhancement,,new,2012-08-17T23:10:20Z,2012-08-17T23:10:20Z,"It's desirable to make CD-ROM installer smarter, for example, make the upgrade inside a chroot environment before finalizing the installation.",delphij Active Tickets,1780,Request support of VMXNet3,FreeBSD,8.3.0-BETA2,,enhancement,,new,2012-09-07T12:43:24Z,2012-09-07T12:43:24Z,It would be great if we could get support of VMXNet3 adapters. Overall it seems to get better suppport from VMWare than VMXNet2 and may provide jumbo frame support.,cmessin1 Active Tickets,1781,Please provide options for specifying Alignment and Sector Size for UFS creation.,Backend,8.3.0-BETA2,,enhancement,,new,2012-09-07T14:33:51Z,2012-09-08T01:17:42Z,"While ZFS generally seems to be prefered, some users still run UFS on hardware raid. It would be usefule if the GUI had the option of specifying aligmnment when creating UFS volumes. Also, sector size option would be usful for ases in which drive reporting may be incorectly read.",cmessin1 Active Tickets,1789,Fix to Automatic Scanning for MiniDLNA Plugin,FreeBSD,,,enhancement,,new,2012-09-09T14:18:30Z,2012-10-24T09:42:48Z,"There has been a lot of complaints about the fact that MiniDLNA cannot recognize changes to the files and update accordingly. I have a fix which does still have 1 issue but it works 99% of the time. I would like to see the wait_on function added and a script added to the MiniDLNA PBI. As for configuration, the PBI should address wait_on being enabled or disabled (in case of some issues), The media path must be specific to each directory the media is stored in (wait_on is not perfect), and a user selectable delay to rebuild the database (default could be 300 seconds). Please see this posting for details. I have a valid script which works in a jail. http://forums.freenas.org/showthread.php?8671-MiniDLNA-Automatic-Rescan-A-work-in-progress&p=37048&viewfull=1#post37048",JoeSchmuck Active Tickets,1798,Use proper htaccess/htpasswd in FreeNAS,GUI,,,enhancement,,new,2012-09-16T03:14:33Z,2012-09-19T12:15:46Z,"I strongly recommend to abandon the current GUI login and replace it with a proper Nginx htaccess popup, which is much more secure. Nginx allows you to define custom not-authorized error pages also, which is more efficient.",TECK Active Tickets,1812,Web UI does not have a way to add drives as mirrors,GUI,,,enhancement,,new,2012-09-24T19:11:07Z,2012-09-24T19:11:07Z,"The Web UI does not have a way to take a drive and add it as a mirror. Either turning a singleton into a mirror, or making a 3 (or more) way mirror. (This isn't the same as replacing a drive in a mirror, although that may be the ultimate goal.) Not a huge priority, I realize, but there are quite a few uses for doing this. ",sef Active Tickets,1859,Warn user if UFS is very large,GUI,,,enhancement,william,new,2012-10-23T20:00:11Z,2012-10-24T00:08:45Z,"We should warn user if UFS is very large, for instance, if it's larger than 5TB, it's very inefficient to fsck and ZFS is preferred. (Also if the user choose more than 5 disks, 'stripped' should not be an option or the user should at least be warned).",delphij Active Tickets,1879,Set status to yellow when /var or /etc (or others?) fills up,Backend,8.3.0-RELEASE,,enhancement,,new,2012-10-30T16:01:56Z,2012-10-30T16:01:56Z,"See also forum post: http://forums.freenas.org/showthread.php?8733-Error-after-going-to-release-8-20&p=41398&viewfull=1#post41398 Summary: /var/log/samba/log.nmbd got to 128MB in 5 days and filled /var Setting status to yellow when /var, etc get to 90% (or whatever) will allow e-mail notification when/if https://support.freenas.org/ticket/1845 is implemented. Since filling up causes all kinds of problems, being notified if drive space gets very low is critical (i think). Thanks",greco Active Tickets,1911,"""Custom options "" needed for afpd in GUI",GUI,8.3.0-RELEASE,,enhancement,william,accepted,2012-11-21T08:48:47Z,2012-11-21T10:35:34Z,"Setting up timemachine shares would benefit from the availability (via the GUI) of the option ""volsizelimit"" for afpd. This would be useful either via a 'custom options' field for afp shares, or a proper option in the afpd settings. This option is useful when announcing a single large share, where apples' timemachine will only ""see"" the disk as being of size ""volsize"". (A quota of 100G on a 1T share will let timemachine see the 1T and try to fill it up, which breaks things). The volsize option allows for one large bonjour/avahi announce, instead of many (one per timemachine share). The reason for wanting only one avahi announce is that avahi will announce all shares using one packet. When adding more shares the announcents will no longer fit inside a single packet and avahi falls over with an error of: ""avahi-daemon[53535]: Record too large, cannot send"". For me things broke when announcing the 21st timemachine share... Technical details: Option is used inside /usr/local/etc/Applevolumes.default Example: ""/mnt/store1/tm_onelarge"" ""tm_onelarge"" options:usedots,nohex,upriv,tm dperm:0644 fperm:0755 ea:ad allow:@staff rwlist:@staff volsizelimit:524288 ",sjoerd Active Tickets,1917,DDNS support for dns.he.net,Backend,8.3.0-RELEASE,,enhancement,,new,2012-11-27T08:59:22Z,2012-12-03T12:49:40Z,"pretty straight forward, descriptions are available on dns.he.net a https request can get the job done",realdreams Active Tickets,1932,Add SMART support and serial #s through hptiop(Highpoint) driver,Backend,8.3.0-RELEASE,,enhancement,,new,2012-12-04T22:40:52Z,2012-12-18T10:16:13Z,"This is a followup from ticket 1872(https://support.freenas.org/ticket/1872). I have a Highpoint RocketRAID 4520 until the end of 2012 and I would like to add SMART support and serial numbers to the GUI of FreeNAS. This controller was sent to me on loan so I can test and ensure that FreeNAS works well with this new generation of controllers. William and I had taken a look at this before and it is not an easy fix. He wasn't sure how we were going to get it to work(or IF we could get it to work). The Highpoint FreeBSD CLI didn't appear to give any indication of what physical ports were in use to allow a link between daXX and PortXX on the controller. He was going to consult some other people and do a little more research. This ticket is only to track that this controller still does not have SMART support(developers are busy people!) to ensure that this feature is added, if possible. This ticket is not meant as a ""how about now"" ticket. If its too low on the priority that is fine, I'll just let Highpoint know and they can decide what they want to do. I do have SSH and FTP access for a FreeNAS server setup for anyone to log into. Send me a PM in the forums for the IP and username/password. The server contains no actual data. I would like to have this fixed before the end of the year since I got this card from Highpoint so that we can ensure proper support for this new generation of controllers. Because this controller uses the hptiop driver I believe that adding support for SMART and serial numbers will actually benefit the entire 45xx, 43xx and 35xx families of cards. I am actually using build 12712(nightly build from shortly after 8.3.0 was released) since it has support for the controller. I kept the same installation since William may have stuff installed unique to what we were doing. I can install the latest nightly on request. Thanks!",noobsauce80 Active Tickets,1938,Audible sound at start and shutdown?,Backend,8.3.0-RELEASE,,enhancement,,new,2012-12-08T01:29:38Z,2013-05-09T17:18:50Z,"My pfsense box plays a small 3 melody chime when the machine completes booting up and when it begins a shutdown sequence. Can this feature be added to FreeNAS? I would imagine it would be easy to implement. ",noobsauce80 Active Tickets,1974,VirtualBox can't be installed inside a Jail due to kernel module dependency,FreeBSD,8.3.0-RELEASE,,enhancement,jpaetzel,accepted,2012-12-29T16:30:45Z,2013-04-09T16:01:35Z,"I have been trying to find a solution on how to install VirtualBox on a FreeNAS host. With memory so cheap, the power of a FreeNAS box should be enough for a couple of virtual servers. The problem I have come across is the fact that FreeBSD jails share the kernel with the host and Virtualbox needs to load a module into the kernel. I have found a possible solution for installing the kernel module on the host and then installing virtualbox inside a jail. This solution however assumes a full FreeBSD host where the ports tree can be used. http://forums.freebsd.org/showthread.php?t=21897 I quickly tried to install virtualbox-ose-kmod-legacy using pkg_add on the host, but I couldn't load it due to ""KLD vboxnetflt.ko: depends on netgraph - not available or version missmatch"". I haven't dug any deeper into this problem. What I call for is support for software add-ons that require kernel modules to be loaded on the host.",aahlborg Active Tickets,1981,show link status of network cards in web gui,GUI,8.3.0-RELEASE-p1,,enhancement,,new,2013-01-02T11:18:54Z,2013-01-02T11:18:54Z,"It would be handy to have the link status of network interfaces, on / off and the actual link speed.",rm Active Tickets,2002,"When a zvol is extended, which i believe is only allowed currently via CLI, the iscsi subsystem is not aware of this change",Backend,,,enhancement,,new,2013-01-15T21:06:16Z,2013-01-30T23:08:33Z,"when a zvol is created for use by iscsi and has to be extended via the CLI zfs set volsize=XXXG ZFSVOLUME/zvol the iSCSI subsystem does not show the disk has changed until it is restarted. I would like to request a CLI command to refresh this information without shutting down existing iSCSI sessions. Perhaps even allow changing the zvol size out of the gui and have it refresh on its own? I noticed a similar enhancement made earlier to allow new iSCSI targets to be created without restarting the service. Thank you in advance - Al",TheSov Active Tickets,2015,Feature request: ZFS snapshot: restore snapshot,GUI,,,enhancement,,new,2013-01-25T23:17:32Z,2013-01-25T23:17:32Z,"Add a ""restore"" button right in the snapshot view which would initiate a restore operation. The operation is as follows: - Create a new snapshot, named ""before-restore-