Saving Timeshift snapshots to SnapRaid Array Problems? Also, postdrop file size error after SnapRaid cron?

  • I've got my Timeshift snapshots saving to a drive that's in a SnapRaid array. The first cron for SnapRaid after creating a snapshot popped a bunch of errors for "socket" files. Should I be saving the Timeshift snapshots to a different drive? I can use my SSD that I use for docker stuff for that, but I did want the protection from SnapRaid if possible. Is it possible to ignore those errors, or should I just use the SSD? Or some other solution?


    The other error was a postdrop file size too large error. This is the first SnapRaid cron after adding a ton of files so there's a ton of added files. I tried changing the max file size via omv-env, but it's not even displaying the current value for this variable.


    Or is there a way to have SnapRaid not include added files in the cron email and only show deleted or changed files? I actually can't find the email that generated the error, and the SnapRaid log is only a few lines for the socket files. I don't think the email even included all the added files, but I'm not sure how to view the email that generating the "file too large" error so I'm flying blind here. Ideas? Any logs needed?

    Einmal editiert, zuletzt von Superorb () aus folgendem Grund: changed incorrect postfix to postdrop

  • Superorb

    Hat den Titel des Themas von „Saving Timeshift snapshots to SnapRaid Array Problems? Also, postfix file size error after SnapRaid cron?“ zu „Saving Timeshift snapshots to SnapRaid Array Problems? Also, postdrop file size error after SnapRaid cron?“ geändert.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!