xfs-masters
[Top] [All Lists]

[xfs-masters] [Bug 2936] XFS internal error xfs_alloc_read_agf

To: xfs-masters@xxxxxxxxxxx
Subject: [xfs-masters] [Bug 2936] XFS internal error xfs_alloc_read_agf
From: bugme-daemon@xxxxxxxx
Date: Thu, 8 Jul 2004 15:44:18 -0700
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
http://bugme.osdl.org/show_bug.cgi?id=2936





------- Additional Comments From leonardo@xxxxxxxxxxxxxxxxxxxxx  2004-07-08 
15:44 -------
Hallo, 
  im sorry about time to response, but i solving anothers linux problem in 
another city. 
 
 Well, the problem occurs again, i try to identify what happen but the only 
thing i got is the lasts messages 
... xfs_alloc_read_agf+0xd7/0x1d1  
. 
... sysenter_past_esp+0x52/0x71  
this part repeat "forever" with same sequence and content every time a program 
try to access filesistem. 
  I forgot, but the kernel version is, now , 2.6.7. 
 
the image can be downloaded from 
 
http://www.ambientebrasil.com.br/download/xfs_bug.img.bz2 
 
( *64M* bytes of bzip2 image) 
 
 I dont know much about kernel (a guru of course), but a think the xfs messages 
are a small bug in "readfunctions" when trying to read a already damaged 
filesystem caused by "any bad writefunction". This write mistake is not 
reported,but only the wrong read access, and the system not realy freeze, only 
is putted in readonly mode. 
 
 I think if is a good choice to put debug in xfs in kernel compilation, its 
help? What i can do to trap mode messages as possible? I can try more time to 
debug is the "crash"  happens again. 
 
 
 
 
 
 
 
 

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