On Saturday 11 March 2006 12:02, Ralf Gross wrote:
> > > > On Mar 10, 2006, at 2:58 AM, Ralf Gross wrote:
> > >>
> > >> I'm confused by this output, because Bang5 was the second tape of 
> > >> three
> > >>
> > > >> tapes that were used for the full backup three weeks ago. I don't
> > > >> know why
> > > >> volbytes/files show these values.
> > > >>
> > > >> Looking at the volume state with llist, reports 1970-01-01 01:00:00
> > > >> as firstwritten date.
> > > >>
> > > >>           mediaid: 5
> > > >>        volumename: Bang5-2006-02-08
> > > >>              slot: 5
> > > >>            poolid: 1
> > > >>         mediatype: AIT-2
> > > >>      firstwritten: 1970-01-01 01:00:00
> > > >>       lastwritten: 2006-02-19 01:41:36
> > > >>         labeldate: 2006-02-18 19:30:03
> > > >>           voljobs: 0
> > > >>          volfiles: 0
> > > >>         volblocks: 0
> > > >>         volmounts: 1
> > > >>          volbytes: 1
> > > >>         volerrors: 0
> > > >>         volwrites: 1,031,691
> > > >>  volcapacitybytes: 0
> > > >>         volstatus: Recycle
> > > >>           recycle: 1
> > > >>      volretention: 777,600
> > > >>    voluseduration: 172,800
> > > >>        maxvoljobs: 0
> > > >>       maxvolfiles: 0
> > > >>       maxvolbytes: 0
> > > >>         inchanger: 1
> > > >>           endfile: 66
> > > >>          endblock: 8,689
> > > >>          volparts: 0
> > > >>         labeltype: 0
> > > >>         storageid: 2
> > > >>
> > > >> There is one other tape used for a second client that reports this 
> > > >> date too. I checked the syslog entries, but couldn't find anything
> > > >> obvious. The
> > > >> time entries between 2006-02-18 and 2006-02-19 are all ok.
> > > >>
> > > >> Any ideas why bacula reports this wrong date?
> >
> > By the way, I don't see any problem here. The definition of the
> > FirstWritten field is when the first data record is written not when the
> > Volume is labelled, so just after labelling a Volume, this is normal. The
> > LastWritten field is correct because it is updated each time the volume
> > is written.
>
> But the first data record was written to that volume on 2006-02-18.
> This volume is part of a set of three tapes (Bang4/5/6) that were used
> for a full backup that started on 2006-02-18 19:30. The firstwritten
> date of the volumes Bang4/6 are ok, they indicate the time when the
> first data was written to that tapes. For volume Bang4 it's the time
> the full backup startet, and for Bang6 it's the time when volume Bang5
> filled up and a volume was needed. bacula report this date
> (1970-01-01) only for volume Bang5 and one other volume.

Evidently the volume was recycled and so the FirstWrite date was reset.  If 
that is not the case, then the only thing I could imagine is that either your 
catalog is broken, which does not seem to be the case, or some program other 
than Bacula (i.e. a user?) modified something ...

>
> Ralf
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live
> webcast and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to