On 11/03/2014 02:33 PM, Dušan Čolić wrote:
I forgot:
It was working for some time (deleting old directories etc.) and then crashed.
Btw. why didn't that partition (/dev/md125) remounted read-only on
error when I have that in /etc/fstab?
What do you suggest to do when encountering IO error?
There is another option: to oops. You like this better?
Edward.
On Mon, Nov 3, 2014 at 2:28 PM, Dušan Čolić <dusanc@xxxxxxxxx> wrote:
After an hour or more still nothing, one rsync went to zombie other
still in D state
I killed the main process and rebooted.
krshina3 goran # ps -aux | grep rsync
root 6655 0.0 0.1 101568 9328 pts/4 D 13:08 0:01
/usr/bin/rsync -ax --delete --numeric-ids --relative --delete-excluded
--exclude=/home/windows.qcow2
--link-dest=/mnt/backup/daily.1/localhost/ /home
/mnt/backup/daily.0/localhost/
root 6656 0.0 0.0 0 0 pts/4 Z 13:08 0:00
[rsync] <defunct>
Now I tried same command (rsnapshot -c /etc/rsnapshot.d/daily.conf
daily) and kernel BUGed with:
krshina3 goran # rsnapshot -c /etc/rsnapshot.d/daily.conf daily
rsync: writefd_unbuffered failed to write 5 bytes to socket
[generator]: Broken pipe (32)
----------------------------------------------------------------------------
rsnapshot encountered an error! The program was invoked with these options:
/usr/bin/rsnapshot -c /etc/rsnapshot.d/daily.conf daily
----------------------------------------------------------------------------
ERROR: /usr/bin/rsync returned 0.04296875 while processing /home/
WARNING: Rolling back "localhost/"
rsync error: error in rsync protocol data stream (code 12) at
io.c(1532) [generator=3.0.9]
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
