similar to: 2.4.18 ext3 problems

Hi I've got serious troubles - I posted a while back about experiencing ext3 errors using 2.4.18, at the time I put the problems down to harddisk failure, but these problems are occurring more and more - not all of our systems are having this problem but 3 systems have now shown this problem. The hardware is essentially the same, the only difference is disk manufacturers but we've now

Bug report follows. Please CC me if you want me to read the reply, as I'm not subscribed to ext3-users. [1.] One line summary of the problem: Ext3 has just causing filesystem corruption which required fsck to fix. [2.] Full description of the problem/report: I just had my machine lock up with an ext3 oops, preceeded by a bunch of error messages in the logs. On rebooting, after replaying the

The system stopped responding to ssh but still responded to ping. The logs showed this error: (its long) Feb 4 00:08:08 server1 kernel: gdmgreeter: page allocation failure. order:0, mode:0x50 Feb 4 00:08:08 server1 kernel: [<c014f863>] __alloc_pages+0x28b/0x29d Feb 4 00:08:08 server1 kernel: [<c014b70f>] find_or_create_page+0x39/0x72 Feb 4 00:08:08 server1 kernel:

Hello ext3-users, I tested ext3 on a Linux for S/390 with several stress and benchmark test tests and faced a kernel bug message. The console showed the following output: Message from syslogd@boeaet34 at Fri Aug 3 11:34:16 2001 ... boeaet34 kernel: Assertion failure in journal_forget() at transaction.c:1184: "! jh->b_committed_data" I tried the Patch from

Hi, I got the OOPS below on my laptop running vanilla 2.4.20-ac2; I had to copy it byhand so it may not be 100% accurate. It hasn't happened again, and this is the first problem I've had with this kernel (or any other kernel, for that matter.) Anyway, I'm not sure, if a) this is actually an ext3 problem, b) OOPS reports of 2.4.20-ac2 are of any interest, so I won't bother with

Hello, We have about 20 - 30 embedded machines running Linux 2.4.13, which the ext3-2.4-0.9.13-2413 patch applied. These are PowerPC 7410 based systems. I am getting reports of Oops happening either during removes (rm's), or coppies (cp's). Most reports state that issuing the same command once the system boots back up, does not cause it to crash. I guess its something else leading up

I recently rebooted one of my machines and was greeted with a message about one of my ext3 partitions having some errors. I dutifully started e2fsck on the partition, but after a few hours of some useful messages about fixing inodes, it then started printing out lists of ascending numbers which I'm not sure how to interpret. The first time I noticed this, these numbers were in the 4000000

Hello ext3-developers, Just to summarize, I reported a kernel bug message with ext3 on S/390 in transaction.c. I was able to reproduce it with a ext3 on LVM and on MD. Tom Rini reported a similar problem on PPC. (both big endian). I have sent a backtrace and with jbd-debug set to 5 I was not able to reproduce the problem until now. On S/390 there are some more debug possibilities. I would