Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757244Ab3HAQEk (ORCPT ); Thu, 1 Aug 2013 12:04:40 -0400 Received: from icebox.esperi.org.uk ([81.187.191.129]:49751 "EHLO mail.esperi.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756334Ab3HAQEi (ORCPT ); Thu, 1 Aug 2013 12:04:38 -0400 From: Nix To: Bernd Schubert Cc: Douglas Gilbert , Linux Kernel Mailing List , linux-scsi@vger.kernel.org, "Martin K. Petersen" , nick.cheng@areca.com.tw, stable@vger.kernel.org Subject: Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition References: <87r4ehfzhf.fsf@spindle.srvr.nix> <51F667C2.4020801@fastmail.fm> <87mwp5frdl.fsf@spindle.srvr.nix> <51F67959.2060803@fastmail.fm> <87fvuxdqes.fsf@spindle.srvr.nix> <51F708A4.9090207@interlog.com> <87ob9koogb.fsf@spindle.srvr.nix> <51F80294.50804@fastmail.fm> <877gg7n3rc.fsf@spindle.srvr.nix> <51FA76D6.2060905@fastmail.fm> Emacs: the answer to the world surplus of CPU cycles. Date: Thu, 01 Aug 2013 17:04:25 +0100 In-Reply-To: <51FA76D6.2060905@fastmail.fm> (Bernd Schubert's message of "Thu, 01 Aug 2013 16:55:18 +0200") Message-ID: <871u6dieie.fsf@spindle.srvr.nix> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-DCC-wuwien-Metrics: spindle 1290; Body=7 Fuz1=7 Fuz2=7 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1539 Lines: 40 On 1 Aug 2013, Bernd Schubert verbalised: > On 07/30/2013 11:20 PM, Nix wrote: >> On 30 Jul 2013, Bernd Schubert told this: >> >>> On 07/30/2013 02:56 AM, Nix wrote: >>>> On 30 Jul 2013, Douglas Gilbert outgrape: >>>> >>>>> Please supply the information that Martin Petersen asked >>>>> for. >>>> >>>> Did it in private IRC (the advantage of working for the same division of >>>> the same company!) >>>> >>>> I didn't realise the original fix was actually implemented to allow >>>> Bernd, with a different Areca controller, to boot... obviously, in that >>>> situation, reversion is wrong, since that would just replace one won't- >>>> boot situation with another. >>> >>> Unless there is very simple fix the commit should reverted, imho. It >>> would better then to remove write-same support from the md-layer. >> >> I'm not using md on that machine, just LVM. Our suspicion is that ext4 >> is doing a WRITE SAME for some reason. > > I didn't check yet for other cases, mkfs.ext4 does WRITE SAME and with > lazy init it also will happen after mounting the file system, while > lazy init is running (inode zeroing). Well, it'll happen the first few times you mount the fs. If your fs is years old (as mine are) the inode tables will probably have been initialized by now! -- NULL && (void) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/