Selfhosted

38831 readers

101 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

What is TrueNAS writing all the time to disk? (mander.xyz)

submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]

8 comments fedilink hide all child comments

I have a TrueNAS install with SMB turned on and nothing else. Even when it’s idle and nothing is accessing it, there’s constant disk activity. Very low bandwidth, but it’s like some log is in verbose mode.

TrueNAS is installed in a NVMe disk with plenty of room, and there’s only one pool. I’ve checked my snapshot configuration, nothing enabled faster than daily.

What could be causing it? How do I stop it or redirect it to the NVMe drive? I’m willing to create a partition on the NVMe drive if that’s what will do it.

Edit: thanks everyone for all the feedback, I’ll try these out and report back.

top 8 comments

sorted by: hot top controversial new old

[–] [email protected] 15 points 3 months ago (1 children)

That's most likely the syslog. Check the settings, you can choose the volume to use for it.

[–] [email protected] -1 points 3 months ago

Or set up a ramdisk, or turn off log to disk entirely somehow. But if you do that, you'll lose logs between reboots or crashes, making troubleshooting harder.

[–] [email protected] 5 points 3 months ago

Every 4-5 seconds? Yeah, logging.

You can either move the system dataset to your boot drive/pool or syslog to /var/log:

https://www.truenas.com/docs/core/coretutorials/systemconfiguration/settingthesystemdataset/

I've seem many users recommend a reboot after changing those settings.

[–] [email protected] 5 points 3 months ago

Have you run lsof? See also: https://www.brendangregg.com/linuxperf.html

[–] [email protected] 4 points 3 months ago

Dirty secrets about you.

[–] [email protected] 4 points 3 months ago (1 children)

If it’s logs, there’s a package called log2ram - it’s designed for small form factor systems to reduce writes to SD cards but does apply anywhere you want to log but not hit disk immediately. It syncs logs to disk on a regular basis so you don’t lose much if the system crashes.

[–] [email protected] 2 points 3 months ago

Ooh that sounds promising, thank you!

[–] [email protected] 3 points 3 months ago

Probably these directories...

/tmp /var/tmp /var/log

Two are easy to migrate to tmpfs if you are trying to reduce disk writes. Logs can be a little tricky because of the permissions. It is worth getting it right if you are concerned about all those little writes on an SSD. Especially if you have plenty of memory.

This is filesystem agnostic btw so the procedure can apply to other filesystems on Linux operating systems.