On Tue, May 23, 2006 at 12:29:13PM -0400, Guy Dallaire wrote:
> 2006/5/23, Karsten Fuhrmann <karsten_fuhrmann AT cartoon-film DOT de>:
> >
> >Hello list,
> >i installed a new holding disk in my system and copied all the files
> >of the old holding disks to the new one.
> 
> 
> Did you mount the new holding disk at the same mount point that the previous
> one ?
> 
> All these 'NO FILE TO FLUSH' lines are holding files from the former
> >holding disks.
> >
> >In the amflush.1 file i found the following error messages :
> >
> >size_holding_files: open of /raid/15/20060513000000/stern.cartoon-
> >film.de._usr.4.1 failed: No such file or directory
> >stat /raid/15/20060513000000/stern.cartoon-film.de._usr.4.1: No such
> >file or directory
> >build_diskspace: open of /raid/15/20060513000000/stern.cartoon-
> >film.de._usr.4.1 failed: No such file or directory
> >size_holding_files: open of /raid/15/20060513000000/stern.cartoon-
> >film.de._raid_13_LINETEST.0.1 failed: No such file or directory
> >stat /raid/15/20060513000000/stern.cartoon-film.de._raid_13_LINETEST.
> >0.1: No such file or directory
> >build_diskspace: open of /raid/15/20060513000000/stern.cartoon-
> >film.de._raid_13_LINETEST.0.1 failed: No such file or directory
> >
> >The filename in this logfile are wrong, but amanda still uses the old
> >holding disk names.
> >
> >Is there a way to tell amanda that i moved the holding files
> >somewhere else ? I checked the curinfo files but didnt found any hint
> >where this information is stored! At least the holding disk path isnt
> >there in cleartext!
> 
> 
> I would make a symbolic link from the old holding disk location to the new
> one and try to re-run amdump.
> 
> Ex: ln -s /you_new/holding_disk_directory /your_old_holding_disk_directory
> 
> After running amdump, the new amanda runs should use the new holding disk

My suggestion was going to be similar to Guy's.

I'd consider adding your old holding disk location to amanda.conf
as a second holding disk.  Then make same name symbolic links to
the current location of the files and run amflush.

If that is succesful, remove the second holding disk definition.

I'm guessing the original location of the files is in the dump logs.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)