[kwlug-disc] backups capped at 2 gigs

[Insurance Squared Inc.]

I'm starting to narrow this down.  I think maybe it's doing the zip in 
my /root/ directory and thus running out of space.  When I run it 
manually it's running it in the /backup directory which has lots of 
space.  Haven't confirmed that yet though.



On 13/07/10 11:23 AM, John Van Ostrand wrote:
> ----- Original Message -----
>    
>> I don't know how it works with ext2, ext3 or ext4 -- it seems to me to
>> be the same file system for both 32-bit and 64-bit operating systems.
>> Are there intrinsic limits on ext2, ext3 or ext4?
>>      
> The structure on disk is one limitation on how large a file can be stored.
>
> Ext2/3: 2TB max file size limit (for typical 4KB block size, less for smaller block sizes)
> Ext4: 16TB max file size limit (for typical 4KB block size, less for smaller block sizes)
>
> The other aspect to max file sizes is the kernel and system library. The functions for accessing files need to take values larger than "int". This has not been a problem with distros for years, since like Red Hat 7.1 or something like that.
>
> Another aspect is network transport. For example if a file system that supports 2TB files is shared using an old version of NFS, the network file system itself has limits, and so the maximum file size will be the lesser of the two.
>
> Programs may also be a problem if they don't play well. If a program stores a file pointer in an "int" then it will be unable to deal with large files. Any program compiled using modern includes would show an warning if this mistake was found.
>
>    

-- 
Glenn Cooke
Insurance Squared Inc.
(866) 779-1499
www.insurancesquared.com

Insurance Agent Discussion Forum:
www.americaninsurancebroker.com