Okay, I guess I'll just set a large chunksize, then.  Thanks!

To answer Ian's question, I am simply accustomed to the default being
not to divide backup files up.  Before now, I always thought of
chunksize as only being used if needed and, when not needed and thus
not set, essentially disabled otherwise.  Now I'm poised to set a
rather large chunksize in order to in essence turn it off.  If I really
consider it though, you are right, it doesn't really matter;  Whether
it is enabled, disabled, dividing files, or not dividing files, it
doesn't really matter other than I'm not accustomed to seeing lots of
#, #.1, #.2, #.3 . . . files on the holding disk.  I do have a script
that I've used for years that does not anticipate a holding disk backup
to be in more than one file but turns out it was easy to adapt.  This
is the biggest reason it came to my attention at all.

Do you (and possibly most people) just use the default?

Paul

->>In response to your message<<-
  --received from Ian Turner--
>
> The default is 1 GB, but specifying 0 will just compute a size based on 
> INT_MAX. I don't think there is any way to specify unlimited chunksize, but 
> you could specify whatever your filesystem limit actually is. (2 TiB for ext2 
> with 4KiB blocks)
> 
> Just out of curiosity, why do you care?
> 
> On Wednesday 02 July 2008 15:05:39 Paul Yeatman wrote:
> > Hi, I recently upgraded form Amanda 2.4.4 to 2.6.0.  I used to have
> > chunksize commented out altogether for my holding disks to avoid having
> > things divided up.  Since the upgrade, it is defaulting to a cnunksize
> > of 1G.  Do I simply set it to 0 to not use multiple files?
> >
> > Thanks,
> >
> > Paul
> -- 
> Forums for Amanda discussion: http://forums.zmanda.com/



->>In response to your message<<-
  --received from Dustin J. Mitchell--
>
> From my quick look at chunker.c, it looks like you have to have a
> chunksize.  Setting it to something really large should work.
> 
> Dustin
> 
> -- 
> Storage Software Engineer
> http://www.zmanda.com