1849079 Members
8436 Online
104041 Solutions
New Discussion

Re: ignite tape failure?

 
SOLVED
Go to solution
Todd McDaniel_1
Honored Contributor

ignite tape failure?

Guys,

My make_tape_recovery appears to complete successfully but fails on the rewind at the end...

Does that mean my backup failed? See below...

================================================
$ tail -20 recovery.log
local -n 2008-07-25,06:00 -m t -w
/var/opt/ignite/recovery/2008-07-25,06:00/recovery.log -u -R -g
/var/opt/ignite/recovery/2008-07-25,06:00/flist -a 3296610

* Preparing to create a system archive.

* Archiving contents of cfsapps via tar image to local device/dev/rmt/3mn.
pax: /dev/rmt/3mn : Device busy
WARNING: The pax command returned a non-zero exit status (exit status 1).
WARNING: The pax command returned a non-zero exit status (exit status 1).
* Creation of system archive complete.

* Archive created and rewind the tape to beginning of tape.

ERROR: Failed to open tape device /dev/rmt/3mn:Device busy (errno = 16).
ERROR: The rewind command failed.


======= 07/25/08 06:04:20 CDT make_tape_recovery completed unsuccessfully
===============================================
Unix, the other white meat.
12 REPLIES 12
James R. Ferguson
Acclaimed Contributor

Re: ignite tape failure?

Hi Todd:

I would definitely not consider this a success:

pax: /dev/rmt/3mn : Device busy
ERROR: Failed to open tape device /dev/rmt/3mn:Device busy (errno = 16).
ERROR: The rewind command failed.
make_tape_recovery completed unsuccessfully

Your tape drive may need to be cleaned. Your tape may be bad too. I would test your drive with a simple 'tar' and 'mt rew'.

Regards!

...JRF...
Tim Nelson
Honored Contributor

Re: ignite tape failure?

My first guess would be a bad/faulty tape drive.

Test the daylights out of it then replace or correct the error.

Would have expected an IO error vs device busy though, but you never know.

TwoProc
Honored Contributor

Re: ignite tape failure?

Is it maybe because you're using the no rewind device?

/dev/rmt/3mn is a no rewind device, try the process again using /dev/rmt/3m and let us know what happened.
We are the people our parents warned us about --Jimmy Buffett
Todd McDaniel_1
Honored Contributor

Re: ignite tape failure?

I am having the drive cleaned and I took out the rewind at the end.

I will run another job today and see what it does this time.

thanks all for your help.
Unix, the other white meat.
James R. Ferguson
Acclaimed Contributor

Re: ignite tape failure?

Hi (again) Todd:

A no-rewind device is what an Ignite 'make_tape_recovery' needs.

Regards!

...JRF...
Todd McDaniel_1
Honored Contributor

Re: ignite tape failure?

oh yes, but for some reason they had it using Xmn, but also with a rew option, very odd.

Now, I am using 3mn (no 0mn device)and no option to rewind.
Unix, the other white meat.
TwoProc
Honored Contributor

Re: ignite tape failure?

JRF - OK, but wouldn't a rewind command on a no rewind interface always fail? I'm just asking...
We are the people our parents warned us about --Jimmy Buffett
Steven E. Protter
Exalted Contributor
Solution

Re: ignite tape failure?

Shalom,

Clean the drive, use new media and leave the rewind settings the way they were in your backup script.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
OldSchool
Honored Contributor

Re: ignite tape failure?

" OK, but wouldn't a rewind command on a no rewind interface always fail? I'm just asking..."

nope...means that the device doesn't *automatically* rewind

you can test this with the "mt" command...

tar something to /dev/rmt/Xmn (for whatever device you have).

then issue: "mt -f /dev/rmt/Xmn rew"
Todd McDaniel_1
Honored Contributor

Re: ignite tape failure?

okay the clean tape did its job...

Now it only had one warning I need to check into.


============================================
WARNING: list_expander returned a warning; please check the recovery.log file
for details.
* Creating Archive Configuration

* /opt/ignite/lbin/make_arch_config -c
/var/opt/ignite/recovery/2008-08-13,12:10/archive_cfg -g
/var/opt/ignite/recovery/2008-08-13,12:10/flist -n 2008-08-13,12:10 -r
pa -b 64 -d Recovery\ Archive -t 1 -i 1 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
* Checking configuration file for Syntax
* Writing boot LIF to tape
48055+0 records in
48055+0 records out
* Complete writing boot LIF onto tape.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/3mn -t n -s
local -n 2008-08-13,12:10 -m t -w
/var/opt/ignite/recovery/2008-08-13,12:10/recovery.log -u -R -g
/var/opt/ignite/recovery/2008-08-13,12:10/flist -a 3548600

* Preparing to create a system archive.

* Archiving contents of cfsapps via tar image to local device/dev/rmt/3mn
.
* Creation of system archive complete.
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the backup:
/var/tmp/ign_configure/make_sys_image.log

* Archive created and rewind the tape to beginning of tape.

* Cleaning up old configuration file directories


======= 08/13/08 12:51:29 CDT make_tape_recovery completed with warnings

Unix, the other white meat.
James R. Ferguson
Acclaimed Contributor

Re: ignite tape failure?

Hi (again) Todd:

> okay the clean tape did its job...

You will note that that was my *original* suggestion in my *first* post, too.

Regards!

...JRF...
Gokul Chandola
Trusted Contributor

Re: ignite tape failure?

Hi,
If problem is with only rewind, then it mean backup is restored with error.

Regards,
Gokul Chandola
There is always some scope for improvment.