Hello,
I'm having an issue with btape, every time that I issue the 'quit' comand, I get an 'btape: smartall.c:404 Orphaned buffer: btape 280 bytes at d2e278 from jcr.c:362' (the d2e278 changes on every execution):
root@bacula2mt:~# btape -v -c /etc/bacula/bacula-sd.conf /dev/nst0
Tape block granularity is 1024 bytes.
btape: butil.c:290 Using device: "/dev/nst0" for writing.
11-Sep 14:04 btape JobId 0: 3301 Issuing autochanger "loaded? drive 0" command.
11-Sep 14:04 btape JobId 0: 3302 Autochanger "loaded? drive 0", result is Slot 1.
btape: btape.c:477 open device "Drive-1" (/dev/nst0): OK
*rewind
btape: btape.c:579 Rewound "Drive-1" (/dev/nst0)
*weof
btape: btape.c:609 Wrote 1 EOF to "Drive-1" (/dev/nst0)
*quit
btape: smartall.c:404 Orphaned buffer: btape 280 bytes at d2e278 from jcr.c:362
root@bacula2mt:~# btape -v -c /etc/bacula/bacula-sd.conf /dev/nst0
Tape block granularity is 1024 bytes.
btape: butil.c:290 Using device: "/dev/nst0" for writing.
11-Sep 14:57 btape JobId 0: 3301 Issuing autochanger "loaded? drive 0" command.
11-Sep 14:57 btape JobId 0: 3302 Autochanger "loaded? drive 0", result is Slot 1.
btape: btape.c:477 open device "Drive-1" (/dev/nst0): OK
*quit
btape: smartall.c:404 Orphaned buffer: btape 280 bytes at 22d4278 from jcr.c:362
It's a Debian Wheezy install with bacula 5.2.6. I first saw this after installing 5.2.6, previously I was running 5.0.3 (built from sources) with no problems at all. All bacula tests and backup jobs finishes without errors.
Any clues? What are those orphaned buffers exactly? Will it slowly leak system's memory over time? Can I safely ignore them?
Thanks in advice!
Yamil Chamut
