Since I deleted this line the problem does not occur anymore. I had this option switched on for one year an the bug occurred since Ubuntu 12.10. That leads me to the conclusion:
The bug must have to do something with power saving of the scsi host and there must be a change between linux 3.2 and 3.5 that leads to the bug.
I found a workaround for this bug: I had script to configure some power saving options and this script hat the following line:
Since I deleted this line the problem does not occur anymore. I had this option switched on for one year an the bug occurred since Ubuntu 12.10. That leads me to the conclusion:
The bug must have to do something with power saving of the scsi host and there must be a change between linux 3.2 and 3.5 that leads to the bug.