SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
Rdiff-Backup always fails
Author Message
Post Rdiff-Backup always fails 
Hi everybody,

since some time our backup-script always crashes. The script
itself looks as following:

//--------------------------------------------------------------
script.txt
//-------------------------------------------------------------

When starting the script it gives me this output:

//-------------------------------------------------------------
output.txt
//--------------------------------------------------------------

It's strange but if I comment out everything but the folder /etc
the backup works quite normal.

If I start it with for example /public it crashes. Another
strange fact is, that the system partition seems to be full after
the backup crash. Compare the two outputs of 'df -l'.

Can anybody help me???

thanks in advance

Robert

--
Robert Tafner
tafner < at > dpmi.tugraz.at, http://www.dpmi.tugraz.at
Institute of Human Computer Interfaces
University of Technology, Inffeldgasse 16a, 8010 Graz

Post Rdiff-Backup always fails 
On Wed, 8 Dec 2004 10:59:40 +0100
Robert Tafner <tafner < at > dpmi.tugraz.at> wrote:

Can anybody help me???

You're running out of space on the backup device:

Exception [Errno 28] No space left on device raised of class
exceptions.IOError


I suggest you check your system, mountpoints, etc, to ensure that you
really are backing up to where you think you are.

Keith

Post Rdiff-Backup always fails 
Keith Edmunds <keith < at > midnighthax.com> wrote:

On Wed, 8 Dec 2004 10:59:40 +0100
Robert Tafner <tafner < at > dpmi.tugraz.at> wrote:

Can anybody help me???

You're running out of space on the backup device:

Exception [Errno 28] No space left on device raised of class
exceptions.IOError


I suggest you check your system, mountpoints, etc, to ensure
that you really are backing up to where you think you are.

Well, I have already seen this Exception. But if I reboot the
machine, the system partition has got 8% allocation as before the
backup. If the backup is really made to my system partition it
should be filled with 100% after a reboot, shouldn't it?

thanks Robert

--
Robert Tafner
tafner < at > dpmi.tugraz.at, http://www.dpmi.tugraz.at
Institute of Human Computer Interfaces
University of Technology, Inffeldgasse 16a, 8010 Graz

Post Rdiff-Backup always fails 
On Wed, 8 Dec 2004 11:25:19 +0100
Robert Tafner <tafner < at > dpmi.tugraz.at> wrote:

Well, I have already seen this Exception. But if I reboot the
machine, the system partition has got 8% allocation as before the
backup. If the backup is really made to my system partition it
should be filled with 100% after a reboot, shouldn't it?

Some distributions clear out some directories (eg /tmp) when booting, so
not necessarily. Can you establish where the data is when the root
partition becomes full? (Just in case you need a hand with that, "du -sh *"
in the root directory will point you in the right direction).

Keith

--
----------------------------------------------------------------------
Small business computer support: http://www.tiger-computing.co.uk
Linux consultancy: http://www.TheLinuxConsultancy.co.uk
----------------------------------------------------------------------

Post Rdiff-Backup always fails 
Keith Edmunds <keith < at > midnighthax.com> wrote:

Well, I have already seen this Exception. But if I reboot the
machine, the system partition has got 8% allocation as before
the backup. If the backup is really made to my system
partition it should be filled with 100% after a reboot,
shouldn't it?

Some distributions clear out some directories (eg /tmp) when
booting, so not necessarily. Can you establish where the data
is when the root partition becomes full? (Just in case you need
a hand with that, "du -sh *" in the root directory will point
you in the right direction).

Well, you"re right. I've seen that /tmp is about 980MB. My whole
system partition has got about 1GB so that"s the reason. So I
took a look at /tmp. Here"s what it contains:

:/tmp# ls -la
total 965400
drwxrwxrwt 2 root root 4096 Dec 8 06:26 .
drwxr-xr-x 22 root root 4096 Dec 3 09:27 ..
-rw------- 1 root root 12582864 Dec 8 02:01 < at > 621.0
-rw------- 1 root root 963334144 Dec 8 02:37 < at > 621.1

These two files were created when the backup started. Do you know
what they contain? And can you tell me how to solve this problem.
As mentioned in the first eMail the backup worked for a long
time, so the problem can"t be the size of the system partition...

thanks for your help

Robert

--
Robert Tafner
tafner < at > dpmi.tugraz.at, http://www.dpmi.tugraz.at
Institute of Human Computer Interfaces
University of Technology, Inffeldgasse 16a, 8010 Graz

Post Rdiff-Backup always fails 
On Wed, 8 Dec 2004 12:56:43 +0100
Robert Tafner <tafner < at > dpmi.tugraz.at> wrote:

Well, you"re right. I've seen that /tmp is about 980MB. My whole
system partition has got about 1GB so that"s the reason. So I
took a look at /tmp. Here"s what it contains:

So if you manually copy a file to /mnt/backup/home, does it appear on the
remote system as you expect? Does anything appear in /tmp? What is the
output of "file /tmp/ < at > 621.0"?

Keith

--
----------------------------------------------------------------------
Small business computer support: http://www.tiger-computing.co.uk
Linux consultancy: http://www.TheLinuxConsultancy.co.uk
----------------------------------------------------------------------

Post Rdiff-Backup always fails 
Keith Edmunds <keith < at > midnighthax.com> wrote:


So if you manually copy a file to /mnt/backup/home, does it
appear on the remote system as you expect? Does anything appear
in /tmp? What is the output of "file /tmp/ < at > 621.0"?

I copied a textfile to /mnt/backup/home and it is there. I don't
know what you exactly mean with 'does it apptear on the remote
system'. /mnt/backup/home is local partition and it isn't
exported anywhere to. There's nothing in /tmp. I removed the two
< at > files because otherwise I couldn't run any command (no space
left). Should I start the backup by hand one more time to get the
output of 'file /tmp/ < at > 621.0'?

--
Robert Tafner
tafner < at > dpmi.tugraz.at, http://www.dpmi.tugraz.at
Institute of Human Computer Interfaces
University of Technology, Inffeldgasse 16a, 8010 Graz

Post Rdiff-Backup always fails 
Robert Tafner <tafner < at > dpmi.tugraz.at> wrote:

So if you manually copy a file to /mnt/backup/home, does it
appear on the remote system as you expect? Does anything
appear in /tmp? What is the output of "file /tmp/ < at > 621.0"?

I copied a textfile to /mnt/backup/home and it is there. I
don't know what you exactly mean with 'does it apptear on the
remote system'. /mnt/backup/home is local partition and it
isn't exported anywhere to. There's nothing in /tmp. I removed
the two < at > files because otherwise I couldn't run any command (no
space left). Should I start the backup by hand one more time to
get the output of 'file /tmp/ < at > 621.0'?

Ok. Started it again and after some minutes same output.
"NoSpaceLeftOnDevice' Exception.

Here's the output of 'file' command:

:/tmp# file \ < at > 1325.0
< at > 1325.0: data

:/tmp# file \ < at > 1325.1
< at > 1325.1: data

:/tmp# ls -la
total 965392
drwxrwxrwt 2 root root 4096 Dec 8 13:37 .
drwxr-xr-x 22 root root 4096 Dec 3 09:27 ..
-rw------- 1 root root 12582864 Dec 8 13:37 < at > 1325.0
-rw------- 1 root root 963325952 Dec 8 14:13 < at > 1325.1

Any suggestions?

thanks Robert
--
Robert Tafner
tafner < at > dpmi.tugraz.at, http://www.dpmi.tugraz.at
Institute of Human Computer Interfaces
University of Technology, Inffeldgasse 16a, 8010 Graz

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB