| To: | Claas Langbehn <claas@xxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS forced shutdown with kernel 2.6.0 |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Fri, 2 Jan 2004 18:29:21 +0000 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20040102095051.GA19872@xxxxxxxxxx>; from claas@xxxxxxxxxx on Fri, Jan 02, 2004 at 10:50:51AM +0100 |
| Mail-followup-to: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, Claas Langbehn <claas@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
| References: | <20040102095051.GA19872@xxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5.1i |
On Fri, Jan 02, 2004 at 10:50:51AM +0100, Claas Langbehn wrote: > Hello! > > > Last night one of my machines running xfs shut down my /homes partition. > > That machine was running Azureus (a bittorrent client) with probably > high memory usage. > > But even if the memory usage of one program is going near to 100% it > should not force the filesystem to shutdown. Instead it should crash > the application. > > I could also think of bad memory, but we did test the SDRAM modules > only a week ago, and they passed memtest86. > > After rebooting everything was working fine, again. > > So, is this a bug of xfs? I've seen the same bug a few times lately, but only if I had previous memory corruption due to code I was hacking on. Can you reproduce it without the nvidia module loaded as that is likely source of such corruption? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Bug 302] DMAPI conditional build broken in linux-2.6-xfs tree from 20040101, bugzilla-daemon |
|---|---|
| Next by Date: | Re: XFS forced shutdown with kernel 2.6.0, Valdis . Kletnieks |
| Previous by Thread: | [Bug 297] snapshot-2.4.23-2003-12-01_00:33_UTC quota options problem, bugzilla-daemon |
| Next by Thread: | Re: XFS forced shutdown with kernel 2.6.0, Valdis . Kletnieks |
| Indexes: | [Date] [Thread] [Top] [All Lists] |