On 25/04/12 11:20, Hugo Letemplier wrote:
> I erased my tapes with an "mt -f /dev/nst0 erase" after having
> stopped bacula-sd and freed all iscsi layers
You should only need to label the tape, not erase it.
--
Live
2012/4/23 John Drescher :
>> When you recycle tapes they get relabelled. At that point the larger block
>> size will be used automatically.
>>
>> It works for me.
>
> Thanks. I will try to test this soon provided I get some time.
>
> John
>
>
> When you recycle tapes they get relabelled. At that point the larger block
> size will be used automatically.
>
> It works for me.
Thanks. I will try to test this soon provided I get some time.
John
--
For Developers,
On 19/04/12 23:11, John Drescher wrote:
> Now I think I remember. If I change the block size all tapes with the
> previous block size will be not writable since they were previously
> written with the smaller block sizes and you can not change fixed
> block sizes on a tape that contains data. So m
>> Bacula defaults to fixed blocks of ~ 64K. This will work with all LTO
>> drives but can be suboptimal in performance. You can change the block
>> settings in bacula-sd.conf however I believe that will make all tapes
>> that were written with the 64K blocks unusable without you manually
>> erasin
On 19/04/12 17:10, John Drescher wrote:
> Bacula defaults to fixed blocks of ~ 64K. This will work with all LTO
> drives but can be suboptimal in performance. You can change the block
> settings in bacula-sd.conf however I believe that will make all tapes
> that were written with the 64K blocks un
> Thanks for the info. Another question: the text on wikipedia states
> "LTO-3 and LTO-4 use a similar format with 1,616,940-byte blocks" - is
> this something I would need to add as a directive (in trying to resolve
> my current issue), or would Bacula set this appropriately when I set
> media typ
> > Could there be any other reason you may think of (possibly outside of
> > bacula) that would cause a drive to think it's written more than it has,
> > or for the job to start at the wrong point on the tape?
>
> LTO media does not work that way. To write from beginning to end it
> does multiple
> Could there be any other reason you may think of (possibly outside of
> bacula) that would cause a drive to think it's written more than it has,
> or for the job to start at the wrong point on the tape?
>
LTO media does not work that way. To write from beginning to end it
does multiple passes of
Hi
On Thu, 2012-04-19 at 09:41 -0400, John Lockard wrote:
> I know this is probably a stupid question, but I've seen stupid
> questions solve things in the past...
Indeed :)
> Are both your tape drive and tape at least LTO3? If your drive is
> LTO-3 and your tape is LTO-2, then your results mak
I know this is probably a stupid question, but I've seen stupid questions
solve things in the past...
Are both your tape drive and tape at least LTO3? If your drive is LTO-3
and your tape is LTO-2, then your results make perfect sense.
-John
On Thu, Apr 19, 2012 at 1:07 AM, Andre Rossouw wrote
I'm hoping someone can point me in the right direction - faulty drive,
incorrect settings, faulty tape (I hope it's something that simple)
I've run the archive job again, and again Bacula has reported the media
as full after just ~200GB. However when I do llist volume=
it reports a different "
Thanks for the replies. I still have 2 questions:
On Wed, 2012-04-18 at 19:37 +0200, ganiuszka wrote:
> 2012/4/18 Andre Rossouw :
> > Hello.
> >
> > I have a system running Ubuntu 10.04 with Bacula 5.0.1. and a SCSI
> > Tandberg LTO-3 HH drive. It has been running without problems since
> > 2010.
Depending on your compression, it looks like your tape could be full.
Last Volume Bytes: 407,329,219,584 (407.3 GB)
On 4/18/2012 12:42 PM, Andre Rossouw wrote:
> Hello.
>
> I have a system running Ubuntu 10.04 with Bacula 5.0.1. and a SCSI
> Tandberg LTO-3 HH drive. It has been running wit
2012/4/18 Andre Rossouw :
> Hello.
>
> I have a system running Ubuntu 10.04 with Bacula 5.0.1. and a SCSI
> Tandberg LTO-3 HH drive. It has been running without problems since
> 2010. Last week it started writing ~200GB data to the media, and
> reporting that the media is full.
>
> 18-Apr 16:13 ubu
On Wed, Apr 18, 2012 at 12:42 PM, Andre Rossouw wrote:
> Hello.
>
> I have a system running Ubuntu 10.04 with Bacula 5.0.1. and a SCSI
> Tandberg LTO-3 HH drive. It has been running without problems since
> 2010. Last week it started writing ~200GB data to the media, and
> reporting that the media
Hello.
I have a system running Ubuntu 10.04 with Bacula 5.0.1. and a SCSI
Tandberg LTO-3 HH drive. It has been running without problems since
2010. Last week it started writing ~200GB data to the media, and
reporting that the media is full.
18-Apr 16:13 ubuntu-dir JobId 237: Bacula ubuntu-dir 5.0
17 matches
Mail list logo
