New answers tagged tar
First of all, the the overall power consumption will be likely the same or more if you artificially slow down the backup process. Simply because the total number of operations is the same and if the process takes longer, the cpu consumes less peak power but over a longer time. For example, if the process runs for 10 s at peak power of 200W this will consume ...
One approach would be to use parallel compression in order to use all of the cores of your system and therefore reduce the compression time. It won't reduce the load on your system, but it will be loaded for a shortest amount of time ! You can find how to do it in this Q/A for example : utilizing-multi-core-for-targzip-bzip-compression-decompression For ...
There are a few issues with your question and what you're doing: You say that the tar file is compressed, yet you use a filename that indicates that this might not be the case (it has no suffix from any common compression tool). You have probably mistyped or simply not thought about that command line. Let us assume that the tar file is compressed (remove ...
As you have not mentioned compress in your question, I would recommend you to use tar -cf files.tar /path/to/file0 /path/to/file1 ; gzip -9 files.tar Or tar cf - /path/to/directory | gzip -9 - > file.tar.gz in both commands gzip -9 specifies maximum possible compression level (default is -6).
Let me get this correct: You are trying to create a tar file with the contents being a single file called "filename" ? How big is the file denoted as filename ? Is the file filename already compressed? If filename is already, compressed, adding the compression flag "z" to the tar command will make it take longer. Try without the compression flag. ...
what about: tar -C $HOME -cvzf dotfiles.tgz .
The entry --exclude=/var/backups should read --exclude=var/backups to match the pattern expected by tar
The problem is in how tar stores files. So, for example $ echo hello > a $ ln a b $ tar cf foo.tar a b $ tar tf foo.tar a b The problem happens when you try to extract just one file $ mkdir Y $ cd Y $ tar xvf ../foo.tar b b tar: b: Cannot hard link to `a': No such file or directory tar: Exiting with failure status due to previous errors What you ...
Don't rely on wildcard matching / shell globbing but instead use the find command to find and list the files you want and send that list to tar to be archived: find /A/ -type f -print0 -name \*.log | tar -cvf /path/to/file.tar --null -T -
It's important to understand there's a trade-off here. tar means tape archiver. On a tape, you do mostly sequential reading and writing. Tapes are rarely used nowadays, but tar is still used for its ability to read and write its data as a stream. You can do: tar cf - files | gzip | ssh host 'cd dest && gunzip | tar xf -' You can't do that with ...
why people use it so much despite this drawback? Corporate and Academic admins are often more noticed when things break, than appreciated when things run efficiently. Such environments breed fear of experimentation, and scorn for novelty. what choice(I mean other software/tool) do I have if I want the "instant content listing" capability? ...
Top 50 recent answers are included