| To: | Brian Grossman <brian@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs oops |
| From: | Chris Wedgwood <cw@xxxxxxxx> |
| Date: | Sat, 8 Feb 2003 16:54:00 -0800 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <courier.3E45A297.000057A8@xxxxxxxxxxxxxxxxxx> |
| References: | <courier.3E3F5B9E.0000441C@xxxxxxxxxxxxxxxxxx> <20030204091538.A29171@xxxxxxxxxxxxx> <courier.3E4587E9.00000AD2@xxxxxxxxxxxxxxxxxx> <20030208234139.GB23898@xxxxxxxx> <courier.3E45A297.000057A8@xxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
On Sat, Feb 08, 2003 at 05:36:39PM -0700, Brian Grossman wrote: > My most recent problem was deleting three ~1.5GB files. Oops in > kswapd. I'm not sure it's rm (or the fs delete path) to blame... I create and delete 10GB+ files all the time under 2.4.x without problems. > RM in diskwait. Any further access to the filesystem diskwaited, > too. After reboot, I discovered that the third file remained. Yeah, if kswapd barfs, disk IO is pretty much hosed from there out out. > My problems are with 2.4.20. I noticed that after sending it. For me 2.4.20+ has been rock solid even when given lots of abuse. > I'll factor out nvidia in a couple days. Please try. It would be interesting to know if that helps... I use the nv module under 2.4.x and don't have problems, but that might be luck more than anything. --cw |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs oops, Brian Grossman |
|---|---|
| Next by Date: | RedHat 8.0 anf XFS Image or Kernel-Update ?, achim altmann |
| Previous by Thread: | Re: xfs oops, Brian Grossman |
| Next by Thread: | [Bug 213] XFS kernel patch breaks kdemultimedia, bugzilla-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |