From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Martin K. Petersen" Subject: Re: linux-next: Tree for Feb 4 Date: Wed, 04 Feb 2015 10:58:23 -0500 Message-ID: References: <20150204193535.58f132c5@canb.auug.org.au> <54D237D9.4070209@kernel.dk> <54D23B58.9000703@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from aserp1040.oracle.com ([141.146.126.69]:39483 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755411AbbBDP6g (ORCPT ); Wed, 4 Feb 2015 10:58:36 -0500 In-Reply-To: (Sedat Dilek's message of "Wed, 4 Feb 2015 16:36:12 +0100") Sender: linux-next-owner@vger.kernel.org List-ID: To: sedat.dilek@gmail.com Cc: Jens Axboe , Stephen Rothwell , linux-next , LKML , "Martin K. Petersen" >>>>> "Sedat" == Sedat Dilek 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