Bug 236482 - Sorry, I can still deadlock gfs2 :(
Sorry, I can still deadlock gfs2 :(
Product: Fedora
Classification: Fedora
Component: GFS (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Steve Whitehouse
Depends On:
  Show dependency treegraph
Reported: 2007-04-14 19:07 EDT by Gary Lindstrom
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version: 2.6.21-1.3208
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-30 04:59:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
messages file with backtrace from spool7 (287.30 KB, application/octet-stream)
2007-04-14 19:07 EDT, Gary Lindstrom
no flags Details
messages file with backtrace from spool8 (311.53 KB, application/octet-stream)
2007-04-14 19:08 EDT, Gary Lindstrom
no flags Details
messages file with backtrace from virtual1b (288.13 KB, application/octet-stream)
2007-04-14 19:09 EDT, Gary Lindstrom
no flags Details

  None (edit)
Description Gary Lindstrom 2007-04-14 19:07:45 EDT
Well, I'll open another bug report since 221729 was closed.  Maybe this is a
different problem than the last deadlocks...???

Steve, like I said in another report, your gonna hate me.  Been busy and hadn't
tried recently, but I got some time this weekend to try this again, and I can
still deadlock gfs2.  Upgraded all 3 machines in cluster to latest kernel and
updates.  Kernel is: 2.6.20-1.2944.fc6.

I am attaching 3 backtraces, one from each machine in the cluster.  I had a copy
from an ext3 to gfs2 partition running on spool7, a copy from an ocfs to the
same gfs2 partition (to a different directory structure), and ran a 'df' command
on virtual1b.  All 3 machines were deadlocked after a few minutes.  Not positive
but I think it deadlocked on spool8 first...

Sorry.... :(  If you need more info, let me know.
Comment 1 Gary Lindstrom 2007-04-14 19:07:46 EDT
Created attachment 152632 [details]
messages file with backtrace from spool7
Comment 2 Gary Lindstrom 2007-04-14 19:08:55 EDT
Created attachment 152633 [details]
messages file with backtrace from spool8
Comment 3 Gary Lindstrom 2007-04-14 19:09:34 EDT
Created attachment 152634 [details]
messages file with backtrace from virtual1b
Comment 4 Gary Lindstrom 2007-04-14 19:12:53 EDT
Ummm... let me ammend the first comment...  I did a directory list on virtual1b
that hung, not a df command...
Comment 6 Ben Marzinski 2007-05-07 20:08:46 EDT
This looks just like bz #231910, which has a fix. However, 231910 is a RHEL bug.
I'm not sure how Steve is handling bugs with respect to the differences between
RHEL and fedora.  If he needs a fedora version on that bug for tracking
purposes, then one this will do fine. But at any rate, there is a solution to
this problem with will make it upstream shortly.
Comment 7 Robert Peterson 2007-05-08 17:53:18 EDT
Looks like this is a Fedora build issue then.  Reassigning to Chris Feist.
Comment 8 Chris Feist 2007-05-08 18:00:59 EDT
Re-assigning to Steve Whitehouse as he provides kernel patches for the fedora
Comment 9 Steve Whitehouse 2007-05-09 04:03:02 EDT
I'll try and sort this out now that the latest upstream patches have been
accepted by Linus.
Comment 10 Steve Whitehouse 2007-05-11 07:08:33 EDT
The patches have now been sent for both FC5/6 and FC7 so I'm just waiting to
find out which version of the kernel RPM they'll appear in.
Comment 11 Steve Whitehouse 2007-05-30 04:59:52 EDT
Still waiting on FC5/6, but its in FC7 (pre-release) now and also in the current
rawhide devel kernel. Also fixed upstream.
Comment 12 Steve Whitehouse 2007-05-30 10:11:46 EDT
For FC5/6 that will be kernel 2952 which is commited but will be built shortly

Note You need to log in before you can comment on or make changes to this bug.