Linux Btrfs filesystem development
 help / color / mirror / Atom feed
* Re: [Bug #27842] [regression?] hang with 2.6.37 on a BTRFS test machine
       [not found] ` <-tcJxClTQPH.A.Z6D.r6eSNB@chimera>
@ 2011-02-03 11:20   ` Martin Steigerwald
  2011-02-03 11:46     ` Helmut Hullen
  2011-02-03 19:05     ` Rafael J. Wysocki
  0 siblings, 2 replies; 4+ messages in thread
From: Martin Steigerwald @ 2011-02-03 11:20 UTC (permalink / raw)
  To: Rafael J. Wysocki
  Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
	Florian Mickler, linux-btrfs, Helmut Hullen

[-- Attachment #1: Type: Text/Plain, Size: 2124 bytes --]

Added linux-btrfs and Helmut Hullen, who seemed to experience hangs on a 
T23 with BTRFS as well, to Cc.

Am Thursday 03 February 2011 schrieb Rafael J. Wysocki:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.36 and 2.6.37.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.36 and 2.6.37.  Please verify if it still should
> be listed and let the tracking team know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=27842
> Subject		: [regression?] hang with 2.6.37 on a BTRFS test machine
> Submitter	: Martin Steigerwald <Martin@lichtvoll.de>
> Date		: 2011-01-23 12:06 (11 days old)
> Message-ID	: <201101231306.23069.Martin@lichtvoll.de>
> References	: http://marc.info/?l=linux-kernel&m=129578445613283&w=2

Well I now tested with 2.6.36 for more than a week and I did not see any 
of such hangs upto now. The machine seems table with 2.6.36. So I think 
its really an regression of 2.6.37.

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.

Re: [PATCH v2]Btrfs: pwrite blocked when writing from the mmaped buffer of 
the same page
http://marc.info/?l=linux-btrfs&m=129623925116051&w=2

There is another thread about 2.6.37 related BTRFS hang:

flush-btrfs-1 hangs when building openwrt
http://marc.info/?l=linux-btrfs&m=129594547616298&w=2

I will add this as comment to the bug report as well.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bug #27842] [regression?] hang with 2.6.37 on a BTRFS test machine
  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
  2011-02-03 23:21       ` Chris Samuel
  2011-02-03 19:05     ` Rafael J. Wysocki
  1 sibling, 1 reply; 4+ messages in thread
From: Helmut Hullen @ 2011-02-03 11:46 UTC (permalink / raw)
  To: linux-btrfs

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bug #27842] [regression?] hang with 2.6.37 on a BTRFS test machine
  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
@ 2011-02-03 19:05     ` Rafael J. Wysocki
  1 sibling, 0 replies; 4+ messages in thread
From: Rafael J. Wysocki @ 2011-02-03 19:05 UTC (permalink / raw)
  To: Martin Steigerwald
  Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
	Florian Mickler, linux-btrfs, Helmut Hullen

On Thursday, February 03, 2011, Martin Steigerwald wrote:
> Added linux-btrfs and Helmut Hullen, who seemed to experience hangs on a 
> T23 with BTRFS as well, to Cc.
> 
> Am Thursday 03 February 2011 schrieb Rafael J. Wysocki:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.36 and 2.6.37.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.36 and 2.6.37.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=27842
> > Subject		: [regression?] hang with 2.6.37 on a BTRFS test machine
> > Submitter	: Martin Steigerwald <Martin@lichtvoll.de>
> > Date		: 2011-01-23 12:06 (11 days old)
> > Message-ID	: <201101231306.23069.Martin@lichtvoll.de>
> > References	: http://marc.info/?l=linux-kernel&m=129578445613283&w=2
> 
> Well I now tested with 2.6.36 for more than a week and I did not see any 
> of such hangs upto now. The machine seems table with 2.6.36. So I think 
> its really an regression of 2.6.37.
> 
> 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.
> 
> Re: [PATCH v2]Btrfs: pwrite blocked when writing from the mmaped buffer of 
> the same page
> http://marc.info/?l=linux-btrfs&m=129623925116051&w=2
> 
> There is another thread about 2.6.37 related BTRFS hang:
> 
> flush-btrfs-1 hangs when building openwrt
> http://marc.info/?l=linux-btrfs&m=129594547616298&w=2
> 
> I will add this as comment to the bug report as well.

Thanks for the update.

Rafael

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bug #27842] [regression?] hang with 2.6.37 on a BTRFS test machine
  2011-02-03 11:46     ` Helmut Hullen
@ 2011-02-03 23:21       ` Chris Samuel
  0 siblings, 0 replies; 4+ messages in thread
From: Chris Samuel @ 2011-02-03 23:21 UTC (permalink / raw)
  To: linux-btrfs

On 03/02/11 22:46, Helmut Hullen wrote:

> 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.

There have been no changes in git since either, but Chris Mason
did say he was planning on sending a pull request to Linus in
the next week or so.

cheers,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-02-03 23:21 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [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
2011-02-03 23:21       ` Chris Samuel
2011-02-03 19:05     ` Rafael J. Wysocki

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox