tag:blogger.com,1999:blog-6864028793041725839.post1541388735490017096..comments2013-12-11T02:03:31.686-06:00Comments on Stuff that I have done through learning by error!: FreeBSD ain’t free, if I value my time and include the cost of confusion!LBEhttp://www.blogger.com/profile/06085240525687793307noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6864028793041725839.post-16445452354984770592013-05-26T06:50:01.043-05:002013-05-26T06:50:01.043-05:00Ugh. So much fail in a single post.
[quote]
I am ...Ugh. So much fail in a single post.<br /><br />[quote]<br />I am currently in the process of implementing L2ARC using a CF card in a CF/IDE adapter...<br />[/quote]<br /><br />CF cards have a max read speed of 20 MB/s. Hard drives have at least 100 MB/sec read speed. So you want to implement a SLOWER THAN HDD device as L2Arc? LOL<br />Your money is better spent buying more RAM.<br /><br />[quote]<br />Initially FreeNAS was reliable and seemed to be performant, but I had to go and add sabnzbd to download ... favorite TV shows from supernews and add Sick-Beard to handle setting up the downloads. What’s the harm with a couple of little Python programs? It wasn’t that difficult to hack Python 2.6, sabnzbd and Sick-Beard into my embedded version of FreeNAS.<br />[/quote]<br /><br />Really? This is a NAS, as in Network Addressed STORAGE. Making a DEDICATED STORAGE HANDLER do other chores is not smart. At all.<br /><br />Also, regarding your comments on how ZFS development is dead, I guess that zfs feature flags, data compression on l2arc and the other recent additions to zfs's capabilities are evidence that it is "dead".<br /><br />Seriously, research more.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6864028793041725839.post-60131516697624894062011-04-12T19:23:01.954-05:002011-04-12T19:23:01.954-05:00Haha. Nice post. I've been using FreeNAS for...Haha. Nice post. I've been using FreeNAS for a few weeks now and my experience has been very similar to yours. I'm particularly glad that you posted about the perl script that you used to free up inactive memory. I researched that today and improved my throughput 2-3 times what it was when doing large transfers.<br /><br />I hear that a lot of these issues have been addressed in FreeBSD 8.2 and ZFS version 15 included in that release. Sadly, even though FreeNAS 0.8 is marked as a release candidate I don't think it's anywhere as mature a product as 0.7 is. Maybe in due time...Unknownhttps://www.blogger.com/profile/15832912295554798418noreply@blogger.comtag:blogger.com,1999:blog-6864028793041725839.post-30705039443114013742010-10-17T17:57:29.639-05:002010-10-17T17:57:29.639-05:00Could you P L E A S E point out on how you managed...Could you P L E A S E point out on how you managed to install Python 2.6 on an embedded FreeNAS installation? And even more precisely, did you manage to run Python 2.6 apps? Since SABnzbd and Sick Beard both don't require Python 2.6. They just run fine on the already installed Python 2.5.4. Thanks in advance!injectxhttps://www.blogger.com/profile/10605071556016518470noreply@blogger.comtag:blogger.com,1999:blog-6864028793041725839.post-70098449699657843032010-09-08T12:20:40.612-05:002010-09-08T12:20:40.612-05:00I didn't read your entire post but...from what...I didn't read your entire post but...from what I have read on the Internet the WD EADS drives don't use the new 4k sector "Advanced Format" technology, it's the EARS models with 64MB cache that use this. Also, from what I've, any drive with 64MB cache is using the new 4k sector. Now, if I could only get a definitive answer as to whether ESXi 4.1 works with the new 4k sector format off the shelf. There's alot of postings but no sure answers...Anonymousnoreply@blogger.com