rdiff-backup-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Rdiff-backup-bugs] [sr #106504] locking doesn't work


From: anonymous
Subject: [Rdiff-backup-bugs] [sr #106504] locking doesn't work
Date: Tue, 23 Sep 2008 21:18:18 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; pl-PL; rv:1.9.0.1) Gecko/2008072820 Firefox/3.0.1

URL:
  <http://savannah.nongnu.org/support/?106504>

                 Summary: locking doesn't work
                 Project: rdiff-backup
            Submitted by: None
            Submitted on: Tue 23 Sep 2008 09:18:16 PM UTC
                Category: None
                Priority: 5 - Normal
                Severity: 4 - Important
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
        Operating System: GNU/Linux

    _______________________________________________________

Details:

I have cronjob every hour doing backup to another host. In 1.1.x version, I
didn't care about locking, because I knew that I won't be able to do two
backups in the same time - rdiff-backup won't allow me to do that. 

However, in 1.2.1 rdiff-backup launched in such way:
#v+
rdiff-backup -v5 --remote-schema 'ssh -i /home/maho/.ssh/id_tereska -C %s
rdiff-backup --server' \
        --exclude /home/maho/old_komp \
        --exclude "**.avi" \
        --exclude "**beagle*"   \
        --exclude "**.cache*"   \
        --exclude "**[Cc]ache*"   \
        --exclude "**.etwolf*"   \
        --exclude "**.thumbnails*"   \
        --exclude "**Muzyka*"   \
        --exclude "**[Tt]rash*"   \
                /home address@hidden::/mnt/local-backup/laptop 

#v-

produces such output when there is already running backup:
#v+
(...)
Backup: must_escape_dos_devices = 0
Fatal Error: It appears that a previous rdiff-backup session with process
id 5174 is still running.  If two different rdiff-backup processes write
the same repository simultaneously, data corruption will probably
result.  To proceed with regress anyway, rerun rdiff-backup with the
--force option.
Sending back exception 1 of type <type 'exceptions.SystemExit'>: 
  File "/var/lib/python-support/python2.5/rdiff_backup/connection.py", line
335, in answer_request
    result = apply(eval(request.function_string), argument_list)
  File "/var/lib/python-support/python2.5/rdiff_backup/regress.py", line 377,
in check_pids
    --force option.""" % (pid,))
  File "/var/lib/python-support/python2.5/rdiff_backup/log.py", line 163, in
FatalError
    sys.exit(errlevel)

Previous backup seems to have failed, regressing destination now.
Regressing to Mon Sep  1 18:00:02 2008
(...)
#v-




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/support/?106504>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]