If that volume was the one in used when the storage space get full, the director may have created the record into the database, while the sd can't do it on the disk. We have already an issue open for that https://github.com/bareos/bareos/issues/1804
You may want to delete the faulty inexistent volume from your catalog, then a new volume should be created. I'll go to close your reported issue as duplicate. On Thursday 5 September 2024 at 12:17:33 UTC+2 Andrea Bonetti wrote: > Hi all, > > After expanding the pool of a job that was stuck for "Cannot find any > appendable volumes" i get the error in the subject. > The volume is(as per the message) not present in the storage server, and > it's not getting created. > Any clues why this is happening? > This is an NDMP job > -- 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/1a9d6adc-6afc-437f-a36e-888921ceb1adn%40googlegroups.com.
