On Wednesday, January 28, 2015 at 10:44:38 AM UTC-2, John Bolt wrote:
> Hello,
> 
> Please inform the procedure to fix the following backup error after the 
> backup:
> 
> 
> fedora18-sd Elapsed time=01:58:01, Transfer rate=68.49 M Bytes/second
> fedora18-sd Alert: smartctl 6.2 2013-07-26 r3841 
> [x86_64-linux-3.11.10-100.fc18.x86_64] (local build)
>  Alert: Copyright (C) 2002-13, Bruce Allen, Christian Franke, 
> www.smartmontools.org
>  Alert:
>  Alert: Smartctl open device: /dev/st0 failed: Device or resource busy
>  3997 Bad alert command: sh -c 'smartctl -H -l error /dev/st0': ERR=Child 
> exited with code 2.

Hello Marco,

Thanks a lot for the clear explanation. I really appreciate.

When checking for the tape device with lsscsi --generic I got a /dev/st0 
/dev/sg5 answer and not a /dev/nst0 and that misled me to conclude that your 
"Example Storage Daemon Configuration File" in the Chapter 10.7 of the manual 
should be corrected to my "real" device.

Maybe a comment should be added to the corresponding "Archive Device" lines in 
the manual to help avoid others to make the same error.

Searching the web for more "rewinding or non-rewinding" explanations I found 
the following: "usually you should use the non-rewinding device nodes to avoid 
having the drive rewind unexpectedly. When using Backup software like Bareos, 
you actually MUST use the non-rewinding device, otherwise you may get into 
trouble (the software does its own rewinds and doesn't expect the tape to be 
rewound without it having done it itself).

I hope this feedback may help anyone who may fall in similar problems or that 
the manuals could include some information of this kind to improve the user 
experience with Bareos.

-- 
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