To fix a volume, you could use the "update volume" command in bconsole and change the Volume Status to Full. That should allow the volume to be recycled as normal.
BTW, the default config writes logs into a file called "bacula.log" in the Director's working directory and also into the catalog. __Martin >>>>> On Wed, 8 Jun 2022 12:50:56 -0400, Ken Mandelberg said: > > It doesn't look like have logs covering that period. At any rate my > concern is just recovering the volumes like Vol0005. > > I ran bls on it, and it seems to show the file is fine. How do I get it > back into the catalog? > > > > Martin Simmons wrote on 6/8/22 05:46: > >>>>>> On Tue, 7 Jun 2022 19:09:38 -0400, Ken Mandelberg said: > >> I run bacula with file volumes not tapes. Recently several volumes may > >> have gotten corrupted. Here are 3 examples > >> > >> Vol0001 Read-Only File 2022-06-01 2:22:42 34.0GB > >> Vol0004 Full File 2022-05-26 2:11:09 53.6GB > >> Vol0005 Read-Only File 2022-04-03 2:41:19 1B > >> > >> Vol 4 is seemingly ok, but vol 1 and 5 got changed to Read-Only and 5 > >> shows no 1B, although it size on the filesystem is 50GB. There are > >> several like Vol 5. Are they lost for good or is there some way to > >> resurrect them? > > Bacula sets the Read-Only status in the catalog if gets EACCES or EROFS from > > the OS when trying to open the volume for writing. I suggest looking in the > > Bacula log for messages like: > > > > Marking Volume "Vol0005" Read-Only in Catalog. > > > > Then look for other logs from around that time to see why it might have done > > that. > > > > __Martin > > _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
