Selfhosted

40183 readers

803 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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

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

submitted 6 months ago* (last edited 6 months ago) by acockworkorange@mander.xyz to c/selfhosted@lemmy.world

9 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.

you are viewing a single comment's thread
view the rest of the comments

[–] JASN_DE@lemmy.world 15 points 6 months ago (1 children)

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

[–] catloaf@lemm.ee -1 points 6 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.