From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 13201] kernel BUG at fs/ext4/extents.c:2737
Date: Wed, 29 Apr 2009 03:15:34 GMT [thread overview]
Message-ID: <200904290315.n3T3FYbe015926@demeter.kernel.org> (raw)
In-Reply-To: <bug-13201-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13201
Eric Sandeen <sandeen@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@redhat.com
--- Comment #3 from Eric Sandeen <sandeen@redhat.com> 2009-04-29 03:15:31 ---
Franco, sorry we haven't gotten back with suggestions on this. It looks like
you have hit a couple different end results. We've had a few reports of
corruption on larger filesystems which makes us wonder if there might be a
problem above 8T somewhere...
The current upstream git tree (or the 2.6.30-rc3-git5 prepatch) has more extent
validity checking in it; if you do have the time for another test, running on
that codebase may yield more info, depending on where the problem lies.
-Eric
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-04-29 3:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 9:28 [Bug 13201] New: kernel BUG at fs/ext4/extents.c:2737 bugzilla-daemon
2009-04-29 1:06 ` [Bug 13201] " bugzilla-daemon
2009-04-29 3:15 ` bugzilla-daemon [this message]
2009-04-30 3:00 ` bugzilla-daemon
2009-04-30 9:39 ` bugzilla-daemon
2009-05-19 18:04 ` bugzilla-daemon
2009-05-23 10:10 ` bugzilla-daemon
2009-06-05 0:51 ` bugzilla-daemon
2009-06-08 16:49 ` bugzilla-daemon
2009-06-09 5:10 ` bugzilla-daemon
2009-08-26 18:11 ` bugzilla-daemon
[not found] <bug-13201-13602@https.bugzilla.kernel.org/>
2012-05-30 16:30 ` bugzilla-daemon
2012-05-30 16:30 ` 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=200904290315.n3T3FYbe015926@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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.