[Bacula-users] Director will not connect to a remote client

[maaf4d]

Oh, finally! We're getting somewhere. So, after I took out the addresses lines, 
everything is working fine. Next step for me is to get things working on 
CloudLab. Thank you all for your help. I think I can figure out the OpenStack 
issue on my own from here.

Thank you guys so much!

-Marty

+--
|This was sent by maa...@mst.edu via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--



--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Recycling process

[Santiago Díaz Soler]

El 14/03/16 a las 21:16, Santiago Díaz Soler escribió:
>
>
> El 14/03/16 a las 20:43, John Drescher escribió:
>>> Although not your problem (since DRC202L5 was written yesterday), I
>>> see that you have a 7 day retention period on these volumes. Not the
>>> 60 that is in your config.
>>
>> Remember that when you change retention periods in the config files
>> this applies to new volumes only. To get it to apply to existing
>> volumes you need to execute the following 2 commands in bconsole
>> (answering the prompts for each command):
>>
>> update pool from resource
>>
>> update all volumes in pool
>>
>> John
>
> John, thanks for the answer.
> I set the retention period manually with the bconsole, sorry for not 
> bringing that up.
> Even if the volume was written yesterday, bacula changes the Inchanger 
> flag and the slot number of the other volume marked as used with the 
> values from the volume that's supposed to be recycled, and that 
> behavior makes the recycle process to crash.
>
> Paste from /etc/bacula/mtx-changer /dev/sg2 listall
>
> S:11:EXXL5
> S:12:F:DRC201L5
> S:13:F:DRC202L5
> S:14:F:XXL5
>
> At first i thought that it was a retention/volume-use period 
> misconfiguration, but then I checked that it was a random issue and I 
> just can't think of anything else.
>
> What do you think?
>
> Thanks for your help.
> Regards
>
I forget to say that when I execute the "update slots" command, the 
director corrects the volume slots and Inchanger flag values but when 
the job starts the mount requests the incorrect slot.

Thanks for everything
Regards

-- 
Santiago Diaz Soler

Área de operaciones
Coordinación de tecnología
Tel.: 4704-4000 interno (3010)

Educ.ar S.E. - https://www.educ.ar
Ministerio de Educación
Av. Comodoro Rivadavia 1151 (CP 1429) - CABA


--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Recycling process

[Santiago Díaz Soler]

El 14/03/16 a las 20:43, John Drescher escribió:
>> Although not your problem (since DRC202L5 was written yesterday), I
>> see that you have a 7 day retention period on these volumes. Not the
>> 60 that is in your config.
>
> Remember that when you change retention periods in the config files
> this applies to new volumes only. To get it to apply to existing
> volumes you need to execute the following 2 commands in bconsole
> (answering the prompts for each command):
>
> update pool from resource
>
> update all volumes in pool
>
> John

John, thanks for the answer.
I set the retention period manually with the bconsole, sorry for not 
bringing that up.
Even if the volume was written yesterday, bacula changes the Inchanger 
flag and the slot number of the other volume marked as used with the 
values from the volume that's supposed to be recycled, and that behavior 
makes the recycle process to crash.

Paste from /etc/bacula/mtx-changer /dev/sg2 listall

S:11:EXXL5
S:12:F:DRC201L5
S:13:F:DRC202L5
S:14:F:XXL5

At first i thought that it was a retention/volume-use period 
misconfiguration, but then I checked that it was a random issue and I 
just can't think of anything else.

What do you think?

Thanks for your help.
Regards

-- 
Santiago Diaz Soler

Área de operaciones
Coordinación de tecnología
Tel.: 4704-4000 interno (3010)

Educ.ar S.E. - https://www.educ.ar
Ministerio de Educación
Av. Comodoro Rivadavia 1151 (CP 1429) - CABA


--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Recycling process

[John Drescher]

> Although not your problem (since DRC202L5 was written yesterday), I
> see that you have a 7 day retention period on these volumes. Not the
> 60 that is in your config.


Remember that when you change retention periods in the config files
this applies to new volumes only. To get it to apply to existing
volumes you need to execute the following 2 commands in bconsole
(answering the prompts for each command):

update pool from resource

update all volumes in pool

John

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Recycling process

[John Drescher]

On Mon, Mar 14, 2016 at 4:53 PM, Santiago Díaz Soler
 wrote:
> Hi, everyone
>
> I'm facing a weird issue on a bacula instance over Debian 8 (jessie).
> I have a pool with two volumes and everytime that a volume is marked as
> "recycle" (14 days) bacula sets  InChanger and Slot values to 0. Also, the
> volume that was marked as Used gets the InChanger and Slot values of the
> soon to be recycled volume.
> This behavior happens randomly, sometimes the recycle process gets no error.
>
> +-++---+-++--+--+-+--+---+---+-+---+
> | MediaId | VolumeName | VolStatus | Enabled | VolBytes   | VolFiles |
> VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten
> |
> +-++---+-++--+--+-+--+---+---+-+---+
> |  93 | DRC201L5   | Used  |   1 | 37,016,275,968 |   45 |
> 604,800 |   1 |   13 | 1 | LTO-5 | 2016-03-01 21:14:56 |
> | 120 | DRC202L5   | Recycle  |   1 | 50,507,347,968 |   56 |
> 604,800 |   1 |0 | 0 | LTO-5 | 2016-03-13 21:08:43 |
> +-++---+-++--+--+-+--+---+---+-+---+
> (Volume DRC201L5 is in slot 12 but when the volume DRC202L5 enters in
> recycle state, it takes the slot 13)
>

Although not your problem (since DRC202L5 was written yesterday), I
see that you have a 7 day retention period on these volumes. Not the
60 that is in your config.

John

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Director will not connect to a remote client

[Richard]

> Date: Monday, March 14, 2016 15:27:47 -0700
> From: maaf4d 
>
> I am using the public IP address of the machines like so:
> 
> Storage { # definition of myself
>   Name = storage-sd
>   SDPort = 9103  # Director's port
>   WorkingDirectory = "/var/lib/bacula"
>   Pid Directory = "/var/run/bacula"
>   Maximum Concurrent Jobs = 20
>   SDAddress = public.ip.address.xx
> }
> 

You should double check that you don't have 127.0.0.1 or localhost
specified anywhere in your configurations. About the only way you are
going to get netstat output like:

tcp 0 0 127.0.1.1:9101  0.0.0.0:*  LISTEN  6591/bacula-dir
tcp 0 0 127.0.1.1:9102  0.0.0.0:*  LISTEN  1886/bacula-fd
tcp 0 0 127.0.1.1:9103  0.0.0.0:*  LISTEN  1865/bacula-sd

is if you are specifying the localhost name or ipnumber.

Also, that "xxAddress" line is optional and, as the documentation
indicates, it should bind to all addresses if nothing is specified.
Try dropping that line.


[by the way, could you please reply with context. it is very hard to
reply to your messages from the mailing list side when they don't
carry any of the thread.]



--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Director will not connect to a remote client

[Wanderlei Huttel]

Hello
You said that is running in a cloud lab.
I suggest you first learn how to configure in a local machine/local network
and after that try in a cloud lab.
There no secret how to configure bacula, but first you need to know how
bacula works.


Atenciosamente

*Wanderlei Hüttel*
http://www.huttel.com.br

2016-03-14 19:27 GMT-03:00 maaf4d :

> I am using the public IP address of the machines like so:
>
> Storage { # definition of myself
>   Name = storage-sd
>   SDPort = 9103  # Director's port
>   WorkingDirectory = "/var/lib/bacula"
>   Pid Directory = "/var/run/bacula"
>   Maximum Concurrent Jobs = 20
>   SDAddress = public.ip.address.xx
> }
>
> +--
> |This was sent by maa...@mst.edu via Backup Central.
> |Forward SPAM to ab...@backupcentral.com.
> +--
>
>
>
>
> --
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Director will not connect to a remote client

[Dimitri Maziuk]

On 03/14/2016 05:27 PM, maaf4d wrote:
> I am using the public IP address of the machines like so:
...
>   SDAddress = public.ip.address.xx
> }

Mine works fine without that line. What does 'ip a' say on the sd
machine, does it actually have 'inet public.ip.address.xx'? Also 'ip
route': is there route to public.ip.net/mask?

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Director will not connect to a remote client

[maaf4d]

I am using the public IP address of the machines like so:

Storage { # definition of myself
  Name = storage-sd
  SDPort = 9103  # Director's port
  WorkingDirectory = "/var/lib/bacula"
  Pid Directory = "/var/run/bacula"
  Maximum Concurrent Jobs = 20
  SDAddress = public.ip.address.xx
}

+--
|This was sent by maa...@mst.edu via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--



--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Director will not connect to a remote client

[maaf4d]

This is actually not OpenStack anymore. I'm running a temporary experiment on a 
few Linux machines I got in the lab

+--
|This was sent by maa...@mst.edu via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--



--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Director will not connect to a remote client

[Richard]

> Date: Monday, March 14, 2016 17:00:51 -0500
> From: Dimitri Maziuk 
>
> On 03/14/2016 04:45 PM, maaf4d wrote:
>> How would I change that? Maybe that is my issue
> 
> Sorry. I played with OpenStack a year or so ago and decided it
> wasn't worth my time. So I've no idea, all I can tell you is 127/8
> is the loopback address as defined in RFC1122 and will not be
> routed outside localhost.

Are you specifying an IPnumber on the "address" directives? E.g.,

   SDAddresses = { ip = {
  addr = 127.0.0.1; port = 9103; }
  }


If so, and you're using "127.0.0.1", then it will only listen in the
internal interface, not the external, which is what your netstat is
showing. I believe that there are options for this for all the
daemons.


from the current documentation:

SDAddress =  This directive is optional, and if it is
specified, it will cause the Storage daemon server (for Director and
File daemon connections) to bind to the specified IP-Address, which
is either a domain name or an IP address specified as a dotted
quadruple. If this directive is not specified, the Storage daemon
will bind to any available address (the default).

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Director will not connect to a remote client

[Dimitri Maziuk]

On 03/14/2016 04:45 PM, maaf4d wrote:
> How would I change that? Maybe that is my issue

Sorry. I played with OpenStack a year or so ago and decided it wasn't
worth my time. So I've no idea, all I can tell you is 127/8 is the
loopback address as defined in RFC1122 and will not be routed outside
localhost.

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Director will not connect to a remote client

[maaf4d]

How would I change that? Maybe that is my issue

+--
|This was sent by maa...@mst.edu via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--



--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Director will not connect to a remote client

[Dimitri Maziuk]

On 03/14/2016 04:30 PM, maaf4d wrote:
> I get the following when I use netstat:
> 
> tcp0  0 127.0.1.1:9101  0.0.0.0:*   LISTEN
>   6591/bacula-dir
> tcp0  0 127.0.1.1:9102  0.0.0.0:*   LISTEN
>   1886/bacula-fd
> tcp0  0 127.0.1.1:9103  0.0.0.0:*   LISTEN
>   1865/bacula-sd
> 
> 
> It seems to me like it's listening to the correct ports yet it still refuses 
> the connection

Are you connecting from(/to) localhost? 'cause that's what 127.0.1.1 is.
If it's not just localhost then this is what you want to see:

tcp   0   0   0.0.0.0:bacula-dir  0.0.0.0:*   LISTEN
tcp   0   0   0.0.0.0:bacula-fd   0.0.0.0:*   LISTEN
tcp   0   0   0.0.0.0:bacula-sd   0.0.0.0:*   LISTEN

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Director will not connect to a remote client

[maaf4d]

I get the following when I use netstat:

tcp0  0 127.0.1.1:9101  0.0.0.0:*   LISTEN  
6591/bacula-dir
tcp0  0 127.0.1.1:9102  0.0.0.0:*   LISTEN  
1886/bacula-fd
tcp0  0 127.0.1.1:9103  0.0.0.0:*   LISTEN  
1865/bacula-sd


It seems to me like it's listening to the correct ports yet it still refuses 
the connection

+--
|This was sent by maa...@mst.edu via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--



--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula Recycling process

[Santiago Díaz Soler]

Hi, everyone

I'm facing a weird issue on a bacula instance over Debian 8 (jessie).
I have a pool with two volumes and everytime that a volume is marked as 
"recycle" (14 days) bacula sets  InChanger and Slot values to 0. Also, 
the volume that was marked as Used gets the InChanger and Slot values of 
the soon to be recycled volume.

This behavior happens randomly, sometimes the recycle process gets no error.

+-++---+-++--+--+-+--+---+---+-+---+
| MediaId | VolumeName | VolStatus | Enabled | VolBytes   | VolFiles 
| VolRetention | Recycle | Slot | InChanger | MediaType | 
LastWritten |

+-++---+-++--+--+-+--+---+---+-+---+
|  93 | DRC201L5   | Used  |   1 | 37,016,275,968 |   45 
|  604,800 |   1 |   13 | 1 | LTO-5 | 2016-03-01 
21:14:56 |
| 120 | DRC202L5   | Recycle  |   1 | 50,507,347,968 | 56 |  
604,800 |   1 |0 | 0 | LTO-5 | 2016-03-13 21:08:43 | 
+-++---+-++--+--+-+--+---+---+-+---+
(Volume DRC201L5 is in slot 12 but when the volume DRC202L5 enters in 
recycle state, it takes the slot 13)


this is my bacula-dir.conf
*
**
**Job {**
**  Name = "Espacio-Sistemas"**
**  Client = ss03.educ.gov.ar-fd**
**  Level = Incremental**
**  JobDefs = "sistemas"**
**  FileSet = "sys"**
**  Pool = sys-diario**
**  Full Backup Pool = sys-mensual**
**  Differential Backup Pool = sys-semanal**
**  Incremental Backup Pool = sys-diario**
**  #RunBeforeJob = "/etc/bacula/make_catalog_backup.pl Catalogo"**
**  Schedule = "SYS-Ciclo-Semanal"**
**  ##RunAfterJob = "/etc/bacula/delete_catalog_backup"**
**  Messages = Standard**
**  Write Bootstrap = "/var/lib/bacula/%c.bsr"**
**}**
**
**
**

**Schedule {**
**  Name = "SYS-Ciclo-Semanal"**
**  Run = Full Pool=sys-mensual 2nd sat at 3:00**
**  Run = Differential Pool=sys-semanal 1st sat at 21:30**
**  Run = Differential Pool=sys-semanal 3rd-5th sat at 21:30**
**  Run = Incremental Pool=sys-diario mon-fri at 21:05**
**  Run = Incremental Pool=sys-diario sun at 21:05**
**}**
**
**
**
**Pool {**
**  Name = sys-semanal**
**  Pool Type = Backup**
**  Recycle = yes # Bacula can automatically 
recycle Volumes**

**  AutoPrune = yes   # Prune expired volumes**
**  Volume Retention = 60 days **
**  Volume Use Duration = 2592000 seconds # En 4 semanas la cinta cambia 
el "status" a "Used".**

**}*




Thanks for everything, let me know if I miss something.


--
Santiago Diaz Soler

Área de operaciones
Coordinación de tecnología
Tel.: 4704-4000 interno (3010)

Educ.ar S.E. - https://www.educ.ar
Ministerio de Educación
Av. Comodoro Rivadavia 1151 (CP 1429) - CABA

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Copy disk to tape is 4x slower than tar

[Alan Brown]

On 13/03/16 21:48, Dan Langille wrote:
>> As well as increasing max file size you need to boost the tape buffer size 
>> from the 64kB default. I use 2MB
> This is a hardware setting?

No, it's a bacula-sd setting

> I tried Minimum block size & Maximum block size on my tape drive, but need to 
> try it again.
>

My settings:

   Spool Directory = /var/bacula/spool/TAPE
   Maximum File Size = 16G
   Maximum Network Buffer Size = 262144
   Maximum block size = 2M
   Maximum Spool Size = 220G
   Maximum Job Spool Size = 32G


Don't touch minimum block size. It's fine as it is.

2MB is the maximum allowable in bacula, however you probably won't see 
much speed improvement past 500kB unless there's compressible data  in 
the train (it's faster, but only a little. I use it because I have tight 
backup windows and a lot of data to deal with)

FWIW Most LTO tape drives have 8MB(IBM) or 16MB(HP) write buffers.




--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Copy disk to tape is 4x slower than tar

[Cejka Rudolf]

Dan Langille wrote (2016/03/13):
> > As well as increasing max file size you need to boost the tape buffer size 
> > from the 64kB default. I use 2MB
> 
> This is a hardware setting?

Hello, it is software settings:

* Increasing max file size is "Maximum File Size". I use 16 GB for
  LTO-5 and for LTO-4 it should be similar. Every file mark means delay
  of several seconds (3-5?), so you can count, how big slow down for
  each file size it is in percents. On the other side, too big file size
  means slower seeks.

* Tape buffer size: It is "Maximum Block Size". It seems that in Linux
  it is a must to increase it. However, in FreeBSD, I have no problems
  with default 65536 bytes, where I have seen speeds over 250 MB/s with
  well compressable datas and without notable system load, so I did not
  increase it yet. For check, how big block you can use, try mt status -v.
  It is smaller of maxio and cpi_maxio. Without kernel patching, you could
  certainly use 131072 bytes. However, maxio could be increased easily
  (MAXPHYS kernel option) and cpi_maxio depends on driver, how well the
  value is obtained. Sometimes it is just a constant, which is known that
  it could be increased. But, I still think that it is not needed so much
  in FreeBSD.

-- 
Rudolf Cejka  http://www.fit.vutbr.cz/~cejkar
Brno University of Technology, Faculty of Information Technology
Bozetechova 2, 612 66  Brno, Czech Republic

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users