From: Olaf Hering <olaf@aepfle.de>
To: "Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: 4.8.12, crash in ext4, __d_lookup_rcu
Date: Mon, 12 Dec 2016 16:28:37 +0100 [thread overview]
Message-ID: <20161212152837.GA3034@aepfle.de> (raw)
In-Reply-To: <20161212150359.ylhq7ocs7idqxjwv@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
On Mon, Dec 12, Theodore Ts'o wrote:
> What was going on at the time of the crash, and can you reproduce this?
Its the 'rm -rf $dir/$oldbackup.N' at the end of each rsnapshot run.
I will try to reproduce it, see if it happens again during the hourly
rsnapshot runs. So far I have not seen it with 4.8.x, cant remember if
it already happend with earlier kernels.
> There was a huge number of messages about ISO 9660 and accesses beyond
> the end of the loop device, and I wonder if any of this might have
> been connected to the crash.
This was an ISO image with download in progress. Since the download was
slow I mounted what was already available, which was enough to make the
installer happy. But a few files are located at the end of the image,
and the loopN block device does not autogrow as more data became
available. The ISOs are on another drive than the backup disk. Not sure
if such an incomplete iso9660 filesystem can confuse the vfs layer?
Olaf
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2016-12-12 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 8:57 4.8.12, crash in ext4, __d_lookup_rcu Olaf Hering
2016-12-12 9:00 ` Olaf Hering
2016-12-12 15:03 ` Theodore Ts'o
2016-12-12 15:28 ` Olaf Hering [this message]
2016-12-12 15:29 ` Olaf Hering
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=20161212152837.GA3034@aepfle.de \
--to=olaf@aepfle.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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