| To: | Steven Dake <sdake@xxxxxxxxxx> |
|---|---|
| Subject: | Re: Need some help with cause of Oops in XFS 1.2 |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 25 Mar 2003 20:54:29 +0000 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <3E80BCF2.5090005@mvista.com>; from sdake@mvista.com on Tue, Mar 25, 2003 at 01:32:50PM -0700 |
| References: | <3E809EB1.6000904@mvista.com> <20030325193838.A6142@infradead.org> <3E80B9C9.5090107@mvista.com> <20030325203229.A6850@infradead.org> <3E80BCF2.5090005@mvista.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5.1i |
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, Steven Dake |
|---|---|
| Next by Date: | Re: Need some help with cause of Oops in XFS 1.2, Steven Dake |
| Previous by Thread: | Re: Need some help with cause of Oops in XFS 1.2, Steven Dake |
| Next by Thread: | Re: Need some help with cause of Oops in XFS 1.2, Steven Dake |
| Indexes: | [Date] [Thread] [Top] [All Lists] |