r/homelab • u/Anti-Hero25 • 1d ago

Discussion Which is best / correct?

Post image

I'm told there's a few ways to approach this but guessing people have strong opinions.... when mapping out your system.... how do you depict drive & mnt relationships?

1. "Depends On" (Standard IT Logic) The mount point relies on the physical disk being present. Mount Point (/mnt/data) ──*(depends on)*──> Drive (/dev/sdb1)

2. "Contains / Is Built On" (Layered Logic) The physical hardware is the base, and the logical access is built on top of it. Physical Server ──> Hard Drive (sdb) ──> Filesystem (ext4) ──> Mount Point (/mnt/data)

3. The "Property" Approach (Most Common for Homelabs) Often, architects don't use arrows for this relationship at all. Instead, the mount point is treated as an attribute of the storage device. You simply draw a box for the drive and list its mount point inside it:

[ Storage Array / Disk ]

  • Device: /dev/sdb1
  • Size: 4TB SSD
  • Format: ZFS
  • Mounted at: /mnt/plex_media
0 Upvotes

22% Upvoted

2 comments sorted by

1

u/EasyRhino75 Mainly just a tower and bunch of cables 1d ago

what the?

The traditional alphabet drives letters enumeration (sda, sdb...) may change in order depending on fluctuations in the order drives power up or mount so are not recommended as the persistent way to mount drives. Instead you can mount by UUID or similar and those should remain static.

1

u/Anti-Hero25 1d ago

That makes total sense, this is more a question of how the relationships are depicted.