When I use root to tar up some filesystems in AIX 4.3.3 ML10, for those files with 9GB or more will return "File too large" and fail to tar that files. fsize already set = -1. Any help?
When I use root to tar up some filesystems in AIX 4.3.3 ML10, for those files with 9GB or more will return "File too large" and fail to tar that files. fsize already set = -1. Any help?
"Kenneth" < XXXX@XXXXX.COM > schrieb im Newsbeitrag Hi Kenneth, this "problem" has been discussed in this group before quite often. AIX tar cannot handle files bigger than 2 Gig. Use gnu-tar or aix-backup/restore. Regards, Andreas
AIX seems to be seriously underprogrammed, eg. grep: 0652-226 Maximum line length of 2048 exceeded. I can't even begin to imagine what sort of programmers they're using. ``Hmm, this ought to be big enough. Pointers are so confusing.'' -- Ron Hardin XXXX@XXXXX.COM On the internet, nobody knows you're a jerk.
to AIX tar aix-backup/restore. IBM didn't write grep, awk, sed etc and are probably using some version of the original code under licence. It's probably SCO's fault. Why they haven't removed some of the historical boundary conditions I don't know but I stopped worrying about it by using the GNU equivalents, if and when necessary.
"RobH" < XXXX@XXXXX.COM > schrieb im Newsbeitrag Hallo, quote from man tar (from the 5.1 commands reference): "The tar command is not enabled for files greater than 2 Gig in size due to limitations imposed by XPG/4 and POSIX.2 standards." Thus AIX tar works as designed, it's a feature and not a bug. Regards, Andreas
Actualy, when POSIX was created (defined) someone decided that a text line in POSIX could not be more than 2048 - a clear violation of the unix philosophy. AIX happens to be POSIX-compliant. -- Doing AIX support was the most monty-pythonesque activity available at the time. Eagerly awaiting my thin chocolat mint.
2.Apache proxy server returns empty file (file size 0)
3.large file support && ! large file support
It seems a program cannot access BOTH the old (without large file support) and new (with large file support) interfaces at the same time. For example, when large file support is not turned on, type off_t is 32 bits and off64_t is not defined. But when LFS is turned on, off64_t does get defined, and off_t is redefined as 64 bits. Is there a way to have both definitions active in their respective ways? The purpose is building a library which provides certain kinds of wrapping around system or library calls that do deal with interface changes due to large file support. -- |---------------------------------------/----------------------------------| | Phil Howard KA9WGN (ka9wgn.ham.org) / Do not send to the address below | | first name lower case at ipal.net / XXXX@XXXXX.COM | |------------------------------------/-------------------------------------|
4.Using tar to backup large files
In comp.os.linux.misc Tim Edwards < XXXX@XXXXX.COM > wrote: > I would like to know if its possible to backup and restore tar backups > greater than 2gb in total size split into ~650mb chunks. I have an Mp3 > folder with about 2.3gb of stuff in it that I use tar to archive into > several 650mb files. However what happens when I want to restore them? I > have tried creating a tar file greater than 2gb and it seems that tar > cannot extract files from such an archive. I'm running Mandrake 9.1, on This would depend on the way tar was compiled. There is nothing in principle stopping it, I think. > ext3 partitions and I've successfuly created files (including a tar > archive) larger than 2gb on disk. > Once that > 2gb tar archive is created and split into 650mb chunks I need to > know how to recombine them and successfuly extract the files from the Just cat them together and stream them into tar's stdin. cat foo* | tar xvf - > recombined tar archive. Peter
5.tar error - file's is too large
Hello All, i have a question (& problem :) In p570 server create (use mksysb) system backup to a nim server have 12 files - but two it's too large :) s10_root /common/mksysb_images>l \total 185945344 -rw-r--r-- 1 root system 11511500800 Oct 08 18:27 s10.20061007.mks -rw-r--r-- 1 root system 13974220800 Oct 08 19:00 s10.20061008.mks -rw-r--r-- 1 root system 5507788800 Oct 07 23:52 s11.20061007.mks -rw-r--r-- 1 root system 8665907200 Oct 08 18:23 s11.20061008.mks -rw-r--r-- 1 root system 5398630400 Oct 07 23:54 s12.20061007.mks -rw-r--r-- 1 root system 8427161600 Oct 08 18:27 s12.20061008.mks -rw-r--r-- 1 root system 5492172800 Oct 08 00:22 s20.20061007.mks -rw-r--r-- 1 root system 7875993600 Oct 08 18:49 s20.20061008.mks -rw-r--r-- 1 root system 5381324800 Oct 08 18:31 s21.20061007.mks -rw-r--r-- 1 root system 8402534400 Oct 08 18:44 s21.20061008.mks -rw-r--r-- 1 root system 5648691200 Oct 08 18:36 s22.20061007.mks -rw-r--r-- 1 root system 8915763200 Oct 08 18:51 s22.20061008.mks s10_root /common/ZRZUTY/mksysb_images>tar cvf /dev/rmt4 * tar: 0511-825 The file 's10.20061007.mks' is too large. tar: 0511-825 The file 's10.20061008.mks' is too large. a s11.20061007.mks 10757400 blocks. Any question ?? Regards, Pawel (PL)
Users browsing this forum: No registered users and 39 guest