I just installed the sttetch version of amanda common and amanda client, with 
should have restored one of my machines to a full 
backup status.

Unforch, it didn't, and this situtation existed on the previous jessie install, 
where a pi scatters its stuff over a larg e number 
of mount points all attached to /, so basically nothing has actually changed. 

But here is the emailed report from last nights run:
STRANGE DUMP DETAILS:
  /-- picnc / lev 0 STRANGE
  sendbackup: start [picnc:/ level 0]
  sendbackup: info BACKUP=/bin/tar
  sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...
  sendbackup: info end
  ? /bin/tar: ./dev: directory is on a different filesystem; not dumped
  ? /bin/tar: ./proc: directory is on a different filesystem; not dumped
  ? /bin/tar: ./run: directory is on a different filesystem; not dumped
  ? /bin/tar: ./sys: directory is on a different filesystem; not dumped
  ? /bin/tar: ./media/pi/backuppi: directory is on a different filesystem; not 
dumped
  ? /bin/tar: ./media/pi/bootpi: directory is on a different filesystem; not 
dumped
  ? /bin/tar: ./media/pi/workpi1: directory is on a different filesystem; not 
dumped
  ? /bin/tar: ./media/pi/workpi120: directory is on a different filesystem; not 
dumped
  | /bin/tar: ./tmp/.X11-unix/X0: socket ignored
  | /bin/tar: ./tmp/ssh-5i6ERjqwMXjX/agent.705: socket ignored
  | /bin/tar: ./tmp/ssh-VqldgesfylC3/agent.611: socket ignored
  | Total bytes written: 8424396800 (7.9GiB, 5.2MiB/s)
  sendbackup: size 8226950
  sendbackup: end
  \--------
==============
then in the actual report:
==============
picnc   /                           0    8034    3685  45.9 25:48  5314.9  0:25 
150937.9
picnc   /boot                       1      36      29  79.8  0:05  7168.4  0:00 
295570.0

That level 0 should have been around 7 or 8GB. The 1st 4 shoulda been 
in the excludes file and I can fix that easy nuff, as should the last 3.
But it looks as if I'll have to make disklist entries for the pair of 
ssd's plugged into /media.

But thats  not legal either: amcheck says:
ERROR: picnc: Could not access /media/pi/workpi120 (/media/pi/workpi120): 
Permission denied
ERROR: picnc: Could not access /media/pi/bootpi (/media/pi/bootpi): Permission 
denied
ERROR: picnc: Could not access /media/pi/backuppi (/media/pi/backuppi): 
Permission denied
ERROR: picnc: Could not access /media/pi/workpi1 (/media/pi/workpi1): 
Permission denied

/media is owned by root:root, but everything beyond that is pi:pi who is 1st 
user on picnc.coyote.den

What changed to cause this sudden fussiness? Better yet, how do I fix this?

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

Reply via email to