Amanda-Users

Re: Is this OK? "Ignoring cruft file"

2002-08-15 10:51:16
Subject: Re: Is this OK? "Ignoring cruft file"
From: Jon LaBadie <jon AT jgcomp DOT com>
To: "'amanda-users AT amanda DOT org'" <amanda-users AT amanda DOT org>
Date: Thu, 15 Aug 2002 10:37:44 -0400
On Thu, Aug 15, 2002 at 11:47:24AM +0200, Edwin Hakkennes wrote:
> Hi all,
> 
> I added a 'big' disk to my disklist yesterday. About 8G.
> Flushing the files from the holding disk results in 
> 
> NOTES:
>   amflush: beosrv-1._redhat.0.2: ignoring cruft file.
>   amflush: beosrv-1._redhat.0.3: ignoring cruft file.
>   taper: tape xic03 kb 13511296 fm 58 [OK]
> 
> Should I worry about this? Did only 2G of the backup actually make it to the 
> tape?
> The holding disk is empty after this, and it seems to happen only when a disk
> is freshly added to the disklist.

Why do you think only 2GB?  Your chunksize?

The above report says  "kb 13511296", i.e. 13.5GB.
It also says "fm 58", i.e. 58 file marks, about 56 disklist entries.

> If it is due for a full backup lateron, there is no such message.

Don't know what message you might expect,
but try "amadmin xic due beosrv-1 /redhat"
to check when the next full dump is due.

I don't know all the reason for "cruft" files, but occasionally I've seen
empty directories or files that an amflush cleans up and reports as cruft.

> I've set the chunksize of my holding disk to 2G. 

If your file system has a 2GB file size limit, I believe the recommendation
is to have the chucksize below, not at the limit.  If it handles larger files,
then 2GB is fine.

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

<Prev in Thread] Current Thread [Next in Thread>