| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Need some help with cause of Oops in XFS 1.2 |
| From: | Steven Dake <sdake@xxxxxxxxxx> |
| Date: | Tue, 25 Mar 2003 14:02:28 -0700 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20030325205429.A7098@xxxxxxxxxxxxx> |
| References: | <3E809EB1.6000904@xxxxxxxxxx> <20030325193838.A6142@xxxxxxxxxxxxx> <3E80B9C9.5090107@xxxxxxxxxx> <20030325203229.A6850@xxxxxxxxxxxxx> <3E80BCF2.5090005@xxxxxxxxxx> <20030325205429.A7098@xxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 |
I understand filesystem code quite well, and the particular problem (if
you would have read the oops) is in the memory management layer. But
thanks for your advice.
-steve Christoph Hellwig wrote: On Tue, Mar 25, 2003 at 01:32:50PM -0700, Steven Dake wrote:I suspect the issue wouldn't present itself with a vanilla 2.4.18 + xfs1.2 tree as it would have already been caught... And unfortunately I can't apply to a plain vanilla tree, it must go into this particular tree for my company to release it...If you have any suggestions on how I could debug, I'd be willing to try them out.I was really hoping someone had run into this type of problem in the past and could provide some quick pointers on how I could debug.Maybe get some consultant that knows Linux filesystem code to fix it for your company? I wouldn't expect too much help on a heavily patched tree that's not publically available. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Need some help with cause of Oops in XFS 1.2, Christoph Hellwig |
|---|---|
| Next by Date: | [Bug 230] umount hangs after high disk load, bugzilla-daemon |
| Previous by Thread: | Re: Need some help with cause of Oops in XFS 1.2, Christoph Hellwig |
| Next by Thread: | Re: Need some help with cause of Oops in XFS 1.2, Rusell Cattelan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |