From: Laurent CARON <lcaron@lncsa.com>
To: Hannes Dorbath <light@theendofthetunnel.de>
Cc: linux-kernel@vger.kernel.org, drbd-user@linbit.com
Subject: Re: [DRBD-user] Crash on 2.6.22
Date: Fri, 28 Sep 2007 11:12:23 +0200 [thread overview]
Message-ID: <46FCC577.30108@lncsa.com> (raw)
In-Reply-To: <46FCC3E4.7030908@theendofthetunnel.de>
Hannes Dorbath wrote:
> On 28.09.2007 11:00, Laurent CARON wrote:
>> The $HOME directories are stored on a drbd (version: 0.7.24
>> (api:79/proto:74)) partition (with an XFS filesystem).
>
> Was the deadlock with 2.6.22 only in 0.8.x? Is 0.7.x fine with 2.6.22?
I only experienced it with 2.6.22.
Since I pulled the latest svn tree of drbd 0.7.X, it should be pretty
deadlock safe.
Isn't it ?
Laurent
next prev parent reply other threads:[~2007-09-28 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 9:00 Crash on 2.6.22 Laurent CARON
2007-09-28 9:05 ` [DRBD-user] " Hannes Dorbath
2007-09-28 9:12 ` Laurent CARON [this message]
2007-09-28 9:21 ` Stefan Seifert
2007-09-28 9:25 ` Laurent CARON
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=46FCC577.30108@lncsa.com \
--to=lcaron@lncsa.com \
--cc=drbd-user@linbit.com \
--cc=light@theendofthetunnel.de \
--cc=linux-kernel@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