What I actually did was to select them in Baculum and purged them. Then they were in state “Purged”. Then next time a volume from this pool was needed, Baculum grabbed the first one and used it without problems.
> On 1. Mar 2023, at 19:57, Bill Arlofski via Bacula-users > <bacula-users@lists.sourceforge.net> wrote: > > On 3/1/23 06:50, Justin Case wrote: >> Hello folks, >> today I had the situation that bacula tried to create a new disk file >> volumes and the creation failed (not sure what the reason was, lack of space >> or limit of volume number, but I was able to get it to create new volumes >> again): >> Warning: mount.c:216 Open of File device “storagedev1" (/mnt/storage1) >> Volume "vol-2675" failed: ERR=file_dev.c:189 Could not >> open(/mnt/storage1/vol-2675,OPEN_READ_WRITE,0640): ERR=No such file or >> directory >> Now I have in my catalog a number of disk file volumes in state “Error”. >> There are no corresponding volume files on disk with the names found in the >> catalog. >> Will Bacula recycle those volumes automatically (I supposed it doesn’t)? >> If not, what to do with those error volumes in the catalog? just delete >> them? Or move then to scratch? >> Thanks for your time, >> j/c > > If they are in the catalog but the SD could not create them on disk, they > will be marked in "Error" in the catalog, and you will have to delete them. > > If you set them to append, the SD may try to open them, but they will not > exist, and they will be marked in "Error" status again. > > > Best regards, > Bill > > -- > Bill Arlofski > w...@protonmail.com > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
