From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 13037] reiserfs panic (device null superblock)
Date: Sat, 8 May 2010 22:12:29 GMT [thread overview]
Message-ID: <201005082212.o48MCTSm004332@demeter.kernel.org> (raw)
In-Reply-To: <bug-13037-695@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=13037
Christian Kujau <lists@nerdbynature.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lists@nerdbynature.de
--- Comment #10 from Christian Kujau <lists@nerdbynature.de> 2010-05-08 22:12:25 ---
A clean testcase would be nice. I tested 2.6.34-rc6 with reiserfs and an
external log; copied 11000000 files around, copied 2 kernel trees around - no
panic. It's a multicore machine too, but no DRBD or NFS involved.
If these variables make a difference, please describe your (exact) setup so
that one can try to reproduce this.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-05-08 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13037-695@https.bugzilla.kernel.org/>
2010-05-07 15:47 ` [Bug 13037] reiserfs panic (device null superblock) bugzilla-daemon
2010-05-08 22:12 ` bugzilla-daemon [this message]
2012-05-30 15:16 ` bugzilla-daemon
2013-11-20 13:21 ` bugzilla-daemon
[not found] <bug-13037-695@http.bugzilla.kernel.org/>
2009-06-30 12:20 ` bugzilla-daemon
2009-07-02 15:00 ` bugzilla-daemon
2009-07-02 17:34 ` bugzilla-daemon
2009-07-02 18:44 ` bugzilla-daemon
2009-09-18 16:16 ` bugzilla-daemon
2009-09-23 16:39 ` 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=201005082212.o48MCTSm004332@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=reiserfs-devel@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.