similar to: e2fsck running for hours, printing out lists of numbers -- should I stop it?

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

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

Hi Stephen, I'm one of developers of SnapFS, which based on Ext3. I got Assertion failure from SnapFS, at ext3_new_block() in fs/ext3/balloc.c: J_ASSERT (!test_and_set_bit(BH_Alloced, &bh->b_state)) If J_ASSERT is only use as debug, why it will modify data? I found the 'BH_Alloced' flag only occures at two place: one is balloc.c as above, the other is at journal_forget() in

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:

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

Hi, Gettings lots of nasty ext3 errors, as follows: attempt to access beyond end of device 03:06: rw=0, want=1989391900, limit=55167178 EXT3-fs error (device ide0(3,6)): ext3_free_branches: Read failure, inode=10092558, block=-1113264762 - several thousand of these in the course of a few seconds And lots of these: EXT3-fs error (device ide0(3,6)): ext3_free_blocks: Freeing blocks not in

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

Just to make sure somebody reacts (please) I'm forwarding this. Please cc me on replies as I'm not subscribed to this list. -------- Original Message -------- Subject: [RESEND] 2.4.20: ext3: Assertion failure in journal_forget()/Oops on another system Date: Wed, 04 Dec 2002 21:27:31 +0100 From: Andreas Steinmetz <ast@domdv.de> To: Linux Kernel Mailing List

I have installed the xen 3.1.0 x86_64 tarball compiled for RHEL5 on a RHEL5 system. The system in question was able to boot with the xen kernel that came with RHEL5. I untarred the tarball, and did cd /boot mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen The command exited properly and made a initrd image. The machine booted with a grub.conf entry like this: title Xen 3.1.0 root

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

Other than what is printed on STD{OUT|ERR}, is there any functional difference between the -p and -y arguments in the e2fsck command? ..Chuck.. -- Chuck Wolber Electronic Flight Bag/ Network File Server Crew Information Systems/ OSS Wonk Mobile: 253.576.1154 Desk: 206.655.6918 "21. A person who is nice to you, but rude to the waiter, is not a nice person." -Dave Barry "25 things

Hi! I had problem yesterday with e2fsck. It reported a bad superblock. I then tried to use one of the other superblocks. To no avail. Then later I remembered that I had switched the fs type to xfs. Maybe e2fsck could recognize other common fs types, and report this instead? best regards keld

Helping a friend fix a computer that was having severe, weird troubles. Reformatted (from XP) and installed Fedora. Install went ok, on first boot, however, filesystem was READONLY for some reason. Knew hard drive was suspect, so I e2fsck'd it over and over all night long, fall asleep next to the computer. This morning, Fedora boots fine, login not a problem, so I shut down and fsck it again,

hi, just wanted to mention that using 1.36-rc1 fixes the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=144771 thanks to benjamin scott for the hint, and theodore ts'o for fixing. building a source and binary rpm with the provided spec file works flawlessly under fc3 (just had to remove -rc1 from the archive name and Version: in the spec file). if you are replying to

Hi, It seems one of my computers died last night and it looks like hard disk trouble. I took the disk out and attached to another system and tried to mount the partition, but the mount doesn't complete and just hangs (process is also unkillable - I had to reboot). So, I tried to run "fsck -fccp /dev/sda2" but the command just hangs after printing "/dev/sda2: recovering

I've run ext3 filesystems for the last few years and I've never seen this question answered..... If a system shutsdown hard, even with journaling is it at all necessary to run e2fsck? Just curious.... Thanks -- Sam Williams samurai at acm.org +----------------------------------------------------------------------+ +"It is easy to be

I have a bit of a problem with the machine I use at home for backups. The main partition the backups reside on is a 4 disk RAID-5, totaling around 240GB. This has had some sort of corruption inflicted on it, in the content of the (at least) one directory, where there are now corrupted directory entries. This happened after I added an additional SiS PCI IDE controller card to the machine and put

fsck (Red Hat Enterprise Linux AS 2.1) returns an exit code 127 on an ext3 file system when run from a shellscript started by cron. Here is the pertinent part of the script: ... fsck -p /dev/${BK_SLICE} 1>/dev/null 2>&1 STATUS=$? if [ ${STATUS} -ne "0" ] then echo "${MIR_PID}: file system check of /dev/${BK_SLICE} failed, status = ${STATUS}" >>${LOG}

Hi, just to do nothing wrong: for lustre 1.6.0.1 e2fsprogs version: 1.39.cfs8 is recommended. Can I assume that I can also better use the most recent version which is recommended for 1.6.4.1 which is e2fsprogs version: 1.40.2-cfs1 Harald -- Harald van Pee Helmholtz-Institut fuer Strahlen- und Kernphysik der Universitaet Bonn