I've never had amflush complain about chunks being cruft files. It writes them to tape and removes them. If amdump dies you might end up with cruft files (both chunks and full files), but an amcleanup followed by an amflush generally clears things out.
Frank --On Thursday, March 07, 2002 12:30:54 -0500 Mike Cathey <[EMAIL PROTECTED]> wrote: > Joshua, > > The annyoing thing about using this hack is that if you have to use amflush >(something goes wrong), then it (amflush) gives you errors about removing cruft files >for all of the files that split creates. An ingenious hack nonetheless... :) > > If you have the disk space, you could switch the holding partition to ReiserFS or >maybe ext3 (it supports files larger than 2GB right?) > > I'm assuming his amanda server is running on linux... > > Cheers, > > Mike > > -- > > Mike Cathey - http://www.mikecathey.com/ > Network Administrator > RTC Internet - http://www.catt.com/ > > Joshua Baker-LePain wrote: > >> On Wed, 6 Mar 2002 at 4:32pm, Charlie Chrisman wrote >> >> >>> /-- countach.i /dev/sda3 lev 0 FAILED ["data write: File too large"] >>> >>> I get this for two of my clients? what does this mean? >>> >>> >> FAQ. Set your chunksize to something less then 2GB-32Kb. 1GB is fine -- >> there's no performance penalty. >> >> > -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
