| To: | Nathan Scott <nathans@xxxxxxx> |
|---|---|
| Subject: | Re: xfs oops (CVS-2004-05-15_05:00_UTC) |
| From: | Krzysztof Rusocki <kszysiu@xxxxxxxxxxxxxxxxxxxx> |
| Date: | Mon, 21 Jun 2004 04:59:06 +0200 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20040621021505.GA1173@frodo> |
| References: | <20040529155852.GA30391@iceberg.elsat.net.pl> <20040604130816.GA12556@iceberg.elsat.net.pl> <20040621010330.GA1295@iceberg.elsat.net.pl> <20040621021505.GA1173@frodo> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
> > Could you try the 2.6.7 code from XFS CVS for me? (with > SLAB_DEBUG _enabled_). I think this may be fixed by the > XFS buffer undelay fix recently, but I couldn't reproduce > this problem initially so I'm not 100% sure (and I would > really like to know :) -- thanks). > It is done but... Oops is still there - it occurs in shorter period of time than on 2.6.6. run-parts /etc/cron.daily gives here more than fifty percent chance of hitting this. One time I also caught that before init managed to run gettys... However - slab corruption messages did not show up (I have kdb enabled here, so maybe that is the reason). Also, some past observations lead to statement that disabling CONFIG_PREEMPT reduces chance of hitting oops from minutes to hours... but oops occurs in the very same form as with CONFIG_PREEMPT. HTH, Krzysztof |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | data loss over nfs, Sandro Weiser |
|---|---|
| Next by Date: | [Bug 339] data loss problem, bugzilla-daemon |
| Previous by Thread: | Re: xfs oops (CVS-2004-05-15_05:00_UTC), Nathan Scott |
| Next by Thread: | Re: xfs oops (CVS-2004-05-15_05:00_UTC), Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |