xfs-masters
[Top] [All Lists]

[xfs-masters] [Bug 6180] XFS oopses on my box sometimes

To: xfs-masters@xxxxxxxxxxx
Subject: [xfs-masters] [Bug 6180] XFS oopses on my box sometimes
From: bugme-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 16 Mar 2006 00:35:28 -0800
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
http://bugzilla.kernel.org/show_bug.cgi?id=6180





------- Additional Comments From avuton@xxxxxxxxx  2006-03-16 00:35 -------
|Spot on - so, thats why you're getting a panic anyway, somehow one of 
|those inodes with nlink==0 is visible through the directory hierarchy 
|and someone is accessing it; someone else takes it away at the same 
|time, and boom. 
 
|The real root of the problem though is how did the nlink field get that 
|way... this would probably have happened at some point well before your 
|panic, so we've got no real clues to go on unfortunately. :( 
 
To be quite honest I don't think I'm really doing anything unusual, unless  
suspend and resume are unusual. I did xfs_repair this mount before and it did  
happen again afterwards. I'm fairly sure it started after 2.6.15, of course I  
could be mistaken. One thing I can say is there's nothing that really  
_reproduces_ it afaict. I have had it happen during an emerge, have had it  
happening after just comeing back to the computer to use it in the middle of an 
 
x session with nothing else happening.   
  
Simply put I can name most of the normal stuff that runs on this computer.  
Apache2, xdm, fvwm2, konqueror, kate (editor), jasspa microemacs, emerge.  
That's the most used programs. I have had it happen during high cpu usage and  
had it happen alot during no cpu usage.  
  
I don't suppose you have anything to take out the metadata, so you can research 
 
it? reiser4 has a program like this iirc.  
  
My netconsole isn't hooked up correctly atm, so I'm going to reconfigure that,  
rebuild a newer git and see if I can get you a newer dump. This one will be  
with GCC-4.1, if that'll help you any. If you can think of anything I can do to 
 
help please let me know.  
 
If you want I can also try going back to 2.6.15 run it for a week see what 
happens. 
 
Any ideas of where to go from here? 
 

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


<Prev in Thread] Current Thread [Next in Thread>