大网数据广告活动
服务器运维问答

Small LAN Linux fileserver and network design

· 52CE 我爱测

We have a small LAN with a couple dozen desktop client PC's and one fileserver. Our goal is to enable the client PC's to have all storage on the fileserver and for file I/O operations to feel as if the storage is still local. Mos…

问题原文

原帖链接 · MountainX · CC BY-SA 3.0

We have a small LAN with a couple dozen desktop client PC's and one fileserver. Our goal is to enable the client PC's to have all storage on the fileserver and for file I/O operations to feel as if the storage is still local.

Most file operations involve opening / saving files of less than 6 MB. Typical files are spreadsheets (1.6 MB on average), images (png jpeg 5.5 MB on avg), audio (mp3, 5 MB avg) and small plain text files.

However, one of our workers is doing audio and video editing where the audio files are 200 MB on average and the video files can be a few GB.

Our goal is to have all files stored on the fileserver where they can be properly backed up, etc.

Here is our equipment:

  • Switch: HP Procurve 1820-48G J9981A
  • Fileserver: Dual GbE LAN ports via Intel® i210 (Motherboard: SUPERMICRO MBD-X10DAL-I-O ATX Server Motherboard / Intel C612)
  • LAN: CAT 5E cabling for shorter runs; CAT 6 shielded for longer runs
  • Clients: Linux desktops with Gigabit NICs. All systems run either Arch Linux or Kubuntu LTS (14.04 and 16.04 currently).
  • Protocol: NFS v4

We can load the fileserver up with as much RAM or processing power or other components as required (within reason) to achieve our goal. We don't know where the performance bottleneck will be however. (We do not know how to approach this problem correctly as we have little to no networking experience.)

One idea that came up was to do NIC teaming on the fileserver similar to this:

Another idea was to use both fileserver NICs separately and connect the client PC that works with large media files to one address and everyone else to the other address.

Bottom line: We need advice regarding server requirements as well as network design. Please point us in the right direction! Thanks

已采纳解答

原帖链接 · Craig Watson · CC BY-SA 3.0

My personal recommendation would be to use NIC teaming, for a number of reasons. NIC teaming/boding will allow for link redundancy and/or load balancing, depending on which options you select and your hardware/OS choices.

If you opt for a load-balanced configuration, traffic will be split across both links, effectively giving you a single, logical 2Gbps "pipe" - I say "effectively" because there are several options to choose from - for example, source/destination stickiness, round-robin, active/passive, etc.

Your clients will also have a single endpoint to communicate to, which will greatly simplify your deployment.

As far as server requirements, this is beyond ServerFault's remit as we only accept questions that have a quantifiable answer, but your bottleneck will almost certainly be network bandwidth, with a secondary bottleneck of disk I/O.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-07-04)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。