Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: [Bug #27842] [regression?] hang with 2.6.37 on a BTRFS test machine
Date: 03 Feb 2011 12:46:00 +0100	[thread overview]
Message-ID: <BfAAZL8T1uB@helmut.hullen.de> (raw)
In-Reply-To: <201102031220.46250.Martin@lichtvoll.de>

Hallo, Martin,

Du meintest am 03.02.11:

[...]

> I am stuck with what to try next. Since trying to track it down to a
> specific commit appears too involved for me and its appears also
> quite laborious to get any value debug information out of the kernel
> - cause it can take days for the bug to appear -, I am inclined to
> either test with 2.6.37.1 once its available or just give it a go
> with 2.6.38-rc3 or rc4. Maybe 2.6.38-rc3/4 would be the best bet, I
> have seen a report on the btrfs mailing list of 2.6.38 fixing a BTRFS
> hang bug that appeared with 2.6.37. I am just not sure whether its
> related or not.

I've just checked the 2.6.38-rc[1-3] ChangeLog. Only rc1 (18.1.2011) has  
included many btrfs changes, neither rc2 nor rc3 includes any btrfs  
change.

Viele Gruesse!
Helmut

  reply	other threads:[~2011-02-03 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e9vOd5LzdBK.A.dyD.h6eSNB@chimera>
     [not found] ` <-tcJxClTQPH.A.Z6D.r6eSNB@chimera>
2011-02-03 11:20   ` [Bug #27842] [regression?] hang with 2.6.37 on a BTRFS test machine Martin Steigerwald
2011-02-03 11:46     ` Helmut Hullen [this message]
2011-02-03 23:21       ` Chris Samuel
2011-02-03 19:05     ` Rafael J. Wysocki

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=BfAAZL8T1uB@helmut.hullen.de \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.de \
    --cc=linux-btrfs@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