Re: OOPS in NTFS [linux 2.2.3]

David Howells (David.Howells@nexor.co.uk)
Wed, 24 Mar 1999 08:35:20 GMT

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Tigran Aivazian: "Re: intercepting syscalls (by setting pointer in sys_call_table)"
Previous message: Harald Kirsch: "2.2.3ac4 and still sockets on nfs unusable"

> That's a bit worrying though, I thought that one had been nailed. Can you
> reproduce it? Were you in a particularly low / fragmented memory state at the
> time?

Very likely, I routinely run at about 20M into my 100M swapspace, having used
up most of my 64M or RAM. There's normally about 1.5M of RAM free when the
machine is idle (which it almost certainly was - the machine runs updatedb off
cron's daily list at 04:02 in the morning).

As for reproducibility - well I'll have to try running some finds on /nt or
maybe try wine a few times (that seems good at showing up NTFS bugs).

David Howells

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Tigran Aivazian: "Re: intercepting syscalls (by setting pointer in sys_call_table)"
Previous message: Harald Kirsch: "2.2.3ac4 and still sockets on nfs unusable"