From owner-freebsd-questions@freebsd.org Wed Nov 14 02:48:24 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6B2C1105E33 for ; Wed, 14 Nov 2018 02:48:23 +0000 (UTC) (envelope-from va6bmj@gmail.com) Received: from mail-vk1-xa30.google.com (mail-vk1-xa30.google.com [IPv6:2607:f8b0:4864:20::a30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 28611888F4 for ; Wed, 14 Nov 2018 02:48:23 +0000 (UTC) (envelope-from va6bmj@gmail.com) Received: by mail-vk1-xa30.google.com with SMTP id t127so3306590vke.8 for ; Tue, 13 Nov 2018 18:48:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=z0yygpav0Ifvv5JFs2kvq7/y1Hi7Lcfi+uLosdXHrVM=; b=obu+c833c1doR9VqqHRa7qarbTqKNMbR0miu1Mr6T+V/gms6yMPgHlWJ3WIdPjzKB2 XiuzXHaw3JEIz0qIypBik0y44RLTMJQjXrkGnKiCvG8Yfkvf2rEvu34iUk1L4xqNS83I Y87SJYXaKqazwxgYq/KUej0Z0LpLTWQv4fawFy1Oa2nI+E0iQN4ibH6DDMdjrothxmAK l/Jz/IcQqtXzkItN8ekIrz+aVRAMy8V6Myl7gxFJar/gmul/kuwZPSx8CjVxDNSUFRZh CDYcQmJVTb61vSl10NVYNQkCDYY5kUG9qJsuBiq9HICReG22m4SX369leqqScKrqxXIp tJ7g== 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=z0yygpav0Ifvv5JFs2kvq7/y1Hi7Lcfi+uLosdXHrVM=; b=R/i2e3mmavVlGTfbGutGIKgALGOYDW8jJIM9eS9rtkWYiQiKX4D9MLoeSy59HwYSSl /3uK35ALuqSruaAEd8jPJzVMT7+4+vWRDnjDsRJ66jed7cckmIKsevMxbtXYflkkmKea Nv+4TsvN3l4cjUGeFZE54mc3aNbQSO9+Ahi6N6M/DeJd5XGTz/wVuA+AUlVNk4dpMAtE 0UNcBFxfz0DWNYzzBZ5eykdiwTModJ4Ud691X0KBmRYZtrqM42DwL4hyJse9IddRVvZT IG5L2zBey+hP8c6eYPRcGoXydd4XTHNOLWca6n+0xoZFGW+dodFDB1wQQgqshjpI4pY0 59lw== X-Gm-Message-State: AGRZ1gIE3zJJVv+G96asaSSkEzo1foDMHJ28ewNi6b7NhrvvoGNkoJmN NMnBkqFm7AChmuBulK1cj1++8aMl9nECCfbFaJ3KT2au X-Google-Smtp-Source: AJdET5efd/PZpG6Cy9Z371x5DUv3rDS15gtZLc/8ccMXGFOlJM88FpS1/j53IKaVOjrA1O1nPjecYKlcuDIpcVMrxa4= X-Received: by 2002:a1f:95d1:: with SMTP id x200mr44146vkd.78.1542163702304; Tue, 13 Nov 2018 18:48:22 -0800 (PST) MIME-Version: 1.0 Received: by 2002:ab0:54c3:0:0:0:0:0 with HTTP; Tue, 13 Nov 2018 18:48:21 -0800 (PST) In-Reply-To: <20181113224915.9429e289.freebsd@edvax.de> References: <20181113182954.1d7060bd.freebsd@edvax.de> <20181113201830.f0eec001.freebsd@edvax.de> <20181113205020.afc446d9.freebsd@edvax.de> <20181113224915.9429e289.freebsd@edvax.de> From: B J Date: Wed, 14 Nov 2018 02:48:21 +0000 Message-ID: Subject: Re: Kernel Panics With Firefox 63.x To: Polytropon Cc: freebsd-questions Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 28611888F4 X-Spamd-Result: default: False [-4.90 / 200.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[0.3.a.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.95)[-0.953,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; IP_SCORE(-0.94)[ipnet: 2607:f8b0::/32(-2.75), asn: 15169(-1.85), country: US(-0.09)] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2018 02:48:24 -0000 On 11/13/18, Polytropon wrote: >> I halted the building process and did as you suggested earlier. There >> were indeed a number of inconsistencies and corrupted files when I ran >> fsck in single-user mode. > > Excellent! > > Always make sure the file system consistency is present > _before_ the system boots; relying on background fsck > just asks trouble. ;-) > > Technical sidenote: The background fsck can only handle > a subset of errors. Common errors, sure, but sometimes > there is something it cannot correct or repair, and you > boot into an inconsistent system state, but without any > warning. A foreground fsck makes sure that _if_ such a > problem is recognized, you will be interactively prompted, > so you can decide what to do. In very few cases you do > _not_ want fsck to do anything, as it might make data > recovery more problematic; for example, you first decide > to "mount -o ro /something", retrieve data, then run > fsck and maybe end up with zero length files (whose > content you have already recovered), and then you "re-fill" > those files; or you need to use fsdb to help fsck with > a problem it cannot work around. > > However, for typical use, a foreground fsck will be the > right thing to do. You gain safety by paying with downtime. > You usually don't pay with data loss. :-) I've used fsck when working with external hard drives, but it never dawned on me to use it for the main one. > Firefox today uses a quite complex structure of files to > store settings. Combine this with a file system inconsistency, > and you can easily end up with files that get rewritten or > reset, but are still damaged at the next program start. > In case the same inodes were used, the file would always > be somehow damaged, and even if a process of unlink() and > open() / fopen() to create it would allocate a different > inode, it's still possible that the problem was within the > parent inode - and only a proper fsck would have been able > to fix this problem. I remember that Firefox used to be shown as a single process when running top. In the last year or so, it was changed and now it uses several of them. If I want to kill FF, I have to do it to just about every one of them. How many there are seems to be related to factors such as the number of tabs or windows I might have open. I've been running the newly-installed FF for the past few hours and there hasn't been any problems yet. BMJ