From: Theodore Ts'o <tytso@mit.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [4.7-rc4] WARNING: CPU: 10 PID: 3359 at fs/inode.c:280 drop_nlink+0x3e/0x50
Date: Sun, 10 Jul 2016 11:25:15 -0400 [thread overview]
Message-ID: <20160710152515.GH26097@thunk.org> (raw)
In-Reply-To: <20160710001416.GA1922@dastard>
Sorry if I offended your sense of non-newbieness :-), but I didn't
know how your root file system and qemu was configured, and I did find
a potential place where a corrupted file system could lead to exact
symptoms that you reported. Hence the reason that I made the
assumption that I did.
Cheers,
- Ted
prev parent reply other threads:[~2016-07-10 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 23:46 [4.7-rc4] WARNING: CPU: 10 PID: 3359 at fs/inode.c:280 drop_nlink+0x3e/0x50 Dave Chinner
2016-07-05 4:45 ` Theodore Ts'o
2016-07-10 0:14 ` Dave Chinner
2016-07-10 15:25 ` Theodore Ts'o [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=20160710152515.GH26097@thunk.org \
--to=tytso@mit.edu \
--cc=david@fromorbit.com \
--cc=linux-ext4@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 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.