From owner-freebsd-fs@freebsd.org Thu Jun 22 16:38:46 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3F07D901D4 for ; Thu, 22 Jun 2017 16:38:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8041F81534 for ; Thu, 22 Jun 2017 16:38:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22b.google.com with SMTP id m62so53542017itc.0 for ; Thu, 22 Jun 2017 09:38:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=/AU5XL78bUnAcFlDsAhdINqsfKaIO3apC/Ma1Cc6HIQ=; b=oDv87gWIE8IeisZ7kGQ+I77ffkMl2HiH4pFgSQBUmYGICIg6cjWsRwaAkXlhk+YzG9 2dCWbjQD6lLrz7ZKNwh/E8Iaz94CnP9EpMaGyrG3SuZqhQ28XD+muRYFfLJfxY1lnS+d LhXbndDr/dK4pb3MC/rOXRMlVIshatCBCfQx3SatjLM8oVPcbFCNdk1kAp9mWy7eIs2P v+iqblQgYBdiWx/yt5titAcFOJcRQTFOvKZOqdj8B5Ubp0GN/vV6ZM/Oi2GN6WrxfH8+ T6xzmzkc3xn4kNHWpQO+OgTf3/4n/rSnlAtmjCQqCjVa3/V24p7sVvKNUPdrT6hadkFL 7jPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=/AU5XL78bUnAcFlDsAhdINqsfKaIO3apC/Ma1Cc6HIQ=; b=AmckUaAKpFkwZ+dKaRoAmqZKkp8JrHaL6ZjF422BfunUPnpcxMLI5zUAEFyqJ6fRWo G6xgm084eShxDThqSFkw9ETu3JtUJKSbxr3EYMD1A3tgmBndpjyzeo74y3/kt9l/Fojt CBnlG787IswSHQU4mZEYIiZVHaS14qEUpBPgkOPJLAEDLfoQtNBqbx+CFA5SXyZZ76MI pnr5JgFCTlpfoGtjmRy2u6dneCV7u1Istdzo1Ya3sgx6TzDF64/PWdt4wJvR8QI5Lg/Y Tx+oA2K0X+U6qm7cJSiA/sUep09qLMaLC6xNvy/D0EY8JwV6kBm5Sv5iPZUWiQiRRBoq hxhQ== X-Gm-Message-State: AKS2vOz9Vn5nCs5alQebd4DlszpmC0PjkAmIEX1XKwN3IyHNrxY5EYWC 7zCZdqogABrAQPx+Wa1J57vSO6yNv5pB X-Received: by 10.36.20.211 with SMTP id 202mr2965173itg.103.1498149525938; Thu, 22 Jun 2017 09:38:45 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.192.69 with HTTP; Thu, 22 Jun 2017 09:38:45 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:8171:44d0:c310:f5a9] In-Reply-To: <05e6bd02-3582-aea1-5fc3-19caa4073f94@FreeBSD.org> References: <20170610123435.GB69235@FreeBSD.org> <10A08FC1-C84E-4D06-9360-B7C3848F4680@bsd4all.org> <05e6bd02-3582-aea1-5fc3-19caa4073f94@FreeBSD.org> From: Warner Losh Date: Thu, 22 Jun 2017 10:38:45 -0600 X-Google-Sender-Auth: SGukOdEb9ptB2VDlvejvWsReULc Message-ID: Subject: Re: vnode_pager_generic_getpages_done: I/O read error 5 caused by r318394 (was Re: FreeBSD 11.1-BETA1 Now Available) To: Guido Falsi Cc: Peter Blok , Ed Maste , FreeBSD-STABLE Mailing List , FreeBSD FS , Glen Barber , Jonathan Chen Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 16:38:46 -0000 On Thu, Jun 22, 2017 at 2:26 AM, Guido Falsi wrote: > On 06/21/17 16:59, Guido Falsi wrote: > > On 06/13/17 13:44, Peter Blok wrote: > >> Hi, > >> > >> For a while now, I=E2=80=99m not able to build a RPI1-B image from -st= able. I > have narrowed it dow to fix 318394, which adds a refresh option to > geom_label. If I undo this fix in today=E2=80=99s stable it works ok. If = I don=E2=80=99t > I=E2=80=99m getting continuously: > >> > >> vm_fault: pager read error, pid 1 (init) > >> vnode_pager_generic_getpages_done: I/O read error 5 > >> > >> I have looked at the fix and I can=E2=80=99t figure out why it breaks = the code. > >> > >> And yes I have tried various other SD cards - they all have the same > issue. > >> > > > > Hi, > > > > I'm seeing similar symptoms with NanoBSD images on PCEngines ALIX and > > APU2 boards, using compactflash and SD card storage respectively. The > > problem has appeared as soon as I started testing 11.1-BETA1 from the > > stable branch. > > > > Problem appears when I update the image, using a slightly modified > > version of the standard nanobsd update and updatep[12] scripts. My > > changes are not in the dd/gpart commands though, which are the same. > > gpart seems the most likely candidate though. > > > > I have just discovered this thread and I will test reverting r318394 > > soon. Thanks to Peter for narrowing it down! > > > > Maybe this is related to having the disks mounted read-only? > > > > I noticed that after the problem appears many commands, including > shutdown, start failing telling "device not configured" for all mounted > FSes. I'm even unable to "ls /dev". > > Looks like the geom refresh changes devices from below the system in a > way which triggers this reaction. > > I don't know the geom code and have been unable to find an immediate > problem in the commit mentioned above. I'd really like some help to know > where to look, or what kind of debugging information is needed. > > This is quite a bad bug for people running NanoBSD and should be fixed > before the release. > So can I recreate this with the embedded-type NanoBSD image? If this change breaks NanoBSD, it will need to be reverted... Warner