Re: Tar block size

Radosław Korzeniewski <[email protected]>
Newsgroups gmane.comp.bacula.user
Message-ID <CAF_EmoCY=9u7GboTFU3Thc9_W9ZqFXBokvuJ9aufyk8Dmj72uA@mail.gmail.com>
Hello,

śr., 28 sie 2024 o 07:47 [email protected] <
[email protected]> napisał(a):

> Dear all,
>  I've been using bacula v. 15.0.2 for a few weeks. I also installed
> Bacularis v. 3.2. My server has a LTO8, this drive works much better if I
> change the block size ("-b 512").
>

There are special parameters to force Bacula tu use required block sizes:
- Minimum block size = <size-in-bytes>
- Maximum block size = <size-in-bytes>
please check documentation:
https://www.bacula.org/15.0.x-manuals/en/main/Storage_Daemon_Configuratio.html#SECTION0025300000000000000000

But I do not understand why setting a block size to 512 bytes would do any
better in this case.


> I would like to modify the bacula-sd.conf file like this:
> Device {
> ...
> ArchiveDevice = "/dev/nst1 -b 512"
>

I'm pretty sure this kind of configuration is not supported and according
to documentation (and my Bacula developer experience) this Archive
Device = <name-string>,
which:
The specified name-string gives the *system file name* of the storage
device managed by this storage daemon. This will usually be the device file
name of a removable storage device (tape drive), for example /dev/nst0 or
/dev/rmt/0mbn.
So, unless you have a device file named "/dev/nst1 -b 512" it simply won't
work.

....
> }
> What do you think?
>

Bacula does not use TAR for saving on the tapes, so your suggestion is
invalid.
I hope this helps.

best regards
-- 
Radosław Korzeniewski
[email protected]

_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.