Finally answered my own question (update, and set the max bytes
setting). As for how this happened in the first place, I don't know. I
guess we'll see what happens next go 'round -- this was the only tape
that had gotten like this, so maybe it was a mistake I made early on.
Ryan Novosielski wrote:
Having trouble writing to a tape that had been previously written to:
05-Aug 15:35 helios-dir: Recycled current volume "Delta_0001"
05-Aug 15:35 helios-sd: Recycled volume "Delta_0001" on device
"/dev/rmt/0cbn", all previous data lost.
05-Aug 15:35 helios-sd: New volume "Delta_0001" mounted on device
/dev/rmt/0cbn at 05-Aug-2005 15:35.
05-Aug 15:35 helios-sd: User defined maximum volume capacity 425
exceeded on device /dev/rmt/0cbn.
The tape is 12GB, but the first time it was written to, only one block
was written. Bacula now refuses to write any more than that to the
tape (ie. the tape is full after 425 is written). Any idea how this
sort of thing might happen and what to do to correct it? Here is my
pool and storage config:
Pool {
Name = catalyst_DELTA
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 13 days
Accept Any Volume = no
Maximum Volume Jobs = 1
}
Device {
Name = helios_DDS #
Media Type = DDS-4
Archive Device = /dev/rmt/0cbn
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = no;
RemovableMedia = yes;
RandomAccess = no;
}
Thanks.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
