Hello, I investigated newsgroups and mailinglists for aprox. 3 weeks now. But i have not found any comment about ext3 freezing a whole system. But: I do have 5 ext2 partitions on my system. I upgraded theses partitions to ext3 with tunefs. after mounting 1 partition as ext3 all was fine. After that i mounted all partitions as ext3. And, after approx. 3-4 minutes my system freezes. No mouse or keyboard input was accepted. Only the keyboard LEDS were flashing. Has anybody else the same expirience? My System is a SuSE 8.1 with kernel 2.4.19 Is this a known Problem? And if not, which is the correct way of reporting it. Ciao, carsten
On Wednesday 30 October 2002 16:58, read_news@c-hoehne.de wrote: Hi Carsten,> I investigated newsgroups and mailinglists for aprox. 3 weeks now. But i > have not found any comment about ext3 freezing a whole system. > But: > I do have 5 ext2 partitions on my system. I upgraded theses partitions > to ext3 with tunefs. > after mounting 1 partition as ext3 all was fine. After that i mounted > all partitions as ext3. And, after approx. 3-4 minutes my system > freezes. No mouse or keyboard input was accepted. Only the keyboard LEDS > were flashing. > Has anybody else the same expirience? > My System is a SuSE 8.1 with kernel 2.4.19 > Is this a known Problem? And if not, which is the correct way of > reporting it.The flashing of LED's seems that SuSE has the morse code if panic() in the kernel. I've never heard of ext3 freezing the mashine and I also never experienced this kind of thing. ... I assume you were in X? Please test this again without beeing in X. A small stress test can be: while true; do dd if=/dev/zero of=/largefile bs=16384 count=131072; done this will create a ~ 2gb file in / named largefile. You should see an oops/panic output if the LED's are starting again flashing. The output of above you have to feed ksymoops with. -- Kind regards Marc-Christian Petersen http://sourceforge.net/projects/wolk PGP/GnuPG Key: 1024D/569DE2E3DB441A16 Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16 Key available at www.keyserver.net. Encrypted e-mail preferred.
I have a RH 7.3 system with kernal 2.4.18-3smp with ext3 drives that seemed to be working OK, but in past few days it has hung up several times, with the kernal still running (system responds to pings), but all other services are stalled. The consistent message in /var/log/messages is: Nov 17 11:21:24 krypton kernel: Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)" Nov 17 11:21:24 krypton kernel: ------------[ cut here ]------------ Nov 17 11:21:24 krypton kernel: kernel BUG at commit.c:535! Nov 17 11:21:24 krypton kernel: invalid operand: 0000 And it goes on. This sounds similar to what you are experiencing. I'm looking for some documentation that this is a bug, and that there is (hopefully) a fix. Can I turn ext3 off and revert to ext2 by simplying change my fstab file, or is life not that simple? John V. Kjellman