Quota problem - Solved.

[SamTzu]

I case you run in to similar problem like this...
The solution is to disable quota and enable it again.

Apr 05 22:11:28 starting migration of CT 162 to node 'temp-1A2cE' (10.10.108.24)
Apr 05 22:11:28 starting rsync phase 1
Apr 05 22:11:28 # /usr/bin/rsync -aHAX --delete --numeric-ids --sparse /media/data2/private/162 root@10.10.108.24:/media/data2/private
Apr 05 22:17:15 IO error encountered -- skipping file deletion
Apr 05 22:19:52 rsync: readlink_stat("/media/data2/private/162/var/lib/amavis/.spamassassin/bayes_journal") failed: Input/output error (5)
Apr 05 22:19:52 ERROR: Failed to sync container private area: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1060) [sender=3.0.7]
Apr 05 22:19:52 aborting phase 1 - cleanup resources
Apr 05 22:19:52 removing copied files on target node
Apr 05 22:20:53 start final cleanup
Apr 05 22:20:53 ERROR: migration aborted (duration 00:09:25): Failed to sync container private area: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1060) [sender=3.0.7]
TASK ERROR: migration aborted

Edit:
Just run in to this again.
First I tried to start the container.

root@czc7460p68:~# vzctl start 152
vzquota : (warning) Incorrect quota shutdown for id 152, recalculating disk usage
vzquota : (error) quota check : lstat `bayes_journal': Input/output error
vzquota on failed [1]

I could not start the 152 from the web-console or the command line. (Editing quota had no effect.)
This fixed it.

root@czc7460p68:~# vzctl quotaoff 152
vzquota : (error) Quota is not running for id 152
vzquota : (warning) Repairing quota: it was incorrectly marked as running for id 152

After this the container started normally.

PS. That bayes_journal is part of SpamAssassin. What's up with that?