From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 13037] reiserfs panic (device null superblock)
Date: Wed, 30 May 2012 15:16:29 +0000 (UTC) [thread overview]
Message-ID: <20120530151629.410E111FD1C@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-13037-695@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=13037
Alan <alan@lxorguk.ukuu.org.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alan@lxorguk.ukuu.org.uk
Kernel Version|2.6.28.9 |2.6.34
--- Comment #11 from Pawel Zawora <pzawora@gmail.com> 2010-05-10 10:19:58 ---
I can confirm that:
1. reiser over local hard disk works stable,
2. is possible to reproduce problem using internal journaling.
Problem appears in that case:
NFS(v3) ---> resier ----> storage "depends on network" (DRBD/iSCSI).
My environment:
multiple (4+) nfs clients(noacl,udp) [multiple simultaneous file access on the
same time] uses failover nfs server . NFS works over DRBD (active/passive ;
async protocol). DRBD uses dedicated network connection. "panic time" is depend
on load.
NFS server works stable with kernel <= 2.6.25 and new kernel with ie XFS
(always over DRBD)
Additonally, on the same cluster - when I try switch nodes - stopping nfsd
causes bug reported as 14055.
--
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:[~2012-05-30 15:16 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
2012-05-30 15:16 ` bugzilla-daemon [this message]
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=20120530151629.410E111FD1C@bugzilla.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.