Unsolved

This post is more than 5 years old

1 Rookie

 • 

48 Posts

1233

July 9th, 2007 01:00

WARNING fixed volume filemark not in sync with tape volume

Hi

I got this error several times in Networker error log this night
Is it severe? How should I fix it?

07/09/07 00:15:53 nsrmmd #1: WARNING fixed volume filemark not in sync with tape volume:PDN135L3 next:57 VWFN:56 ssid:1771135274

2 Intern

 • 

244 Posts

July 9th, 2007 02:00

Hi Trekk,

Did you have a problem with mediadb ? Ie. have you recover NW from boostrap or have you noticed something like this in daemon.log:
nsrmmdbd: WISS error: Unable to mount /nsr/mm/mmvolume6: database was not shutdown cleanly
or
nsrmmdbd: XCHK ssid:1196216828 host:host_name name:/save/set/name has a fragment with an
invalid volid:1900742733
?

1 Rookie

 • 

48 Posts

July 9th, 2007 05:00

No problem with mediadb

Did not recover NW from bootstrap and nothing like this in daemon.log :(

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

July 16th, 2007 11:00

Well, it says warning so it should not be severe by definition, however it doesn't indicate anything pleasant either. It looks as file records on tape are not in sync with what mdb has (you can fix that with scanner in case of severe trouble). There used to be an issue with that in initial 7.2 version - what NW version do you run?

1 Rookie

 • 

100 Posts

June 1st, 2009 04:00

Hi

I have a problem with mediadb. I recovered mediadb from bootstrap like you said and there is a lots of "WARNING fixed volume filemark not in sync with tape volume" messages in daemon log. Is it a big problem ? and What can ı do ?

455 Posts

June 1st, 2009 05:00

Sounds like your index may be currupted, in which case you may have to run NSRCK -L 6

Check the doc for NSRCK. for more options.

2 Intern

 • 

1.1K Posts

June 2nd, 2009 06:00

There is no evidence for index corruption here; possibly media database issue but it may be an issue with your hardware. It may be a problem as your tapes may not be readable without scanning them in which is a laborious process.
I'd suggest - run nsrim -m to check the media database, use a cleaning cartridge in drives you have seen the problem, check the logs to see if it is a specific tape where the problem is seen and if so remove it from the system. Run a testbackup and see if you can reproduce the problem.
No Events found!

Top