Equipment/Lattner: Difference between revisions

From London Hackspace Wiki
m (Added documentation for system lattner - the new file server)
No edit summary
Line 20: Line 20:
* 1U Rackmount server with 4 x 1000GB 3.5" SATA drives and one 2.5" 32GB Boot SSD
* 1U Rackmount server with 4 x 1000GB 3.5" SATA drives and one 2.5" 32GB Boot SSD
* Debian 8
* Debian 8
* Connected to [[Equipment/Cisco1]] via port 37 & 38 in a 2 port LACP channel bond.
* Connected to [[Equipment/Cisco1]] via port 31 & 32 in a 2 port LACP channel bond.
* Runs Samba (workgroup 'LHS') and has 2 shares:
* Runs Samba (workgroup 'LHS') and has 2 shares:
** space, which is read/write to everyone on the local network  
** space, which is read/write to everyone on the local network  

Revision as of 14:56, 5 July 2016

Lattner
Hackspace Unknown.png
Model SuperMicro X7DBU
Sub-category Networking
Status Good working order
Training requirement no
Origin mixed
Location Basement rack
Maintainers Sysadmin team
  • 1U Rackmount server with 4 x 1000GB 3.5" SATA drives and one 2.5" 32GB Boot SSD
  • Debian 8
  • Connected to Equipment/Cisco1 via port 31 & 32 in a 2 port LACP channel bond.
  • Runs Samba (workgroup 'LHS') and has 2 shares:
    • space, which is read/write to everyone on the local network
    • managed which contains useful things that are of interest to hackspace members.
  • shares /home over nfs, currently used by lamarr at least.

Motherboard and Memory

Lattner has 32GB of ECC DRAM and is powered by a SuperMicro X7DBU motherboard. Possible management via IPMI is available via an off-board card that is currently NOT installed.

Disk Configuration

  • 4 1TB drives connected directly to the motherboard SATA ports.
  • System is using ZFS in a RAIDZ2 (Double-Parity) RAID providing 1800GiB of usable storage.
  • zpool was created using device-aware /dev/disk/by-id rather than generic /dev/sda,sdb,sdc,sdd enumeration to help facilitate disk replacements when a drive goes down:
    • HOW? By labeling the outside of the drive-tray with the disk serial number, we can easily reconcile the serial number of a failed/failing drive with one that is in the array.
  • Boot drive is simply a single SSD - it shouldn't hold anything precious nor be used as a caching device as there is sufficient system memory and ZFS can likely manage caching automatically.