I have been running /tmp to tmpfs for sometime now to decrease writes but memory is a problem and it blocks upgrades. My thought was to send /tmp to NFS share but after trying it would seem /tmp won’t go straight to NFS share and then I have started thinking about doing to a file partition on NFS share.
Yes I did. Don’t. It creates more problems than to stay local. Don’t make yourself dependent on yet another box. BOTH have to work for your Smart Home to work.
Btw. your post makes us victims to the XY problem. So why do you want to do this ?
Generally, both boxes are very stable, and I did know that would make it more dependant. Overall RAM is an issue and I am not wanting to drop in a Pi4 yet. I have spare SSD and I have ordered a SATA to USB adaptor now. As such I will copy the SD card to SSD and roll out the now swap and tmpfs and leave it back to normal disk. That way the ware levels won’t be an issue.
Thanks for everyone’s input but seems Pi on a busy system SSD only way to go.
No, and to be frank you still have not answered what the problem is you’re trying to solve.
Is it SD wearout ? Or is it lack of RAM ? Or still something else ?
What HW do we talk about and what applications to use that much ? 1G is enough unless you’re doing anything extraordinary.
When I first installed openhabian V2.2 there were recommendations to put /tmp on tmpfs and yes I know that is RAM to easy writes on the SD Card. However I starting to run low on RAM and due to the SD Card write cycles I though there was little else but to go back to SD Card or NFS.
So apart from explaining based on recommendation to move to tmpfs I thought my first post was clear about what I wanted to move and why.
Now if your saying that post to move to TMPFS is wrong and that SD Card writes are not longer an issue then I can reverse those changes out.
No problem, I have read my original post multiple times and in my head I thought I explained in enough detail but obviously not.
To further expand the issue with /tmp of tmpfs is that updates download to /tmp. On a 1GB RAM system there is just not enough room so updates fail.
In terms of the writes yes ZRAM is a significant change however I am not in the know enough to say if it was there when I deployed. Looking at the post date I would suggest not.
So Markus is it now that ZRAM can be used there is no more ware issues?
There were no separate recommendations I know of. Btw you confuse openHABian with openHAB. There’s no such thing as openHABian 2.2. And if you meant to say “by the time openHAB 2.2 was current” then that’s 2+ yrs old so no matter what it was I would no longer consider that a valid statement.
OS updates do not download to /tmp. There’s almost nothing in openHABian that would cause downloads (unless you sit in front of the Pi console which you shouldn’t be doing) so I can’t follow you there. Those few occasions that do are far away from filling standard /tmp which is 100MB.
Yes, read the link. I’m just about to make it the default for new installations.
Yeah but even Java (the probably largest among downloads) isn’t THAT huge. Your problem probably was you were using /tmp for other stuff not to belong there (logs, presumably).