Lloyd Duhon <[EMAIL PROTECTED]> writes: > That would be wonderful, if there is a way to do that. I am not > personally aware of a way. I would be sufficiently happy to just > extract a few files from the archive, that is my primary goal at this > time. If anyone knows of any way, no matter how time or hardware > consuming it is, please let me know. > > At 09:13 AM 5/16/2002 -0500, you wrote: >> I'm not that experienced with TAR and GZIP, but it may be possible >> to TAR/GZIP you 6GB file into a series of smaller files that DO >> transfer correctly. >> >>The file that this data resides in is 5.6 GB, a .tgz file. when I try to >>perform any operation on the file, I get the error "Operation Not >>Permitted" or similar. the most expressive error message was from lsattr: >>lsattr: Operation not permitted While reading flags on >>/Raid/Backup.cp1/cp1/2002_Mar/03.Full.tgz >>file returns: >>/Raid/Backup.cp1/cp1/2002_Mar/03.Full.tgz: can't stat >>`/Raid/Backup.cp1/cp1/2002_Mar/03.Full.tgz' (Value too large for defined >>data type).
Hm - what I want to say rather pertains to reading the file at all, not necessarily splitting it. The general consensus seems to be that it is some kind of 'large file' problem, so one viable alternative might be to 'hide' the file size from the programs working on it, using pipes. What does cat 03.Full.tgz | tar tvzf - do? Is there an error message? If yes, what does cat 03.Full.tgz > /dev/null do? Is there still an error message? If yes, it would appear that you cannot read the file at all for whatever reason - what exactly is the system you're working on like? (Distribution/Release, Kernel Version) Another way to achieve essentially the same thing using dd instead of cat would be dd if=03.Full.tgz bs=10k | tar tvzf - or dd if=03.Full.tgz of=/dev/null respectively. If you need more help, please tell me your distribution (cat /etc/issue if it is redhat), and the versions of all major utilities, which can be obtained using ver_linux (included in the kernel-source-*.rpm (not the kernel-*.src.rpm)) like this: sh /usr/src/linux-<version>/scripts/ver_linux It is not necessary for the kernel source rpm to exactly match the kernel you are running (for getting the ver_linux information, anyway). Please cut&paste ver_linux's output along with all error messages from the commands above, perhaps that sheds a little more light on the matter. So long, Joe -- "I use emacs, which might be thought of as a thermonuclear word processor." -- Neal Stephenson, "In the beginning... was the command line" _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
