I'm not sure if this has been seen with others but after my upgrade from 4.5.6 to 4.7 I lost all my NFS exports. The only way I could get them to export again is go into my shares and re-apply the shares without changing anything to the shares.

 

No biggie just took me a little time before I noticed them gone and found where the root of my problem was.

For your shares to be exported, you will need to click apply again to each share.

I think the release notes mentioned some changes that were made to NFS that would have requires what you ended up doing.

Nice memory prostuff.

http://lime-technology.com/forum/index.php?topic=9252.msg88255#msg88255

o Fixed issue with NFS where it's possible a client NFS-mount could refer to a different server resource as a result of configuration changes on the unRaid server.  NOTE: if you are using NFS, I strongly suggest you un-mount any NFS client connections to your unRaid server before updating to this release.  Following re-boot with this release, you will need to go to the Shares page and click 'Apply' for each User Share that you want exported via NFS.  Subsequent client NFS mounts should be ok and be preserved across server config changes and re-boots.

 

Following are the technical details:

 

All NFS-exported shares will have an explicit 'fsid' value set.  For disk shares, and the cache share, it's set as follows:

for cache, fsid = 10

for diskN, fsid = 10+N (ie, for disk1 it's 11, for disk2 it's 12, etc.)

 

For user shares, the first time a share is configured for NFS export, we assign an fsid to it (stored in the 'shareExportNfsFsid' variable in the user-share config file).

 

The fsid's are assigned starting at 100.  Once an fsid is assigned to a user share, that fsid stays with that share (but if the share is deleted and later re-created, it will get a different fsid).  Also fsid's are never re-used.

 

The next fsid to be assigned is kept in the 'shareNfsFsid' config variable in the 'share.cfg' file.

Okay, you've been pretty misinformed by someone. Been running this stuff for over 4 years or so, no issues I didn't cause myself lol. I have two servers, both have been through upgrades of everything with no loss.

 

You need to understand how unRAID works and how it's different. Each disk except parity stores data on standard file systems (ResiserFS). You could power down and remove ANY of those data drives and mount them in a Linux computer to read them with no issue. If you lose the parity drive you lose the data protection but not the data. If you lose two drives then whatever was on those drives is lost. If you lose one drive you lose nothing. An uber fast CPU or a pile of memory will do nothing but burn more electricity and generate more heat since neither of those is a performance bottleneck in an unRAID system.

 

By the drives you need to store the data you HAVE and then buy ONE more. when you run low dial up NewEgg and order ONE more drive. Maybe keep a spare around if you're paranoid. Every single time I see a deal on drives and don't need them and have bought I have regretted it because by the time I am ready to use the damned thing drives cost LESS! I have a TON of media too, more DVD and BD movies than I can stand and I'm nowhere near needing 20 drives. Unless you intend to not compress them, which is silly, you aren't going to need that kind of space and you're just going to waste power. Start with what you need, grow as needed - been there, done that.

 

Buying solid hardware up front is a good idea. Buying a good 80+ PSU, a good drive enclosure, a good case, and enough SATA ports for expansion is all good. Mind you I have had an 8port card sitting for nearly a year since I end up replacing small drives with big ones instead of adding more drives but someday I'll need it I'm sure. I have some Supermicro cages that are even older