From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Nathan Royce <nroycea+kernel@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] F2FS Segmentation Fault
Date: Mon, 13 Jul 2020 17:03:47 -0700 [thread overview]
Message-ID: <20200714000347.GA19314@google.com> (raw)
In-Reply-To: <CALaQ_hosk7627nTx97+xSSsGiN-qt=pTGNW4DZn4TOcAeRSC8g@mail.gmail.com>
Hi Nathan,
On 07/13, Nathan Royce wrote:
> I won't re-format unless I hear something within a few days in case
> you want me to try something.
>
> Preface: There was a notable power outage a couple of nights ago.
> When the power returned, everything seemed fine. No issues during
> bootup or anything.
> Then today, I went to open an application and my system started
> schitzing out with programs suddenly closing(/crashing?).
> I switched tty and tried to log in but was unable to even be allowed
> to enter in my password.
> I switched to another and tried logging in as root which succeeded (somehow).
> I looked at the journal and saw an entry saying something about
> /bin/login not being a valid exec format.
> I went to reboot and when it got to fsck part of initramfs, it failed
> and I was kicked to root.
> I ran fsck and saw a bunch of issues, but I guess nothing could get
> resolved enough to let me reboot.
> Oh, in case you're wondering, my / (system) is on a 64GB SDHC card.
> I just happened to also have an older / system on my mechanical drive
> using BTRFS which I could boot to (which I'm on now).
> I ran fsck from this older system and it seems I got the same results:
>
> *****
> Info: Fix the reported corruption.
> Info: Force to fix corruption
> Info: Segments per section = 1
> Info: Sections per zone = 1
> Info: sector size = 512
> Info: total sectors = 124168159 (60628 MB)
> Info: MKFS version
> "Linux version 5.1.15.a-1-hardened (builduser@slave-1) (gcc version
> 9.1.0 (GCC)) #1 SMP PREEMPT Thu Jun 27 11:33:04 CEST 2019"
> Info: FSCK version
> from "Linux version 4.19.13-dirty (userName@computerName) (gcc
> version 8.2.1 20181127 (GCC)) #2 SMP PREEMPT Mon Dec 31 00:15:50 CST
> 2018"
> to "Linux version 4.19.13-dirty (userName@computerName) (gcc
> version 8.2.1 20181127 (GCC)) #2 SMP PREEMPT Mon Dec 31 00:15:50 CST
> 2018"
> Info: superblock features = 0 :
> Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
> Info: total FS sectors = 124168152 (60628 MB)
> Info: CKPT version = 63f2b4a
> Info: checkpoint state = 55 : crc fsck compacted_summary unmount
>
> NID[0x18eca] is unreachable, blkaddr:0xcf1d9d3c
> NID[0x18ecb] is unreachable, blkaddr:0x5db5f91f
> NID[0x18ecc] is unreachable, blkaddr:0x4653d
> NID[0x18ee3] is unreachable, blkaddr:0x144dc401
> NID[0x18ee4] is unreachable, blkaddr:0x558cfba9
> NID[0x18ee5] is unreachable, blkaddr:0x45553
> NID[0x18f78] is unreachable, blkaddr:0x560555ac
> NID[0x18f79] is unreachable, blkaddr:0x58cccb0d
> NID[0x18f7a] is unreachable, blkaddr:0x53d84
> NID[0x4d621] is unreachable, blkaddr:0x4fc1d
> NID[0x4d622] is unreachable, blkaddr:0x4fc1e
> NID[0x7fa32] is unreachable, blkaddr:0x20b0ca3a
> NID[0x7fa33] is unreachable, blkaddr:0xf71b60
> [FSCK] Unreachable nat entries [Fail] [0xd]
> [FSCK] SIT valid block bitmap checking [Fail]
> [FSCK] Hard link checking for regular file [Ok..] [0x4f6]
> [FSCK] valid_block_count matching with CP [Fail] [0x736fcb]
> [FSCK] valid_node_count matcing with CP (de lookup) [Fail] [0x70327]
> [FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x70334]
> [FSCK] valid_inode_count matched with CP [Fail] [0x6f09e]
> [FSCK] free segment_count matched with CP [Ok..] [0x3bfc]
> [FSCK] next block offset is free [Ok..]
> [FSCK] fixing SIT types
> [FSCK] other corrupted bugs [Fail]
>
> Do you want to restore lost files into ./lost_found/? [Y/N] Y
Could you try to say "N" here to move forward to fix the corrupted metadata?
Thanks,
> Segmentation fault
> *****
>
> *****
> Message: Process 3425 (fsck.f2fs) of user 0 dumped core.
>
> Stack trace of thread 3425:
> #0 0x000055f8515739c8 n/a (fsck.f2fs)
> #1 0x000055f851575261 n/a (fsck.f2fs)
> #2 0x000055f851572c56 n/a (fsck.f2fs)
> #3 0x000055f85156a3f0 n/a (fsck.f2fs)
> #4 0x00007f51420feee3 __libc_start_main (libc.so.6)
> #5 0x000055f85156a95e n/a (fsck.f2fs)
> *****
>
> So if you want more information or need me to try something, let me
> know soon if you would. Otherwise, I'll just be reformatting my card
> in a few days.
> It just could've been a fluke occurred because of the power outage but
> didn't manifest itself until today.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-07-14 0:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 22:24 [f2fs-dev] F2FS Segmentation Fault Nathan Royce
2020-07-14 0:03 ` Jaegeuk Kim [this message]
2020-07-14 2:24 ` Nathan Royce
2020-07-14 5:54 ` Jaegeuk Kim
2021-03-27 12:02 ` Nathan Royce
2021-03-27 12:41 ` Nathan Royce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200714000347.GA19314@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nroycea+kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).