From owner-freebsd-fs@freebsd.org Wed Jun 3 22:54:27 2020 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C9AA42F56E5 for ; Wed, 3 Jun 2020 22:54:27 +0000 (UTC) (envelope-from jdelisle@gmail.com) Received: from mail-il1-x141.google.com (mail-il1-x141.google.com [IPv6:2607:f8b0:4864:20::141]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49ckkB37ZVz3xwB for ; Wed, 3 Jun 2020 22:54:26 +0000 (UTC) (envelope-from jdelisle@gmail.com) Received: by mail-il1-x141.google.com with SMTP id p5so4222762ile.6 for ; Wed, 03 Jun 2020 15:54:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=l7brOPywC/A5nMRGp2CSe+KI9hEM/C4rRslLesAii+k=; b=H8GcymKJWs4q1AwNx01hNMCJ6Ko5WFWNVKITpRgprhBnYi6ybWYLohOpA6VpCMO2Fw xHyRQiDOuRjYZHiN8a81zlxRfbLbCL2OEcQFzzGbT1L/KSg0PZFImDy9CbiB7Fq7InSX 0OPmzQ5FguAKcxPoCEO1POdXNJ6kC+PzPvAxGHbTAlMU51xU3162gAnsHEFsT3N4mITC RgesFqr6n2D9O+NhdnVVvKdpCfettqfXcVtpucv9lkCZcciEOrTBhjzl0ABfgcJAUpB8 kEztHMYGqIm3w9Kw1y43Pcx7Tsst77s7xPYWg7pk3GSNdLqf3CO6/Qbvjx4bT2HPf7rT slrw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=l7brOPywC/A5nMRGp2CSe+KI9hEM/C4rRslLesAii+k=; b=DhL3SgJWVNqzwWhODOZD7ESIYlrwRFj7tTwZILJsAhTAJNxvYQkWGHkUvXHNXNdxsV dpPlC25FU1hCem8DGzS2NnK6Qdyenb0qtkyVl7NP8zSQ27B++xPxm/t0vBXQAn6xFPMt 1KCYymEaeZhjBQr1as34qg73magmgTDPdBynxpJSPsZRS7ueaXBBeBL6Y/MFw1l6+/nr EPg9p+s/TAx4QzhJwoWtjskNi7EnUey6/05BNjk3qFJPgTOwUp3MQ77wlEZriNSfVOTa l2EBKDUrLlp2z7YnpY5PTg1msMMZul6wHauGNtrkp4qSy25xKbmk4LkDhsNXTXj7LpG3 BOvw== X-Gm-Message-State: AOAM5315rRf/gKm+AKkW8rJIeBbcLuQwSofuC/gMKaRVo5J5cai5pr/1 l2bsQRY2elFFnLvL8Bakj8mhInapOT1BJZky+vmdDppA X-Google-Smtp-Source: ABdhPJxTHBL6qeqsTNEntnWkzX4WK4QRgr3ZgzAcdTakL5T5kaBCBZh2HVggNBm67S6Atgy10IRAc0Pa0rA6btZDU/M= X-Received: by 2002:a92:bacb:: with SMTP id t72mr1734511ill.26.1591224865317; Wed, 03 Jun 2020 15:54:25 -0700 (PDT) MIME-Version: 1.0 References: <2b976212-4c83-b528-3db6-aa8f5be4db4f@national.shitposting.agency> In-Reply-To: From: jdelisle Date: Wed, 3 Jun 2020 17:54:13 -0500 Message-ID: Subject: Re: fsck this shit To: Jan Bramkamp Cc: freebsd-fs X-Rspamd-Queue-Id: 49ckkB37ZVz3xwB X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=H8GcymKJ; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of jdelisle@gmail.com designates 2607:f8b0:4864:20::141 as permitted sender) smtp.mailfrom=jdelisle@gmail.com X-Spamd-Result: default: False [-2.97 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.013]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; NEURAL_HAM_LONG(-1.05)[-1.050]; NEURAL_SPAM_SHORT(0.09)[0.093]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::141:from]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2020 22:54:27 -0000 Nothing like making a good first-impression, right? On Wed, Jun 3, 2020 at 3:22 PM Jan Bramkamp wrote: > > On 03.06.20 22:18, Thomas Mueller wrote: > > from goatshit54108@national.shitposting.agency: > > > >> Once upon a time, the power ran out, and then... > >> ** SU+J Recovering /dev/<...> > >> ** Reading 33554432 byte journal from inode 4. > >> ** Building recovery table. > >> ** Resolving unreferenced inode list. > >> ** Processing journal entries. > >> fsck: /dev/<...>: Segmentation fault > > GAAAY. > > > >> OK, let's check the core dump... oh, wait... tough luck. Fortunately, > subsequent runs of fsck ended up likewise, so I was able to get a core dump > by re-executing fsck while being inside a TMPFS-backed directory. (On the > other hand, unfortunately, fsck was never able to replay the journal.) > Furthermore, I saved the .sujournal file, but saving the contents of the > whole filesystem was beyond my resources. (It would have been adequate to > use a tool that collected (only) the blocks that fsck read before > segfaulting (thus constructing a small test case), but no such tool was at > hand.) > >> Before running "fsck -y" (because I had no other options) I looked at > "fsck -n" to see whether a particular, large file would get idiotically > removed as part of "fixing" the filesystem. This routine is prompted by (1) > personal experiences of files getting lost or truncated to 0 length, and > (2) past reports of disasterous behaviors involving soft updates, such as > untouched (read-only) files getting lost; "lost" means not even relinked to > /lost+found or anything. And wouldn't ya know it, fsck did ask whether to > remove something that had an unambiguously large size (to be exact, IIRC: > "DUP ... REMOVE?", whatever that means). That's it, either (a) remove the > file, or (b) stay dirty; take it or leave it. It's not like there was some > 3rd option to relink the file to /lost+found. After "fsck -y", the file > disappeared without a trace. GAAAAAAAAAY. > > > >> The fsck_ffs (or fsck_ufs) file was the one distributed with the > 12.1-RELEASE, the one with the SHA3-256 checksum of > 447592ae05dc7829823901700bb90940968cae006719964d39b1212bb312d164. Let's see > the backtrace: > >> * thread #1, name = 'fsck_ufs', stop reason = signal SIGSEGV > >> * frame #0: 0x0000000000219d93 fsck_ffs`blk_free(bno=10692928, > mask=0, frags=134643471) at suj.c:653:34 > >> frame #1: 0x000000000021a481 fsck_ffs`ino_trunc(ino=5296913, > size=134610944) at suj.c:1547:3 > >> frame #2: 0x0000000000216fee fsck_ffs`suj_check [inlined] > cg_adj_blk(sc=0x0000000801574540) at suj.c:1788:5 > >> frame #3: 0x0000000000216fc3 fsck_ffs`suj_check [inlined] > cg_apply at suj.c:1900 > >> frame #4: 0x0000000000216fa5 > fsck_ffs`suj_check(filesys="/dev/<...>") at suj.c:2737 > >> frame #5: 0x000000000020ef54 fsck_ffs`main [inlined] > checkfilesys(filesys="/dev/<...>") at main.c:427:9 > >> frame #6: 0x000000000020ef07 fsck_ffs`main(argc=1, > argv=0x00007fffffffec48) at main.c:205 > >> frame #7: 0x000000000020810f fsck_ffs`_start(ap=, > cleanup=) at crt1.c:76:7 > >> Some analysis: > > (snip) > > > > I have had times when fsck_ffs from FreeBSD didn't succeed, but fsck_ffs > from NetBSD did succeed. That was on a FreeBSD installation, but I also > had/have NetBSD installed. > > > > I use GPT with no traditional BSD disklabels, so FreeBSD and NetBSD can > read and write each other's partitions. > > > > I ran "host national.shitposting.agency", and got > > > > national.shitposting.agency has address 52.11.159.5 > > national.shitposting.agency mail is handled by 20 mx2.cock.li. > > national.shitposting.agency mail is handled by 10 mx1.cock.li. > > > > so the domain really exists. > Yes as you can see in the MX records its run by a bunch of well known > racists and faschists who also brought us nice domains like > hitler.rocks, nigge.rs. nuke.africa and rape.lol. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >