archive-org.com » ORG » F » FREENAS.ORG

Total: 927

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • [How-To] Transmission & FreeNAS Shared Mount Points | FreeNAS Community
    This is how i did it and may alleviate some other peoples troubles Users and Groups Required for Transmission Jail to use the zfs shared mounts How to configure Transmission to put ALL of the torrent data on those shared mounts including the resume and torrent folders How to structure the zfs mount points so you can restrict things down properly and prevent incomplete torrents from showing up in other plugins like couchpotato or minidlna It is a high level overview of what I did with screenshots It lists a few shell commands but people should be familiar with a linux shell as i don t outline all the commands step by step I wrote it after I did the configuration so some steps may or may not be right if you spot anything wrong let me know so i can update it Click to expand Hi Thanks for taking the time to write this up helped me tremendously as I am new to this transmission and freenas Everything seems I am downloading my first torrent to work fine However I took a look into the settings json file after restarting transmission and saw that my changes were overwritten with the original file So I am not sure if the incomplete override you recommended would work michael d Nov 16 2013 2 Offline MtK FreeNAS Aware Member Since Jun 22 2013 Messages 395 Message Count 395 Likes Received 22 Trophy Points 18 Occupation Web Developer Location NL MtK Dec 2 2013 Great post ndboost though I have a few issues which are not directly related to your guide so I will open a seperate thread for them the only related issues is I ve set the Incomplete as you suggested also in the settings json but the directory is always

    Original URL path: https://forums.freenas.org/index.php?threads/how-to-transmission-freenas-shared-mount-points.15962/ (2016-02-01)
    Open archived version from archive

  • SpiderOak installation into a Jail (FreeNas 9.2) | FreeNAS Community
    inotify dir watcher syscall inotify init not implemented Apr 2 15 53 39 freenas kernel linux pid 94289 inotify dir watcher syscall inotify init not implemented Click to expand Turns out you can ignore this msg as BSD uses Kqueue and not inotify The shutdown issue was because I was forgetting to tell spideroak to run in the background and closing the shell window was killing the process Thanks again HP N54L Microserver 16GB RAM 6x Hitachi DeskStar 5K3000 in RAIDz2 FreeNAS 9 3 fullmetaljester Apr 3 2014 4 Offline thewizard Member Since Apr 1 2014 Messages 2 Message Count 2 Likes Received 2 Trophy Points 3 thewizard Apr 4 2014 Hey mate I ve found a similar issue the GUI interface times out after awhile and even if you leave the Jail Terminal window open it eventually stops the process and SpiderOak ceases to upload I fixed it by adding a Cron job to my FreeNAS My Jail ID is 2 you can get it apparently by running the cmd jls The Cron job itself is simple jexec 2 spideroak headless I set the job to run once a day just before midnight Perfect for my needs thewizard Apr 4 2014 5 Offline fullmetaljester Member Since Dec 24 2013 Messages 15 Message Count 15 Likes Received 1 Trophy Points 1 Occupation Sr Datacenter Engineer Location Boston fullmetaljester Apr 5 2014 I pushed it into the background this way spideroak headless from the jail shell been running nonstop for days HP N54L Microserver 16GB RAM 6x Hitachi DeskStar 5K3000 in RAIDz2 FreeNAS 9 3 fullmetaljester Apr 5 2014 6 Offline fullmetaljester Member Since Dec 24 2013 Messages 15 Message Count 15 Likes Received 1 Trophy Points 1 Occupation Sr Datacenter Engineer Location Boston fullmetaljester May 2 2015 I can confirm this process still works with the 5 1 8 port and the 5 2 0 install file Just rename it to 5 1 8 Also you will need to run the following before starting the Spideroak install pkg install linux base c6 6 6 4 sysctl compat linux osrelease 2 6 18 set this one in your Jail config to make permanent HP N54L Microserver 16GB RAM 6x Hitachi DeskStar 5K3000 in RAIDz2 FreeNAS 9 3 fullmetaljester May 2 2015 7 Offline maikthulhu Member Since Jul 14 2015 Messages 2 Message Count 2 Likes Received 0 Trophy Points 1 Location Pullman WA maikthulhu Jul 14 2015 I m using FreeNAS 9 3 and was having trouble getting this going current version in ports tree as of this writing is 5 1 8 I tried following the instructions here but kept having trouble so here is my attempt to fill in the gaps by providing step by step what worked for me Hope this helps Create a standard jail Add storage I concur that anything you attach should be in Read Only mode On your FreeNAS host get a shell and type kldload linux Make this load at boot by modifying boot loader conf and adding linux load YES I haven t tested the above because I don t want to reboot but I m pretty sure that s how you do it The rest of these commands are performed in the jail Update the ports tree portsnap fetch extract portsnap fetch update Create the distfiles folder mkdir usr ports distfiles Go to the distfiles folder cd usr ports distfiles Get SpiderOak 5 2 0 fetch https spideroak com getbuild platform slackware arch i386 dummy SpiderOak 5 2 0 i686 1 tar gz Rename the package to reflect a 5 1 8 version number and expected extension mv SpiderOak 5 2 0 i686 1 tar gz SpiderOak 5 1 8 i686 1 tgz Go to the SpiderOak ports folder cd usr ports net spideroak Generate new checksums so the Makefile can build using the 5 2 0 package make makesum Attempt the install make install The install fails at this point stating it can t find PIL imaging so I m assuming some files were renamed because I found imaging so which seems to fit the bill so cd work stage usr local share spideroak cp imaging so PIL imaging so Go back to the port s folder cd Attempt the install again make install clean Attempting to run SpiderOak now results in complaints about missing libsodium so I wasn t sure where to look but since it s a Linux program with Linux libraries I decided to grab the 32 bit debian package to source the missing library First go to tmp cd tmp Next grab the debian package fetch http http us debian org debian pool main libs libsodium libsodium13 1 0 3 1 i386 deb Extract the debian package tar zxvf libsodium13 1 0 3 1 i386 deb Extract the data archive tar zxvf data tar xz Go to the folder containing library files cd usr lib i386 linux gnu Copy files to SpiderOak s share folder cp libsodium so 13 usr local share spideroak Go to SpiderOak s share folder cd usr local share spideroak Create a symlink for libsodium so ln s libsodium so 13 libsodium so Clean up cd tmp rm r libsodium usr control tar gz data tar gz debian binary Now just follow the instructions above for setting up SpiderOak and you re good to go maikthulhu Jul 14 2015 8 Offline dreamerns Member Since May 1 2015 Messages 3 Message Count 3 Likes Received 0 Trophy Points 1 dreamerns Jul 16 2015 I ve been using spideroak for more then a year I recently built a FreeNAS box and started switching all my stuff there Making SpiderOak run on it is the last piece of the puzzle I haven t solved I was able to run 5 1 8 in jail it required linux base c6 6 6 4 however I noticed some bad issues Spideroak installs SpiderOak Hive folder by default On first run it copied all mu stuff there and

    Original URL path: https://forums.freenas.org/index.php?threads/spideroak-installation-into-a-jail-freenas-9-2.19868/ (2016-02-01)
    Open archived version from archive

  • vmxnet3.ko for FreeNAS 9.X in ESXi 5.5 | FreeNAS Community
    Feb 15 2014 Ya I m working on that as well as a compile for 9 2 1 however Github is currently checking out a multi 100 MB repository to me at 30KiB s so it ll be awhile David E Feb 15 2014 5 FREAKJAM likes this Offline cyberjock Forum Guard Dog Admin Member Since Mar 25 2012 Messages 18 609 Message Count 18 609 Likes Received 1 444 Trophy Points 113 cyberjock Feb 15 2014 I know several people would appreciate a how to on compiling this stuff This is often asked for in various fashions Usually it s someone using less than the latest version of FreeNAS with the less than the latest version of ESXi In my case I m using 9 2 0 with ESXi 5 1 Hardware recommendations RAID5 RAIDZ1 is dead Read my guide It answers common questions newbies to FreeNAS have Only you can prevent flame wars Read the FreeNAS manual SpoilerTarget Show My Main System FreeNAS 9 3 STABLE whatever is the latest Intel Xeon E3 1230v2 Supermicro X9SCM F 32GB DDR3 ECC 1600 RAM 32GB SATA DOM Cyberpower 1500AVR Ten WD Red WD60EFRX NAS Hard Drives RAIDZ2 40 9TB usable space 10GbE Chelsio adapter cyberjock Feb 15 2014 6 Offline David E Newbie Member Since Nov 1 2013 Messages 75 Message Count 75 Likes Received 12 Trophy Points 8 David E Feb 16 2014 Added a module for 9 2 1 x64 and rough instructions for doing it yourself Its possible I missed steps since I made the instruction list a couple weeks after doing it myself let me know and I ll be happy to update the original post cyberjock You may want to try the 5 5 tools build with 5 1 they tend to try to stay pretty backwards compatible with the OS level drivers David E Feb 16 2014 7 Offline cyberjock Forum Guard Dog Admin Member Since Mar 25 2012 Messages 18 609 Message Count 18 609 Likes Received 1 444 Trophy Points 113 cyberjock Feb 17 2014 And the 5 5 vmxnet3 ko does work with 5 1 Woohoo Not too useful for my purposes But it does work Hardware recommendations RAID5 RAIDZ1 is dead Read my guide It answers common questions newbies to FreeNAS have Only you can prevent flame wars Read the FreeNAS manual SpoilerTarget Show My Main System FreeNAS 9 3 STABLE whatever is the latest Intel Xeon E3 1230v2 Supermicro X9SCM F 32GB DDR3 ECC 1600 RAM 32GB SATA DOM Cyberpower 1500AVR Ten WD Red WD60EFRX NAS Hard Drives RAIDZ2 40 9TB usable space 10GbE Chelsio adapter cyberjock Feb 17 2014 8 Offline FREAKJAM Member Since Oct 10 2013 Messages 20 Message Count 20 Likes Received 2 Trophy Points 3 FREAKJAM Feb 17 2014 I can confirm the latest vmxnet3 ko works with FreeNAS 9 2 1 ESXi 5 5 Thanks alot FREAKJAM Feb 17 2014 9 Offline ajohnson Member Since Feb 25 2013 Messages 18 Message Count 18 Likes Received 1 Trophy Points 3 ajohnson Feb 25 2014 Thanks for documenting all of this David I have a compile setup on my end for this as well It s working quite nicely I do have one question when a FreeNAS update occurs do you do a full make clean make release cycle or have you worked out some way of git pulling and compiling updates without needing to do a make clean would be much faster in theory ajohnson Feb 25 2014 10 Offline David E Newbie Member Since Nov 1 2013 Messages 75 Message Count 75 Likes Received 12 Trophy Points 8 David E Feb 25 2014 I was planning on testing this tonight for the 9 2 1 1 release I think I can just stash pull rebase stash pop on the parent repo delete the os I forget the name here build directory and fetch checkout the new release tag for the two sub repos I ll give it a go and report back David E Feb 25 2014 11 Offline ajohnson Member Since Feb 25 2013 Messages 18 Message Count 18 Likes Received 1 Trophy Points 3 ajohnson Feb 25 2014 Great thanks much Also I wanted to contribute the method I was using before I read this thread It actually used make buildenv to set the environment up so that it builds using the FreeNAS FreeBSD toolchain in such a way that you can build the driver outside of the source directory I don t know that this is really more useful than your method but I ll put it here in case it is of interest I guess the one benefit of this approach is that you don t actually need to build the full FreeBSD kernel FreeNAS release if you don t want to you can just build the kernel module Before performing these steps follow David s instructions up to and including Check out FreeNAS I use a slightly different directory for the FreeNAS source below so just consider that Instructions for creating a vmxnet3 driver for FreeNAS from outside the FreeNAS build directory Code text Set the environment up to use the FreeNAS FreeBSD build toolchain instead of the system s default toolchain cd usr local freenas FreeBSD src make buildenv Assuming your vmware tools distrib is extracted in a directory structure as below do the following cd usr local vmware tools distrib lib modules source tar xvf vmxnet3 tar cd vmxnet3 only SYSDIR usr local freenas FreeBSD src sys make The ko file should now live in usr local vmware tools distrib lib modules source vmxnet3 ko ajohnson Feb 25 2014 12 David E likes this Offline David E Newbie Member Since Nov 1 2013 Messages 75 Message Count 75 Likes Received 12 Trophy Points 8 David E Feb 25 2014 So fetching then checkout of the new tag combined with deleting the os base directory worked fine for me and I added 9 2 1 1 I also

    Original URL path: https://forums.freenas.org/index.php?threads/vmxnet3-ko-for-freenas-9-x-in-esxi-5-5.18280/ (2016-02-01)
    Open archived version from archive

  • vmxnet3.ko for FreeNAS 9.X in ESXi 5.5 | Page 2 | FreeNAS Community
    Smart UPS 3000 Dual Power supply on all equipment with 1 PS to each UPS pbucher Aug 4 2014 30 Offline cyberjock Forum Guard Dog Admin Member Since Mar 25 2012 Messages 18 609 Message Count 18 609 Likes Received 1 444 Trophy Points 113 cyberjock Aug 4 2014 pbucher said And you know what all boxes virtual or non virtualized can one day get pissed at you That s not exactly anything new in the world of IT Click to expand You re back huh Yes but when it s significantly more virtualized than non virtualized you can t ignore the extra risk because any box can get pissed at you You wouldn t punch a lion in the face would you But one might eat you next time you are on a Safari adventure in Africa It s all about risk mitigation something you personally don t seem to understand Hardware recommendations RAID5 RAIDZ1 is dead Read my guide It answers common questions newbies to FreeNAS have Only you can prevent flame wars Read the FreeNAS manual SpoilerTarget Show My Main System FreeNAS 9 3 STABLE whatever is the latest Intel Xeon E3 1230v2 Supermicro X9SCM F 32GB DDR3 ECC 1600 RAM 32GB SATA DOM Cyberpower 1500AVR Ten WD Red WD60EFRX NAS Hard Drives RAIDZ2 40 9TB usable space 10GbE Chelsio adapter cyberjock Aug 4 2014 31 Offline pbucher FreeNAS Aware Member Since Oct 15 2012 Messages 180 Message Count 180 Likes Received 18 Trophy Points 18 Location napp it is fun pbucher Aug 4 2014 cyberjock said You re back huh Yes but when it s significantly more virtualized than non virtualized you can t ignore the extra risk because any box can get pissed at you You wouldn t punch a lion in the face would you But one might eat you next time you are on a Safari adventure in Africa It s all about risk mitigation something you personally don t seem to understand Click to expand Nope I m not back I m just poking the caged tiger Actually I deal with risk mitigation all the time which is why when I poke caged tigers I use a long stick Anyways I don t know where you get your info but their is like 0 risk due to virtualization of FreeNAS when you do it right And just like anything else in IT when you get fancy things get messy Think of it has the difference between using the restore disk provided with a stock dell model vs using the retail OEM windows disk and a custom built home brew system And yes some folks should just buy the dell I get that but you won t ever learn how to make a good home brew system if you always buy from the Dell web page Enough now going back to enjoying my supported virtual SAN Ask Me ESXi 5 5U2 32GB RAM 8 vCPU VMXNet3 LSI 9207 8e 24 Seagate Constellation ES 3 SAS 1TB RAID 10 SuperMicro SC847E26 JBOD LSI 9207 8i ZeusRAM for SLOG SuperMicro X9DRW 3TF Intel E5 2650 128GB ECC DDR3 RAM Dual APC Smart UPS 3000 Dual Power supply on all equipment with 1 PS to each UPS pbucher Aug 4 2014 32 Offline spidernas Member Since Mar 26 2014 Messages 10 Message Count 10 Likes Received 0 Trophy Points 1 spidernas Aug 5 2014 Please let s not get this thread locked It s the only one that has vmxnet3 ko updates spidernas Aug 5 2014 33 Offline pbucher FreeNAS Aware Member Since Oct 15 2012 Messages 180 Message Count 180 Likes Received 18 Trophy Points 18 Location napp it is fun pbucher Aug 6 2014 spidernas said Please let s not get this thread locked It s the only one that has vmxnet3 ko updates Click to expand Well I m guilty of not deploying 9 2 1 6 so I can t answer for it but the stock drivers provided with ESXi 5 x have worked fine all except for 1 or two of the releases in the 9 2 x series where you had to compile the drivers in order to use them I m thinking it was maybe 9 2 1 or something like that I deployed at some level every build in the 9 2 x series up to 9 2 1 5 and once ix backed out the one kernel patch that changed the APIs in the kernel the stock drivers have worked great Anyways let s not lock the thread Ask Me ESXi 5 5U2 32GB RAM 8 vCPU VMXNet3 LSI 9207 8e 24 Seagate Constellation ES 3 SAS 1TB RAID 10 SuperMicro SC847E26 JBOD LSI 9207 8i ZeusRAM for SLOG SuperMicro X9DRW 3TF Intel E5 2650 128GB ECC DDR3 RAM Dual APC Smart UPS 3000 Dual Power supply on all equipment with 1 PS to each UPS pbucher Aug 6 2014 34 Offline jgreco Resident Grinch Member Since May 29 2011 Messages 8 130 Message Count 8 130 Likes Received 1 274 Trophy Points 113 Location WHO 1 ville Unixland jgreco Aug 6 2014 spidernas said OT I still don t get this overblown aversion to virtualizing FreeNAS People seem to want it why ignore this user base Click to expand It s not an aversion Feel free to go and do it I posted a guide to it somewhere It is even very well thought out in ways that n00bs tend not to understand The problem with virtualizing FreeNAS is that unlike a typical virtual machine most people are trying to store huge amounts of data A virtual environment is already an incredibly complex abstraction and a ZFS system is also an incredibly complex abstraction If you are not careful and thoughtful with your strategy you will end up in an M C Escher painting that you may become hopelessly trapped in See for example I give the very good advice to use actual disks by passing

    Original URL path: https://forums.freenas.org/index.php?threads/vmxnet3-ko-for-freenas-9-x-in-esxi-5-5.18280/page-2 (2016-02-01)
    Open archived version from archive

  • vmxnet3.ko for FreeNAS 9.X in ESXi 5.5 | Page 3 | FreeNAS Community
    reliable FreeNAS VM for small scale file storage and you re willing to commit appropriate resources in the form of VM datastores there are options available Click to expand Small scale server consolidation is really what interests me The common use case being dumping antiquated fileservers I can throw RAID at datastores it s what we ve always done But the thought of dumping hardware raid and gaining the benefits of ZFS is compelling In addition if the 10Gb ethernet drivers function reliably we should be able to get fantastic network and shared data performance within the host Ideally I d like to have 10Gb SAN like performance to the collection of VM s running iop intensive apps and skip the wire Plus add replication and all the other ZFS goodness It is very easy to make a strong business case for the esxi host and additional hardware necessary when so many functions can be centralized Vt d so far gives me a pretty strong comfort level and allows me to migrate from hardware RAID Virtualized overhead is minimal The ability to boot to baremetal with full pool access seems like a great solution It also allows easy performance comparisons between virtualized and baremetal implementations Your passed through redundant datastores is an interesting thought in terms of performance though the magical loss of data pools bothers me Things fail for a reason In an smb world A virtualized freenas solution hits many of the targets ZFS AD ISCSI AFP replication and backup services all wrapped up in a decent gui I just want it to play nice in my already virtualized environment There is also no hope in hell of rolling out something that can randomly refuse to mount a pool I was going to start Known Good SAFE and FAST esxi thread hoping that the gurus would pitch in Throw it in an experimental or performance section whatever But didn t really want to incur cyberjocks wrath So instead of improving the product and figuring out how to tweak it We have to all retreat to our own little holes and never speak of the innovation and cool things we pull off Thanks for all your posts jgreco We ve wandered OT but this is by far the most active esxi thread Rebel 9 2 1 9 x64 Intel S1200v3RPS Xeon e3 1220v3 32GB ECC Intel Rs2wc080 Flashed 9211 8i IT 6x 2TB striped mirrors Koolaid 9 2 1 9 x64 SM x10SL7 F Xeon e3 1230v3 32GB ECC Seasonic G 550 SM 846TQ mjws00 Aug 13 2014 47 Offline jgreco Resident Grinch Member Since May 29 2011 Messages 8 130 Message Count 8 130 Likes Received 1 274 Trophy Points 113 Location WHO 1 ville Unixland jgreco Aug 13 2014 mjws00 said But the thought of dumping hardware raid and gaining the benefits of ZFS is compelling Click to expand That makes me nervous the hardware RAID for primary disk VM storage and for ESXi boot vm conf files seems like a real good idea This veers off into the world of VM design philosophy though and in my philosophy a VM should be designed such that it has a base system disk in some ways quite similar to the FreeNAS install image and then add on additional disks for application use or better NFS mounting of application data So a lowish performance RAID controller ironically still the favored M1015 around here except this time with IR firmware is still desirable from my point of view In addition if the 10Gb ethernet drivers function reliably we should be able to get fantastic network and shared data performance within the host Click to expand Unnecessary Try running iperf on two E1000 s on two VM s on the same host It already goes faster than gigE There s some debate as to which option is better vmxnet or E1000 Vt d so far gives me a pretty strong comfort level Click to expand It might give you a less strong comfort level if you run into some of the gotchas I ve seen Things suddenly not working correctly after an upgrade of either ESXi or FreeNAS comes to mind Your passed through redundant datastores is an interesting thought in terms of performance though the magical loss of data pools bothers me Things fail for a reason Click to expand Well that s easily enough explained So you re some guy on a budget who has managed to install ESXi on something that vaguely qualifies as a compatible whitebox You have several disks a 1TB and two 2TB s attached to the motherboard SATA ports You think gee I could get FreeNAS goodness So you make a VM with three 1TB VMDK s in RAIDZ1 on your unprotected datastores Now maybe you know or maybe you don t know what happens with ESXi when it loses access to a datastore Typically it freezes VM I O So a failed disk that s appearing via the ESXi I O abstractions because it is an ESXi datastore can cause the FreeNAS VM to freeze This isn t what you intended or expected So you also had the ESXi host mounting NFS from the FreeNAS VM in a wonderful loopback fashion cuz you know you re SO clever and look how smart you are ZFS protected VM s Except that now all your VM s using the NFS datastore also freeze And in a panic you cannot tell what s going on and reset the ESXi host How much of a betting person are you Because we ve seen stuff like this and it s resulted in pool damage My best estimation is that the freezing of the I O is somehow very bad and the reset of the hypervisor leaves the pool in an inconsistent state and we can agree that SHOULDN T happen but seen it As you say things fail for a reason So when you listen to me say

    Original URL path: https://forums.freenas.org/index.php?threads/vmxnet3-ko-for-freenas-9-x-in-esxi-5-5.18280/page-3 (2016-02-01)
    Open archived version from archive

  • vmxnet3.ko for FreeNAS 9.X in ESXi 5.5 | Page 4 | FreeNAS Community
    5 U1 FreenasVM 16GB RAM FreeNAS 9 3 amd64 ZFS RAIDZ2 6 HDDs 2GB LSI 9211 8i Intel RES2SV240 with direct path I O ESXi Chelsio S320E LP in direct path mode Fusion io 80GB SLC LOG in direct path mode AFP CIFS NFS BTsync plugin Crashplan plugin Plex plugin Nik Mar 22 2015 71 Offline David E Newbie Member Since Nov 1 2013 Messages 75 Message Count 75 Likes Received 12 Trophy Points 8 David E Apr 4 2015 So it looks like they have moved to a new mechanism for releases where they are much more frequent and aren t receiving new revision numbers just dates I updated the original post but you have to figure out the date of the release you are upgrading to open up its MANIFEST file and find the Git revision number then build the kernel for precisely that revision I just upgraded to 9 3 myself so I haven t seen what the in GUI update mechanism looks like does anyone know if it lists a date there I m a little bit frustrated by this release process since it means everything will be far more frequent with less end user communication about each one and I have to assume less testing So far the module I built for the latest rev seems to be working but it will need more testing If anyone has been having problems feel free to update to the rev posted in the OP and let me know how it goes And keep in mind you can t take arbitrary updates anymore without possibly breaking your network David E Apr 4 2015 72 Offline Nanderson87 Member Since Jun 11 2015 Messages 1 Message Count 1 Likes Received 0 Trophy Points 1 Location Florida Nanderson87 Jun 11 2015 Just wanted to offer my thanks here and bump this thread My ESXi host was getting crashes from my FreeNas VM due to what seemed like the E1000 NIC adapter Had to switch to vmxnet3 adapter to try and clear it up OF course even in the nice new 9 3 the vmxnet3 isn t recognized This guide along with your link fixed me right up and I m about the farthest thing from a Linux guy you can get I downloaded your stable release unzipped and put into an iso Mounted the iso to the virtual machine mounted it to a cd drive folder in the FreeNAS shell copied the vmxnet3 file from the cd folder to boot modules added the tunable per your guide rebooted and it sees them just fine Had to reconfigure the adapter since it replaced an E1000 then reboot once more and we re back in business Nanderson87 Jun 11 2015 73 Offline Spearfoot Newbie Member Since May 13 2015 Messages 73 Message Count 73 Likes Received 17 Trophy Points 8 Spearfoot Jun 17 2015 Thank you for this post I have been testing FreeNAS 9 3 STABLE 201506042008 running on VMware ESXi 6 0 0 build 2715440 and the VMware supplied VMXNET3 driver does indeed fail under load when used for either NFS or iSCSI datastores My test is simple I spin up two Windows VMs and simultaneously run the ATTO disk benchmark on them Things seem great at first with incredibly fast transfer rates But inevitably the underlying datastore goes South and the benchmarks stall With iSCSI based datastores I see this sequence of FreeNAS console messages Code text WARNING 10 0 58 1 iqn 1998 01 com vmware 554fa508 b47d 0416 fffc 0cc47a3419a2 2889c35f no ping reply NOP Out after 5 seconds dropping connection WARNING 10 0 58 1 iqn 1998 01 com vmware 554fa508 b47d 0416 fffc 0cc47a3419a2 2889c35f connection error dropping connection With NFS based datastores there are no console or error messages or any other indication of a problem except that the vSphere client shows the NFS datastore in italicized typeface when it goes off line Oddly despite their underlying datastore being off line the Windows VMs don t halt or crash Eventually the datastores wake up and the Windows VMs respond to input The benchmarks then run to completion albeit very slowly Today I will try to find time to compile the driver using these instructions and see if these problems persist EDIT Let me add that when I move the datastores over to an E1000 based configuration the test case works fine both for NFS and iSCSI But both have slower and or less consistent read rates coupled with abysmally slow write rates SpoilerTarget Show my systems PC Workstation Windows 7 Ultimate Supermicro C7P67 Intel Core i7 2600K 3 4GHz 16GB Kingston RAM 1 x 120GB Samsung 850 EVO boot drive 4 x 1TB Seagate ST1000DM003 in 2TB RAID 10 array on IBM M1015 HBA NVidia Quadro 2000d video card 2 x Samsung S24C450 24 displays 1920x1200 FreeNAS system FreeNAS 9 3 STABLE always latest version Running virtualized as VMware ESXi v6 0 VM with 2 vCPUs and 16GB RAM on Supermicro X10SL7 F Intel Xeon E3 1241v3 3 5GHz 32GB Crucial ECC RAM Motherboard s LSI 2308 controller passed through to FreeNAS VM via VT d per best practices 1 x 16GB SanDisk Cruzer Fit ESXi boot drive 2 x 60GB Edge Boost Pro Plus SSD ESXi datastore including mirrored FreeNAS boot images 7 x 2TB HGST 7K4000 drives in a 10TB RAID Z2 pool tank on LSI 2308 Synology DS411 II NAS Diskstation 5 x Proprietary system w Intel Atom D525 1 8GHz 4GB RAM 4 x 4TB RAID 6 volume 2 x 4TB WDC Re WD4000FYYZ 2 x 4TB HGST DeskStar NAS HDN724040ALE640 Test system FreeNAS 9 3 STABLE always latest version or VMware ESXi v6 0 Supermicro X8SIE LN4F Intel Xeon X3460 2 8GHz 24GB Hynix ECC RAM 1 x 16GB SanDisk Cruzer Fit FreeNAS boot drive 1 x 16GB SanDisk Cruzer Fit VMware 6 0 ESXi boot drive 4 x 500GB WDC drives set up as 2 mirrored vdevs in a

    Original URL path: https://forums.freenas.org/index.php?threads/vmxnet3-ko-for-freenas-9-x-in-esxi-5-5.18280/page-4 (2016-02-01)
    Open archived version from archive

  • vmxnet3.ko for FreeNAS 9.X in ESXi 5.5 | Page 5 | FreeNAS Community
    interesting stuff depending on your topology needs It doesn t hurt jgreco Oct 22 2015 81 You must log in or sign up to reply here Show Ignored Content Page 5 of 5 Prev 1 2 3 4 5 Share This Page Tweet Your name or email address Do you already have an account No create an account now Yes my password is Forgot your password Stay logged in FreeNAS

    Original URL path: https://forums.freenas.org/index.php?threads/vmxnet3-ko-for-freenas-9-x-in-esxi-5-5.18280/page-5 (2016-02-01)
    Open archived version from archive

  • migrating from openfiler | FreeNAS Community
    Geek Member Since Feb 29 2012 Messages 2 736 Message Count 2 736 Likes Received 310 Trophy Points 83 pirateghost Feb 8 2014 1 backup data to another device external hdd different server etc 2 install FreeNAS 3 set up your zpools datasets zvols shares etc 4 copy data back 5 enjoy pirateghost Feb 8 2014 2 Offline sbertsch Member Since May 12 2015 Messages 10 Message Count 10 Likes Received 0 Trophy Points 1 sbertsch May 12 2015 pirateghost lets take this a step further and my question is the same one the CIFS SAMBA shares sure no problem The block storage is the question what if we have openfiler up and running and want to replace it wholesale for freeNAS is it possible to move the external block storage and migrate the targets without destroying the data Thanks in advance Scott sbertsch May 12 2015 3 You must log in or sign up to reply here Show Ignored Content Share This Page Tweet Your name or email address Do you already have an account No create an account now Yes my password is Forgot your password Stay logged in FreeNAS Community Home Forums FreeNAS Forum How To Guides

    Original URL path: https://forums.freenas.org/index.php?threads/migrating-from-openfiler.18293/ (2016-02-01)
    Open archived version from archive