Am 22.05.20 um 17:24 schrieb Christian Lehmann: > Hi Pierre, Hi, please answer to list, not to me.
> so you think it might be an issue of this specific tape? That is not the > case as I tested different tapes and it happened anyway. See my last > response, I attached also some config-files as well as output of the > successful btape test. > I am also not sure how to simply test a tape with bscan. I tested a corrupt tape in the past by this command: bscan -c bacula-sd.conf -v -d 99 -dt -S -r -h localhost -t 5432 -P secreddbpassword -V medianame /dev/nst0 2>&1 |gzip >|bscan.log.gz This will produce a very large logfile which here is inline compressed to the filesystem as a gz-file. You can follow it with zless bscan.log.gz in another terminal session. If you will also synchronize the database you can add -m -s in the list of options, but I think it's not needed so you should check first errors at the end of the tape without using this options. Another useful information maybe can be found if you check your drive for errors with some useful tools, like tapeinfo or, what I know for some weeks, smartctl which is also possible to check for errors on tape drives (but both tools use not nst0 file node, they use sg-devnode so you must find the related one. (e.g. /dev/sg0) tapeinfo is helpful by try each of them. Use both tools with loaded tapes. Maybe comparing at the start and the end is helpful to find issues. I hope my information is correct, it's some days ago where I found a corrupt tape and so I must not use the tools after that time. Cheers, Pierre _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
