Thanks for the quick reply.  The backuppc user uses /bin/sh not bash.  sh is a symbolic link to /bin/dash it looks like.  Not sure if this helps or not.

On Thu, Jul 31, 2008 at 7:58 AM, Holger Parplies <> wrote:

Jeff Rippy wrote on 2008-07-31 06:58:46 -0500 [[BackupPC-users] archive problem]:
> Hi all,
>      I have a Ubuntu 8.04 and BackupPC 3.x.x setup with an LTO-1 drive.
> When I go to archive a host I get the following error:
> Executing: /usr/share/backuppc/bin/BackupPC_archiveHost
> /usr/share/backuppc/bin/BackupPC_tarCreate /usr/bin/split
> /usr/bin/par2 geonosis 75 /bin/gzip .gz 0000000 /dev/st0 0 *
> Xfer PIDs are now 9666
> Writing tar archive for host geonosis, backup #75 to /dev/st0
> /bin/sh: cannot create /dev/st0: Permission denied
> Executing: /bin/sh -c -cf /usr/share/backuppc/bin/BackupPC_tarCreate
> -t -h geonosis -n 75 -s \* . | /bin/gzip >> /dev/st0
> Error: /usr/share/backuppc/bin/BackupPC_tarCreate, compress or split failed
> Archive failed: Error: /usr/share/backuppc/bin/BackupPC_tarCreate,
> compress or split failed
> So it looks like one of the scripts is trying to create /dev/st0 if its not
> there,

no, it looks like the shells output redirection is trying to create /dev/st0
after BackupPC_archiveHost had already determined that it exists. Strangely,
my /bin/sh *never* says "cannot create", only "/bin/sh: filename: Permission
denied" - whether the file exists and permissions prevent writing to it or it
does not exist and directory permissions prevent creating it.

So, I don't know what shell you're using and why it claims to be creating
something that in fact exists, but I'd guess it's simply a permissions problem
on /dev/st0.

Hope that helps.