Received: by 10.192.165.156 with SMTP id m28csp492514imm; Mon, 16 Apr 2018 04:01:52 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/aLbE6fwm58mKNvuyor9lrrZXZ6HintQk8COm9KHQxHWcMpqCOwjc9JO2pVpRZuGA0VXDf X-Received: by 10.101.66.199 with SMTP id l7mr1755925pgp.335.1523876512278; Mon, 16 Apr 2018 04:01:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523876512; cv=none; d=google.com; s=arc-20160816; b=rb1EBG/PkkBqbgwa95Jw1J2wC2/VziBJGRmSl+/tN5JkSS1720jekPtd03MkT9FzzS M+q5ntNsSjLb4RLvRNRgF/MZU28/q7lyz4vdOeZ8dPKEMwgUCXpp2wacVms9m/2b97HG RiK3lZ6ZaX+tfhON9oe3UnP2TEwz+isz02DPyPn53JuCT21LMnJ2YyjX9Oh1XMlFn0NI n9SwsCIxXWEMOTOT4uX3pn8qqS5oUqtYjkN8qozVqiwGZ6h/kt+CeBHbW8XbncefoFey nv+9GIe5ueUJX6eBmAfAszeep0uWZhraOyvlDczX8ueBy2c/y5CE6PMIsxNe7/UIieCq jZFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=YkRtEvhmWafYGP4hJF7l2GhEsgryy3HuVaVGxlt5uls=; b=lVhYwfZEX5QJA9atuBb93zKV5nKDyx64/IDLeQXvHJecgZCNchiK+OWeCQX602dUkr qqWufdbVkKRlINBCM4zpBoK3H8vZb7GFgou3AhQHjCT5r2iPUWa5m9oLSVZ8tyRtjKzD Ur07WKGqJuNVQLJeDW63wYQkjDxc/D89o1E7A62BgZUPlz/41CPOt77EdIX27kIu15aM MNgQdCNBZ9lsPEa5tlKm6eAWhoA3OpumYo8Rko81/o6rrc5OP4FC1Ac9FL38analyNzI YQZS7a7hXnSsXFn+3TM7IXSu9XIuHmZpk3i+qH2Tm+pTLZS+vXC24RtuK4y+yxTwJDWt IUxA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@broadcom.com header.s=google header.b=Q3XwvJhO; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k2si6359155pgs.4.2018.04.16.04.01.25; Mon, 16 Apr 2018 04:01:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@broadcom.com header.s=google header.b=Q3XwvJhO; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754408AbeDPJGf (ORCPT + 99 others); Mon, 16 Apr 2018 05:06:35 -0400 Received: from mail-pg0-f65.google.com ([74.125.83.65]:33046 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754157AbeDPJGd (ORCPT ); Mon, 16 Apr 2018 05:06:33 -0400 Received: by mail-pg0-f65.google.com with SMTP id i194so3526436pgd.0 for ; Mon, 16 Apr 2018 02:06:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YkRtEvhmWafYGP4hJF7l2GhEsgryy3HuVaVGxlt5uls=; b=Q3XwvJhODfYqz5PSIu8dbQNIyR+hx9JaCFe0eGvN1DN0ZHc/5+dvjzWErImv6i/y70 CbiRfAruBHt6iXD3wQhdNassppGCKBmBb9WoOZLt07qfTZWfQATcdzC0A7LB4XF4zO/y scGViziih1PjuLVQeITnyQYX0hCe0qafZljkg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YkRtEvhmWafYGP4hJF7l2GhEsgryy3HuVaVGxlt5uls=; b=h9f2uOJBGb/m9s2re5/MVuVoQH5b48V98TgDeHBYJs2Jx1jrwEQdoVpP2iQp+jlLu2 8CbKBw95lVkHSFivHpQKxcIKmMBeVOmdgGL3X+7WnmJVfUY2C6z0JshpJwAUFgfY29cd nUuNObObjpE7NQ1x8vMlEhK9yVzv3toANx3R+NwKMVN2gT3+ThgMfG4O7sNqHNDRvdWl anbxJfhqYr/DQmvckgAjAVlHn2U8wikRroeJyQxsjR6kgNPbkX6OPcCzuhub5l7T8gUj cr+3B0yFo3uB+2WiyvlCdmxUYEYb16izzGZX4X+RFIsSmVAzXDjwqXn22eY6V+lmm5tP bfoA== X-Gm-Message-State: ALQs6tAxoHjiIohND7gsBpqRr4bp7cEX6xSD3uUzJVgh9ic6w19ym2Up Ixqi/aMmGY56a+Myadbh91DFszR1YbwFsSwznCKT1w== X-Received: by 10.99.114.80 with SMTP id c16mr8444748pgn.385.1523869592605; Mon, 16 Apr 2018 02:06:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.154.68 with HTTP; Mon, 16 Apr 2018 02:06:31 -0700 (PDT) In-Reply-To: References: <1523524915-25170-1-git-send-email-jinpu.wangl@profitbricks.com> From: Sreekanth Reddy Date: Mon, 16 Apr 2018 14:36:31 +0530 Message-ID: Subject: Re: [PATCH v2] block: ratelimite pr_err on IO path To: Jinpu Wang Cc: "Martin K. Petersen" , Jens Axboe , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, "Elliott, Robert (Persistent Memory)" , Suganath Prabu Subramani , Chaitra P B , linux-scsi Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 16, 2018 at 1:46 PM, Jinpu Wang wrote: > On Fri, Apr 13, 2018 at 6:59 PM, Martin K. Petersen > wrote: >> >> Jinpu, >> >> [CC:ed the mpt3sas maintainers] >> >> The ratelimit patch is just an attempt to treat the symptom, not the >> cause. > Agree. If we can fix the root cause, it will be great. >> >>> Thanks for asking, we updated mpt3sas driver which enables DIX support >>> (prot_mask=0x7f), all disks are SATA SSDs, no DIF support. >>> After reboot, kernel reports the IO errors from all the drives behind >>> HBA, seems for almost every read IO, which turns the system unusable: >>> [ 13.079375] sda: ref tag error at location 0 (rcvd 143196159) >>> [ 13.079989] sda: ref tag error at location 937702912 (rcvd 143196159) >>> [ 13.080233] sda: ref tag error at location 937703072 (rcvd 143196159) >>> [ 13.080407] sda: ref tag error at location 0 (rcvd 143196159) >>> [ 13.080594] sda: ref tag error at location 8 (rcvd 143196159) >> >> That sounds like a bug in the mpt3sas driver or firmware. I guess the >> HBA could conceivably be operating a SATA device as DIX Type 0 and strip >> the PI on the drive side. But that doesn't seem to be a particularly >> useful mode of operation. >> >> Jinpu: Which firmware are you running? Also, please send us the output >> of: >> >> sg_readcap -l /dev/sda >> sg_inq -x /dev/sda >> sg_vpd /dev/sda >> > Disks are INTEL SSDSC2BX48, directly attached to HBA. > LSISAS3008: FWVersion(13.00.00.00), ChipRevision(0x02), BiosVersion(08.11.00.00) > mpt3sas_cm2: Protocol=(Initiator,Target), > Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set > Full,NCQ) > > jwang@x:~$ sudo sg_vpd /dev/sdz > Supported VPD pages VPD page: > Supported VPD pages [sv] > Unit serial number [sn] > Device identification [di] > Mode page policy [mpp] > ATA information (SAT) [ai] > Block limits (SBC) [bl] > Block device characteristics (SBC) [bdc] > Logical block provisioning (SBC) [lbpv] > jwang@x:~$ sudo sg_inq -x /dev/sdz > VPD INQUIRY: extended INQUIRY data page > inquiry: field in cdb illegal (page not supported) > jwang@x:~$ sudo sg_readcap -l /dev/sdz > Read Capacity results: > Protection: prot_en=0, p_type=0, p_i_exponent=0 > Logical block provisioning: lbpme=1, lbprz=1 > Last logical block address=937703087 (0x37e436af), Number of > logical blocks=937703088 > Logical block length=512 bytes > Logical blocks per physical block exponent=3 [so physical block > length=4096 bytes] > Lowest aligned logical block address=0 > Hence: > Device size: 480103981056 bytes, 457862.8 MiB, 480.10 GB > > >> Broadcom: How is DIX supposed to work for SATA drives behind an mpt3sas >> controller? [Sreekanth] Current Upstream mpt3sas driver doesn't have DIX support capabilities, it supports only DIF feature. Thanks, Sreekanth >> >> -- >> Martin K. Petersen Oracle Linux Engineering > > > Thanks! > > -- > Jack Wang > Linux Kernel Developer > > ProfitBricks GmbH > Greifswalder Str. 207 > D - 10405 Berlin