What is a file server?

Essentially, a file server is a computer that stores files, is attached to a network, and provides shared access of those files to multiple workstation computers.  File servers do not perform computational tasks - that is, they do not run programs for client machines.  Furthermore, they do not provide dynamic content like a web server.  Still further, file servers are not like database servers in that the former do not provide access to a shared database whereas the latter do.  File servers provide access to static files via a local intranet through Windows or Unix protocols as well as over the internet through file transfer or hypertext transfer protocols (FTP and HTTP). 

What can you do with a file server?

The primary function of a file server is storage.  For the home user, one central storage location can increase overall computing efficiency and reduce overall computing cost.  By placing all of your important files in a single location, you do not need to worry about different versions of files you're actively working on, wasting disk space by having multiple copies of less-than-important files scattered on different systems, backing up the right files onto the right backup storage medium from the right computer, making sure every PC in your home has access to the appropriate files, and so on. 

From a system builder's perspective, a file server can also liberate your various workstation computers from having to accommodate multiple hard drives, and decrease overall hard drive expenditures.  With the rise of SSDs, which offer tremendous performance at a high cost per GB, a file server can free workstations from the performance shackles of platter-based disks - an especially useful consideration for laptops and netbooks, where the small capacity of an SSD is often a deal breaker since these mobile computers usually can house only one drive.

A dedicated file server allows every user in a home - whether they're at home or on the road - to access every file they might need, regardless of which particular device they might be using at any given time.  Dedicated file servers also allow you to share your files with friends and coworkers - simply provide them with a URL, a login name and password, and specify what content they can access.  For example, maybe you'd like to share your kids' camp photos with the in-laws - but your cloud storage capacity won't fit all of those photos plus all of the other stuff you have stored in your cloud drive locker.  Maybe you'd like to share sensitive information with a colleague that you'd rather not upload to a server owned by Amazon or some other third party, but the files are too big to email.  Or maybe you'd simply like to access your 200GB library of MP3s while you're holed up in a hotel on business with nothing but your 60GB SSD-based netbook.  These few examples are really only the tip of the iceberg when it comes to the utility of a file server. 

That said, there are alternatives to a file server for all of these needs.  You could dump all of your photos onto a flash drive and give them to the in-laws the next time you see them - but you have to do this every time you want to share more photos - and who knows if you'll get your flash drives back?  You could mail a DVD-R to your colleague - but perhaps a DVD-R's ~4GB capacity is insufficient, and snail mail takes days if not weeks to be delivered.  If you're on the road, you could just bring along your portable external hard drive - which takes up space, and can be lost or stolen.  A file server is a simple, singular solution to all of these problems.  Home file servers do not require enterprise-grade hardware and can be very affordable.  They can also be made from power-sipping components that won't spike your electrical bill.

What considerations are important in building a file server?

Because the primary role of a file server is storage, this is the most important aspect to think about.  How much storage space do you need?  Do you want to share 50GB of photos taken on a point and shoot digital camera?  500GB of music?  2TB of movie DVD ISOs?  30TB of mixed media and work-related files?  Also, at what rate are your storage demands growing, and how easily do you want to be able to expand your file server?

How easily do you want to be able to administer your files?  Many of the more powerful file server operating systems are unfortunately not particularly easy to run for the non-IT professional.  However, there are file server OS's that are easy to run.  What about being able to recover your files in the event of catastrophe?  Placing your files in one computer is tantamount to putting all of your eggs in one basket, which can be risky.  What about security?  Anything on any sort of network is vulnerable to intrusion.  While this guide answers all of these questions, it is aimed at home users and therefore necessarily makes some sacrifices to storage space, administration capabilities, recoverability, and security - simply because home users typically can neither afford nor require professional-grade file server solutions.

Why build a file server instead of using NAS?

Simply put, a NAS (networked attached storage) device is a computer appliance.  It is built specifically to provide network-accessible storage.  NAS devices typically offer easier administration than file servers (some are a few mouse clicks away from plug and play operability), but are often limited by proprietary software, and are neither as capacious nor as expandable as a dedicated file server.  Further, higher-end NAS devices that can house as many hard drives as some of the builds outlined in this guide are more expensive than the file server alternative.  Finally, because they are designed with only one purpose in mind, they are not as flexible as a file server, which in a multi-system home, might need to be co-opted into a basic workstation at a later point in time.  That said, while NAS devices are outside the scope of this guide, they're worth investigating if you're not already familiar with them. 

This guide is laid out differently than my previous builder's guides in that rather than detailing specific systems at specific price points capable of performing specific tasks, it instead discusses options for operating systems and types of components and how these different options are best suited to addressing different needs.  That is, maybe you need a lot of storage space but you're not particularly concerned about backups.  Or perhaps you don't need much storage space at all but want to use a very straightforward file server operating system.  By mixing and matching recommendations to suit your needs, hopefully you'll be able to construct a file server with which you'll be pleased!

File Server Operating Systems
Comments Locked


View All Comments

  • Emantir - Sunday, September 4, 2011 - link

    Im using my file server since october'10 it consists of:
    - Lian Li PC-Q08
    - Zotac NM10 DTX Wifi
    - 200GB Matrox Sata HDD (System)
    - 4x 2TB Western Digital WD20EARS (Storage)
    - Asus EN210 Silent
    Sporting Ubuntu 10.10 with Software Raid 5 and XBmC for HD Playback, works like a charm.
    XBmC Remote Apps exist for iOS and Android so i skipped buying a MCE Remote.
  • Emantir - Sunday, September 4, 2011 - link

    Uh, forgot the Problems:
    - Asus EN210 blocks one Sata Port
    - There are some problems concerning the JMicron Sata Multiplier and Linux. one drive gets miserable write speeds, thus making the whole raid 5 somewhat slow. More: http://goo.gl/cM0gg
  • Lonyo - Sunday, September 4, 2011 - link

    Does the NM10 support staggered spin-up of hard drives?
  • Emantir - Sunday, September 4, 2011 - link

    AFAIK No, Im using a 300W PSU anyway, thus high initial current isn't a Problem.
  • pvdw - Monday, September 5, 2011 - link

    But you should have a good quality PSU to give nice clean, reliable current. Loads of PSUs are just rubbish.
  • Lonyo - Sunday, September 4, 2011 - link

    You may have mentioned needing a good power supply, but when you talk about Atom and Zacate boards, low power solutions, and low power "green" drives, you don't focus on the fact that total system power use in typical conditions could be lower than 30w. If you are buying a beefy 500w power supply, you could be wasting a LOT of power due to efficiency issues.

    The 80PLUS rating only tests as low as 20% of full load. 30w on a 500w PSU is below 10% load, so you could be getting 70% efficiency.
    While it's not a major concern, if you are looking to make things low power to leave it on 24/7, you might want to think about some DC power supplies rather than regular desktop power supplies.
    If you are making a 2~4 drive file server based on an Atom system, you could get a 100~120w picoPSU instead of a "real" PSU, and get potentially much higher efficiency than with a 300w+ normal PSU.

    Of course, not everyone (especially Americans) cares about efficiency, since for them power is so inexpensive, but for a 24/7 box, why not at least discuss things which might improve power efficiency?
  • jtag - Sunday, September 4, 2011 - link

    I have to say that a file server guide that mentions RAID/NAS really should include a discussion on which drives are suitable for using in a RAID. Not all drives are valid for use in a RAID, not because of reliability concerns, but rather because not all manufacturers support Error Recovery Control (see http://www.csc.liv.ac.uk/~greg/projects/erc/ for more info) in their consumer level drives.

    I'd very much appreciate it if AnandTech could run the following command on every drive they test and add it to bench, so we could come up with a list of drives that do support ERC:

    smartctl -l scterc /dev/sdX

    smartctl is available for both Windows and Linux (smartmontools.)

    Of course, this may say it is supported, but the real test would be to set timeouts:

    smartctl -l scterc,70,70 /dev/sdX

    And then cause the drive to have a block error and see if access times out, or causes the drive to drop out of the RAID. This would also be a good test of RAID controller cards, though personally I always use software RAID under Linux.
  • jtag - Sunday, September 4, 2011 - link

    And for the record - I run 6 2TB drives in a RAID-6 (2 drive redundancy) with one hot spare under Gentoo Linux software RAID. My drives are 5 Seagate ST32000542AS and one Samsung EcoGreen F4 HD204UI
  • jwilliams4200 - Sunday, September 4, 2011 - link

    Any tips on how to "cause the drive to have a block error"?
  • Rick83 - Monday, September 5, 2011 - link

    you can use hdparm to mark a block as faulty, IIRC.

Log in

Don't have an account? Sign up now