Subject: Re: linux-next: Tree for Feb 4

From: "Martin K. Petersen" <[email-masked]>
Date: Wed, 04 Feb 2015 10:58:23 -0500

>>>>> "Sedat" == Sedat Dilek <[email-masked]> writes:

>>>>> I am seeing the following in my logs several times...
>>>>> 
>>>>> Feb 4 02:53:13 fambox kernel: [15507.397482] blk_update_request:
>>>>> I/O error, dev loop0, sector 21261344 Feb 4 02:53:13 fambox
>>>>> kernel: [15507.397531] loop0: DISCARD failed.  Manually zeroing.

Sedat> What's the plan... s/pr_warn/pr_debug ?

The rationale here is that we'd like to log (once) if discard or write
same fail on a given device.

In SCSI we disable these commands if they get failed by the storage. But
it looks like loop keeps advertising discard support after a failure.

Is your loop device encrypted? Do you know why the discard is failing?

-- 
Martin K. Petersen	Oracle Linux Engineering