From: James Bottomley <James.Bottomley@suse.de>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: [Bug 16275] Kernel panic when mounting filesystem
Date: Wed, 21 Jul 2010 13:43:41 -0700 [thread overview]
Message-ID: <1279745021.20250.44.camel@mulgrave.site> (raw)
In-Reply-To: <201007200957.o6K9vaXx014277@demeter.kernel.org>
On Tue, 2010-07-20 at 09:57 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> --- Comment #9 from Pawel Staszewski <pstaszewski@artcom.pl> 2010-07-20 09:57:34 ---
> Created an attachment (id=27167)
> --> (https://bugzilla.kernel.org/attachment.cgi?id=27167)
> Panic first screen
Well, this validates the guess that it's the zero segment check, thanks!
so it's clearly a filesystem bug.
Which filesystem is this? I tried looking for the 'Checking internal
tree' message, but couldn't find it in the sources.
James
next prev parent reply other threads:[~2010-07-21 20:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16275-11613@https.bugzilla.kernel.org/>
2010-06-23 7:20 ` [Bug 16275] Kernel panic when mounting filesystem bugzilla-daemon
2010-06-23 7:26 ` bugzilla-daemon
2010-06-23 7:35 ` bugzilla-daemon
2010-06-25 8:13 ` bugzilla-daemon
2010-06-27 21:06 ` James Bottomley
2010-06-27 21:07 ` bugzilla-daemon
2010-07-05 16:02 ` bugzilla-daemon
2010-07-20 9:56 ` bugzilla-daemon
2010-07-20 9:57 ` bugzilla-daemon
2010-07-21 20:43 ` James Bottomley [this message]
2010-07-20 9:58 ` bugzilla-daemon
2010-07-21 9:02 ` bugzilla-daemon
2010-07-21 20:09 ` bugzilla-daemon
2010-07-21 20:44 ` bugzilla-daemon
2010-07-22 3:09 ` bugzilla-daemon
2010-07-22 6:41 ` bugzilla-daemon
2010-07-22 8:22 ` bugzilla-daemon
2010-07-22 8:37 ` bugzilla-daemon
2010-07-23 19:21 ` bugzilla-daemon
2010-07-24 10:20 ` bugzilla-daemon
2010-07-26 14:44 ` bugzilla-daemon
2010-07-26 14:45 ` bugzilla-daemon
2010-07-26 14:54 ` bugzilla-daemon
2010-08-03 10:29 ` bugzilla-daemon
2010-08-03 11:59 ` bugzilla-daemon
2012-08-09 14:00 ` bugzilla-daemon
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=1279745021.20250.44.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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).