From: Nathan Royce <nroycea+kernel@gmail.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] F2FS Segmentation Fault
Date: Sat, 27 Mar 2021 07:41:09 -0500 [thread overview]
Message-ID: <CALaQ_hq+Cxt7BhcEAMWXFwaOGVtVs6+kOZqoYPvze7ee-USY9A@mail.gmail.com> (raw)
In-Reply-To: <CALaQ_hoviFQeBXODari+gzbBNkHCJk0u9Hqa3EzHksscrhKj1A@mail.gmail.com>
I don't know how much of it was the issue, but when I unmounted the
sd-card, and closed the cryptsetup for it, and then ran
non-destructive badblocks on it, I was getting ONLY errors.
I stopped bb, then pulled out the card, blew on it, wiped down the
contacts with rubbing alcohol, let it dry, put it back in and now bb
is running cleanly.
I then stopped bb, tried to cryptsetup-open it and it said the
partition is not a valid LUKS device.
Weird since I was using non-destructive.
Looks like I'm now forced to rebuild that partition.
I wish I had troubleshot the aspect of the sd-card being properly
seated. I know I've experienced something similar to it in the past
where files suddenly aren't able to be read. Once I reseat the
sd-card, everything was fine.
The last time I had to even remove the card was maybe 1-2 weeks ago
when I had to deal with a noisy power-supply fan.
The whole debacle (including btrfs, keyboard leds blinking) may very
well have been from the sd-card not being seated well.
On Sat, Mar 27, 2021 at 7:02 AM Nathan Royce <nroycea+kernel@gmail.com> wrote:
>
> An update, not quite 1 year later. I encountered another segfault issue.
>
> It began with my email report to the linux-btrfs mailing list titled
> "BTRFS Balance Hard System Crash (Blinking LEDs)" just the other day.
...
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2021-03-27 12:41 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
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 [this message]
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=CALaQ_hq+Cxt7BhcEAMWXFwaOGVtVs6+kOZqoYPvze7ee-USY9A@mail.gmail.com \
--to=nroycea+kernel@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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).