On Monday, 24 August 2015 15:50:56 UTC+1, Jörg Steffens  wrote:
> Am 18.08.2015 um 13:11 schrieb Nick Fisk:
> > On Monday, 17 August 2015 15:15:14 UTC+1, Marco van Wieringen  wrote:
> >> Nick Fisk <friskyfisk10 <at> googlemail.com> writes:
> >>> I can see that only the redhat based packages seem to have the RADOS
> >>> backend available. Is there any particular reason for this?
> >> Yes most distributions don't have native CEPH support themself and
> >> we don't want to be fully depended on external repos while building
> >> in the OpenBuildService (OBS) which we use for compiling most platforms.
> > 
> > When you mean native, do you mean in the disto's own repositories? Ubuntu 
> > has had it for a while now
> > http://packages.ubuntu.com/search?keywords=ceph
> 
> Thank you for the hint. I added this as a feature request
> https://bugs.bareos.org/view.php?id=507 and we will include this as
> times permits.
> 
> > Ok great, I will look into building from source then.
> 
> Did this work well?

The basic rados part was very simple. I made sure I had the librados-dev 
library installed and then did a "apt-get source". After rebuilding I copied 
the rados backend library into /usr/libs/bareos/backends and it just worked!!

However as it stores one volume per object performance was quite poor as that 
object only lives on 1 OSD. So I upgraded to 15.2 and tried to also compile the 
radosstriper support, I haven't managed to get this working so far.

The 1st thing I found was that I needed to add "-lrados" to the end of  
RADOS_STRIPER_LIBS, otherwise the test code in the configure script failed to 
link.

This got me as far as building the bareos library, however when trying to use 
it the SD bombed out on startup when it tries to initialise the rados device. 
I'm not sure if this is something related to the Ubuntu radosstriper library or 
something more generic, but here is the output I got:

bareos-sd (90): stored_conf.c:831-0 Inserting Director res: MS-TAPE1-mon
bareos-sd (90): stored_conf.c:831-0 Inserting Device res: Rados
bareos-sd (90): stored_conf.c:831-0 Inserting Device res: LTO6-1
MS-TAPE1-sd (8): crypto_cache.c:55-0 Could not open crypto cache file. 
/var/lib/bareos/bareos-sd.9103.cryptoc ERR=No such file or directory
MS-TAPE1-sd (10): socket_server.c:112-0 stored: listening on port 9103
MS-TAPE1-sd (90): stored.c:642-0 calling init_dev /mnt/backups
MS-TAPE1-sd (10): stored.c:644-0 SD init done /mnt/backups
MS-TAPE1-sd (90): stored.c:642-0 calling init_dev Rados Device
LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate 
registration of tracepoint probes having the same name is not allowed.
BAREOS interrupted by signal 6: IOT trap
Kaboom! bareos-sd, MS-TAPE1-sd got signal 6 - IOT trap. Attempting traceback.
Kaboom! exepath=/usr/sbin/
Calling: /usr/sbin/btraceback /usr/sbin/bareos-sd 2652 /var/lib/bareos
It looks like the traceback worked...
Dumping: /var/lib/bareos/MS-TAPE1-sd.2652.bactrace
MS-TAPE1-sd: smartall.c:414-0 Orphaned buffer: MS-TAPE1-sd 3352 bytes at 
1abf8f8 from jcr.c:404
MS-TAPE1-sd: smartall.c:414-0 Orphaned buffer: MS-TAPE1-sd 536 bytes at 1ade0c8 
from jcr.c:406
MS-TAPE1-sd: smartall.c:414-0 Orphaned buffer: MS-TAPE1-sd 24 bytes at 
7fd42c001538 from jcr.c:391
MS-TAPE1-sd: smartall.c:414-0 Orphaned buffer: MS-TAPE1-sd 280 bytes at 
7fd42c001588 from jcr.c:408
MS-TAPE1-sd: smartall.c:414-0 Orphaned buffer: MS-TAPE1-sd 280 bytes at 
7fd42c0021f8 from lib/mem_pool.h:90


> 
> regards,
> Jörg
> -- 
>  Jörg Steffens                   [email protected]
>  Bareos GmbH & Co. KG            Phone: +49 221 630693-91
>  http://www.bareos.com           Fax:   +49 221 630693-10
> 
>  Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
>  Komplementär: Bareos Verwaltungs-GmbH
>  Geschäftsführer:
>  S. Dühr, M. Außendorf, Jörg Steffens, P. Storz, M. v. Wieringen

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to