[DRBD-user] Found a new disk flush error code

Thomas Reinhold it-beratung at thomasreinhold.de
Mon Dec 15 15:14:28 CET 2008

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Thanks for your quick answer.

This is the complete error message (I shoud have posted that in the  
first place, sorry):

> Dec 11 21:47:56 bftest-54 kernel: FAILED
> Dec 11 21:47:56 bftest-54 kernel:   status = 1, message = 00, host =  
> 0, driver = 08
> Dec 11 21:47:56 bftest-54 kernel:   <6>sd: Current: sense key:  
> Illegal Request
> Dec 11 21:47:56 bftest-54 kernel:     Additional sense: Invalid  
> command operation code
> Dec 11 21:47:56 bftest-54 kernel: drbd0: local disk flush failed  
> with status 134217730

What I forgot to mention is that DRBD runs on top of a dm device (dm- 
crypt), which in turn runs on top of the raid array. Could that cause  
the problem?



Am 15.12.2008 um 12:49 schrieb Lars Ellenberg:

> On Mon, Dec 15, 2008 at 10:32:16AM +0100, Thomas Reinhold wrote:
>> Hi all,
>>
>> I'm getting bazillions of disk flush error messages:
>>
>>
>>    drbd0: local disk flush failed with status 134217730
>>
>>
>> Googling the error code did not yield any result. Any idea what  
>> this could be?
>>
>>
>> The system is Debian Etch with DRBD 8.0.13 (etch-backports):
>>
>>
>>    Linux bftest-54 2.6.18-6-amd64 #1 SMP Wed Oct 15 10:07:11 UTC  
>> 2008 x86_64
>>    GNU/Linux
>>
>>
>> The DRBD device is running on top of a RAID-1 set based on LSI 1078.
>>
>>
>> I have disabled disk flushing for now, and the error obiously has  
>> gone. Since
>> we are using an UPS, disabling disk flushing should not be a problem.
>> Nevertheless, I would like to know what the error message indicates.
>
> 134217730
> happens to be
> 0x8000002
>
> that cannot be an accident?
> it smells like a directly propagated scsi_execute_req return value.
>
> to my understanding, lower level drivers should either return "0"
> (Success) or some small negative error code (-EOPNOTSUPP, -ENXIO,
> -ENODEV, maybe -EIO).
> returning 0x8000002 to blkdev_issue_flus is unexpected.
>
> do you have any
>  FAILED
>  status = %x, message = %02x, host = %d, driver = %02x
> in your kernel log prior to that?
>
>
> -- 
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
>
> DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
> __
> please don't Cc me, but send to list   --   I'm subscribed
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20081215/accbe45d/attachment.htm>


More information about the drbd-user mailing list