Hi there,

I'm having trouble using bscan to recover the catalog data from a tape
which was purged by accident.

I get the following output:

# bscan -c /etc/bacula/bacula-sd.conf -v -V MJR263L3 -s -m /dev/nst0
bscan: butil.c:282 Using device: "/dev/nst0" for reading.
22-Feb 17:04 bscan JobId 0: Invalid slot=0 defined in catalog for Volume
"MJR263L3" on "Superloader-Drive" (/dev/nst0). Manual load my be
required.
22-Feb 17:04 bscan JobId 0: 3301 Issuing autochanger "loaded? drive 0"
command.
22-Feb 17:04 bscan JobId 0: 3302 Autochanger "loaded? drive 0", result:
nothing loaded.
22-Feb 17:04 bscan JobId 0: Ready to read from volume "MJR263L3" on
device "Superloader-Drive" (/dev/nst0).
bscan: bscan.c:288 Using Database: bacula, User: xxx
bscan: bscan.c:431 Pool record for Taeglich-Autoloader found in DB.
bscan: bscan.c:445 Pool type "Backup" is OK.
bscan: bscan.c:455 Media record for MJR263L3 found in DB.
bscan: bscan.c:473 Media type "LTO-3" is OK.
bscan: bscan.c:483 VOL_LABEL: OK for Volume: MJR263L3
bscan: bscan.c:978 Created Client record for Client: bacula-fd
bscan: bscan.c:1061 Created new JobId=2411 record for original
JobId=1067

But nothing shows up in the database, now the drive is idle, doing
nothing, bscan is in "D" state, no error messages in syslog, nothing.

I sent a device reset, so bscan aborted, but I cannot access the
device... :-( Now, tapeinfo hangs as well.

Tape broken?

Any hints?

Thanks,

Tino.

-- 
"What we nourish flourishes." - "Was wir nähren erblüht."

www.lichtkreis-chemnitz.de
www.tisc.de

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to