lkml.org 
[lkml]   [2015]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: linux-next: Tree for Feb 4
From
Date
>>>>> "Sedat" == Sedat Dilek <sedat.dilek@gmail.com> 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


\
 
 \ /
  Last update: 2015-02-04 17:41    [W:0.068 / U:0.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site