I got volumes in error when having write problems. Once it was full FS, once the mounted FS becomes RO, once the mount itself was broken, permissions also could be a problem. But every time it was problem to write the volume. Be sure that the server is OK and you can write with user bareos.
I found that most easy way to fix volumes in "error" state is to remove them, bareos will create new good one. On Monday, January 10, 2022 at 5:54:17 PM UTC+2 [email protected] wrote: > Hi, > > I backup multiple servers to my bareos server, these are all type=File > based backups. > This has run fine for multiple months, but now I have lots of errors: > > If I go to storages -> volumes, all my volumes have a status 'error'. > The volumes are not full (maximum bytes is 10.74GB, current bytes varies > from 1.51KB, to a couple of GB's). > All my backup jobs remain 'queued'. > > How do I start to fix this? Is there an easy way to clear/delete all > volumes and start over without deleting all my defined jobs/etc... > > I have restarted postgres, bareos-fd, bareos-sd, and bareos-dir a week > ago, and it ran OK for a day of two afterwards, but now the same problem > occurs. > > best regards, > Andy > -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/3f9a8e8e-f3f5-4010-ad41-aef7ae5168b2n%40googlegroups.com.
