From: Tomas Hlavaty <tom@logand.com>
To: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8 in nilfs_segctor_do_construct
Date: Thu, 23 Jan 2020 13:31:38 +0100 [thread overview]
Message-ID: <87v9p2tkut.fsf@logand.com> (raw)
In-Reply-To: <87immckp07.fsf@logand.com>
Hi Ryusuke,
>> 2) Can you mount the corrupted(?) partition from a recent version of
>> kernel ?
this will take me some time to figure out
>> 3) Does read-only mount option (-r) work to avoid the crash ?
ro mount doesn't seem to crash
at least after mounting the partition read-only
- running lscp
- running sudo find . -type f inside the mounted partition
- cat <some random file on the nilfs partition>
does not crash
the crash i was seeing was during rsync (writing i guess)
Other info that might be relevant:
- the nilfs partition was on top of luks
- the corruption happened probably during shutdown
the shutdown hanged for a long time waiting for nilfs
disk (iirc it waits for 1m30s) and even after that it did
not finish so i turned the computer off without waiting
further. after new start, i got the crash
- i got the same problem on another disk recently
Regards,
Tomas
next prev parent reply other threads:[~2020-01-23 13:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 17:34 BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8 in nilfs_segctor_do_construct Tomas Hlavaty
2019-11-18 16:51 ` Ryusuke Konishi
2019-11-19 6:04 ` Viacheslav Dubeyko
2020-01-23 13:00 ` Tomas Hlavaty
2019-12-19 21:02 ` Tomas Hlavaty
2020-01-23 12:31 ` Tomas Hlavaty [this message]
2020-03-27 6:26 ` Tomas Hlavaty
[not found] ` <CAKFNMomjWkNvHvHkEp=Jv_BiGPNj=oLEChyoXX1yCj5xctAkMA@mail.gmail.com>
2020-03-28 9:26 ` ARAI Shun-ichi
2020-04-30 12:38 ` BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8 in nilfs_segctor_do_co Hideki EIRAKU
2020-04-30 15:27 ` Tom
2020-05-31 17:49 ` Ryusuke Konishi
[not found] ` <20200601024013.1296-1-hdanton@sina.com>
2020-06-01 11:46 ` Ryusuke Konishi
2020-01-23 13:58 ` BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8 in nilfs_segctor_do_construct ARAI Shun-ichi
2020-01-23 14:30 ` ARAI Shun-ichi
2020-02-10 13:46 ` ARAI Shun-ichi
2020-02-16 2:10 ` ARAI Shun-ichi
2020-02-16 2:24 ` Brian G.
2020-02-16 3:59 ` Ryusuke Konishi
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=87v9p2tkut.fsf@logand.com \
--to=tom@logand.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@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).