Quote:
Originally Posted by raju.mopidevi
To backup our files you can use "cpio"
|
thx, i'll search it.
Quote:
Originally Posted by timvandijk039
Hi Toredo,
here are some thoughts...
1. Are the files accessible from the specified cron user? Eg. correct file- and directory permissions; Is the file system mounted and accessible for the cron user?
2. How big is the tar-file and what type of file system are you using? Some file systems have a pretty low file size limit. Eg: FAT16 has a file size limit of 2GB and FAT32 has it's limit at 4GB.
3. What is the output of: (You might be hitting the limit of the maximum open file handle count)
Hope this helps.
Best regards,
Tim |
thx for the help, here the answers
1)the last times i tried to run it as root, but there was the same error.
2)the resulting file is ~30mb, the source and the target filesystems are both ext3.
3)this is the output from "ulimit -a":
Code:
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 479
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 479
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Quote:
Originally Posted by leopard
Hello toredo,
Your title is rather indefinite and doesn't provide an accurate synopsis of the problem. A descriptive title is always beneficial in the long run; it helps you get more relevant replies faster and it allows other users to find it with the search function. Your description is OK, but it would improve the readability of your post if you chose to use correct spelling, punctuation and grammar. Please see this tutorial for more details.
By the very nature of the error, one would assume that the file in question may be corrupt, or it is not really compressed. Wikipedia provides proof of this concept. Use:-
to check the status of the file. This will be beneficial in your diagnosis.
Remember that a simple Google search often will yield some insight to any particular problem. |
thx for the answer, i'll try to write a better english, but it's not my native language and i'm not very good in english, so i have problems to write a good text. but i'll try it:-)
ok, i used the file-command:
Code:
10-03-16.tar.bz: bzip2 compressed data, block size = 900k
i tried it with a corrupted and a normaly archive, both gave the same output.
ok, i use the google-link to search again. i already searched, but may be i used the wrong key words.
Quote:
Originally Posted by jschiwal
Redirect the output of stderr to a file. Study the output for error messages. Writes to stdout or reads from stdin will be blocked in a cron job which could account for a partially complete archive. Make sure you define any environmental variables and PATH entries you need. Also post your cron job. More eyeballs may be able to spot something you missed.
|
ok, good idea, i'll change the job and write the stderr to a file.
20 3 * * * root /root/scripts/backup.sh /home/vss vss 20
backup.sh creates a backup archive on a defined path. the number on the right means the maximal number of backup-archives for "/home/vss".
best regards
toredo
