Is it right to mount /var on HDD instead of SSD so it will last longer?

Question

linux

When installing Linux, is it rational to specify a mount point for the /var partition on the HDD (if available), instead of mounting on the SSD in order to not write logs to the SSD and thereby increase its lifespan? Perhaps there are other partitions that should be mounted on the HDD?

Answer 1

No, all of this "SSD life saving" advice applies to the earliest generations of drives. Modern drives will become morally obsolete much earlier than the moment when their write resource is exhausted.

Answer 2

Almost always - this is saving on matches. Except, of course, when you have a really healthy stream of logs - but then they are usually not stored locally, but centrally.

Answer 3

If you care about optimization and don't care about logs, then /tmp and /var/log are perfectly mounted into memory (tmpfs). The downside is that you won't be able to see what was in the logs before the reboot. Plus - the costs will rush to zero (by mounting /var on the HDD, you will noticeably slow down access to it for writing).

Answer 4

• Firstly, it is not clear what the service life has to do with it? What side is he?
  
• Secondly, if you decide to separate partitions across different disks, then the principle is simple - all data that you often work with is on SSDs, which are rarely accessed on HDDs. Since /var is frequently changed data - its out of the question on an SSD.
  

Answer 5

Not anymore

Answer 6

NO, this is no longer relevant
. Trim technology is already on all disks, their wear is no less than that of hard ones, and sometimes even more.
Children's sores ssd already asked

Answer 7

It all depends on the loads
Let's say for a HEAVY DB server
I would do the following
RAID 1 - OS
RAID 10 - database data
RAID 10 - database logs
Application server (all in one)
RAID 1 - OS
RAID 10 - database + logs + data
Application server (web muzzle)
RAID 1 - OS - data
A separate issue is ssd accelerators and nvme cache
Look, all this is present and allows you to keep the budget within reasonable limits.
In the end, a lot of IOPS and random reading is not always necessary.
In general, make a plan for resource consumption, and choose everything according to this plan.