From: Tomas Hlavaty <tom-3l5KtCzVe0PQT0dZR+AlfA@public.gmane.org>
To: Ryusuke Konishi
<konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-nilfs <linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-3l5KtCzVe0PQT0dZR+AlfA@public.gmane.org>
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
WARNING: multiple messages have this Message-ID (diff)
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 12:31 UTC|newest]
Thread overview: 32+ 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-17 17:34 ` Tomas Hlavaty
2019-11-18 16:51 ` Ryusuke Konishi
2019-11-19 6:04 ` Viacheslav Dubeyko
[not found] ` <76887BD9-D6C4-4A89-8F55-4BEAF2828FD3-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2020-01-23 13:00 ` Tomas Hlavaty
2020-01-23 13:00 ` Tomas Hlavaty
2019-12-19 21:02 ` Tomas Hlavaty
[not found] ` <87immckp07.fsf-3l5KtCzVe0PQT0dZR+AlfA@public.gmane.org>
2020-01-23 12:31 ` Tomas Hlavaty [this message]
2020-01-23 12:31 ` Tomas Hlavaty
[not found] ` <87v9p2tkut.fsf-3l5KtCzVe0PQT0dZR+AlfA@public.gmane.org>
2020-03-27 6:26 ` Tomas Hlavaty
2020-03-27 6:26 ` Tomas Hlavaty
2020-03-28 9:26 ` ARAI Shun-ichi
[not found] ` <20200328.182640.1933740379722138264.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
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 12:38 ` Hideki EIRAKU
[not found] ` <20200430.213842.00392641.hdk1983-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-04-30 15:27 ` Tom
2020-04-30 15:27 ` Tom
[not found] ` <ee5677b7-802b-f524-36cc-9d5ae071859b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-05-31 17:49 ` Ryusuke Konishi
2020-05-31 17:49 ` Ryusuke Konishi
[not found] ` <20200601024013.1296-1-hdanton@sina.com>
[not found] ` <20200601024013.1296-1-hdanton-k+cT0dCbe1g@public.gmane.org>
2020-06-01 11:46 ` Ryusuke Konishi
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
[not found] ` <20200123.225827.1155989593018204741.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2020-01-23 14:07 ` ARAI Shun-ichi
2020-01-23 14:30 ` ARAI Shun-ichi
2020-01-23 14:30 ` ARAI Shun-ichi
2020-02-10 13:46 ` ARAI Shun-ichi
2020-02-10 13:46 ` ARAI Shun-ichi
[not found] ` <20200210.224609.499887311281343618.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2020-02-16 2:10 ` ARAI Shun-ichi
2020-02-16 2:10 ` ARAI Shun-ichi
[not found] ` <20200216.111029.687350152614907818.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2020-02-16 2:24 ` Brian G.
2020-02-16 2:24 ` Brian G.
2020-02-16 3:59 ` Ryusuke Konishi
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-3l5ktczve0pqt0dzr+alfa@public.gmane.org \
--cc=konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.