similar to: ext3/2.2.19 vs. ext3/2.4.14

While compiling two kernels and untarring a third, my root fs was remounted r/w and I got the following in dmesg (kernel 2.4.19-pre9): EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28 Aborting journal on device ide0(3,2). ext3_abort called EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal. Remounting filesystem read-only Remounting filesystem read-only

Hello all. I'm using RedHat 7.2 now and haven't have any problems until today. I can still boot into the system at this time, but cannot load X at all. I'm getting the following error message when I try to run fsck. /contains a file system with errors, check forced. Pass 1: Checking inodes, blocks and sizes Error reading block 1277964 (Attempt to read block from filesystem resulted

Hi Everyone! Just to let you know, I am very happy ext3 made it thorugh to linux kernel 2.4.15 We have installed ext3 on several machines here at jtrix.org (including two laptops) and everything seems to be working fine. Our only concern is for our two public servers. They run linux 2.2.19 for stability reasons. On one of the laptops (dual booting 2.2.19 and 2.4.14) kernel 2.2.19 failed to

Red Hat 2.2.19-6.2.12 + 0.0.7a + https://listman.redhat.com/pipermail/ext3-users/2001-November/002258.html (not tuned in /proc yet) + journal 4MB on each fs + 6 ext3 fs on raid1 (hda+hdc) + 1 ext3 fs on another disk not on raid1 (hdd) While untarring (tar zxf) a file that was on a ext3/raid1 onto hdd I got: ksymoops 2.3.4 on i686 2.2.19-6.2.12.g1. Options used -V (default) -k

Hello, Over the last month or so, I've noticed the following error showing up repeatedly in my system logs under kernel 2.4.18-ac3 and more recently under 2.4.19-rc1: EXT3-fs error (device ide0(3,3)) in ext3_new_inode: error 28 I've now been able to capture the following Oops before the system went down entirely: Assertion failure in do_get_write_access() at transaction.c:611:

I am using 2.4.14 and the ext3 patch to go along with it and yesterday I got the following error. Nov 16 20:14:19 ccs kernel: EXT3-fs error (device ide0(3,72)): ext3_new_block: Allocating block in system zone - block = 394173 Well, I immediately went into maintainance mode and checked the file system and there were plenty of errors including a duplicate block and other stuff. I am not sure, is

Hi, Subject line says it all. When one of the linux.org.uk machines got rebooted, it performed a full fs check of the main 160GB ext3 partition claiming it contained errors. During the check it found: Deleted inode 142279 has zero dtime. FIXED. The kernel message log contained lots of: EXT3-fs error (device md(9,1)) in ext3_new_inode: error 28 We had used up all the available inodes.

All, I know that there is no official port to Kernel 2.4.4, thus I may not get any help, however I am hoping someone could point me in the right direction for my problem. I am currently forced to use kernel 2.4.4 for reasons out of my control (embedded board). Here are the exact versions of everything I'm running: ExT3 Version: ext3-2.4-0.9.6-248 Util Version: util-linux-2.11f.tar.bz2 e2fs

I've not been happy with the stories about the "stable" 2.4.x kernels. Everywhere I read people saying "not for production use". Would you recommend adding ext3 to 2.2.19 (ext3-0.0.7a) or moving to 2.4.1x and using ext3 there (ext3-0.9.12)? -- -IAN! Ian! D. Allen Ottawa, Ontario, Canada idallen@ncf.ca Home Page on the Ottawa FreeNet: http://www.ncf.ca/~aa610/

Could anyone help me out, i've got a situation here. :-) I already contacted RTLinux users with no success, I hope ext3 users can help! I have a 2.2.19 kernel patched with RTLinux 3.1, clean and working. I found and applied the ext3 for 2.2.19 kernel patch. Patch went fine (like in README). I was able to tune2fs -j /dev/hda1 (activate the journal). And it actually works. 1) I was not able

hello: I have been reviewin my message slog and have found the following message: Dec 19 06:27:28 server02 kernel: EXT3-fs error (device sd(8,7)) in ext3_new_inode: error 28 What is error 28 and should I be worried about it? Ray Turcotte

Hello All, I had been trying to work on Rails 4 and Mongoid gem. The following are the versions I had installed: bson-2.2.1 mongoid-3.1.6 After installing and trying to run "rails generate" command. It is failing with NameSpace error for BSON::ByteBuffer. It is trying to connect to mongodb server initially and getting successful. Post that it is failing with the following

Please CC me as I'm not subscribed. Attached is my kernel configuration. Please forgive me if this is being asked a gazillion times in the list. I'm using the 2.4.14 patch found at http://www.uow.edu.au/~andrewm/linux/ext3/ . ld -m elf_i386 -T /usr/src/linux-2.4.14/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \

Hi, Here is the situation, I've got a very old webmail system running on kernel version 2.2.10 (I know, upgrade :) and it runs with quotas as the above suggests with ext2. I upgrade the system to kernel revision 2.2.19 + Stephen Tweedie's patches at ext3-0.0.7a.tar.gz (off kernel.org) with the kdb and ext3 patch applied. Booting up the new kernel still on ext2 reveals that quotas still

I have the following tinc setup: client -- tinc DC1 -- tinc DC2 -- 10.1.2.0/24 subnet It generally works well, however, there is one issue I'm not able to solve: *sometimes*, connectivity to *some* destinations does not work for the first few seconds. To demonstrate: $ mongo mongo.example.com:27017 MongoDB shell version: 3.2.12 connecting to: mongo.example.com:27017/test

Hi, i am seeing an oops (every couple of days) on a UP PII system with SCSI disks, Kernel 2.2.19 and ext3 0.0.6b. All oops output passed the klogd thus i cant anymore pipe it through ksymoops - I ensured klogd got the correct System.map so the result should be reliable. Apr 25 17:03:10 Unable to handle kernel paging request at virtual address 8efd1fc8 current->tss.cr3 = 0981e000, %%cr3 =

Hey everyone, I am planning to set up a debian server using the 2.2 kernel tree (kernel 2.2.20) I have tried applying the 2.2.19 patch once but it spewed out some rejects. I went ahead and selected yes to the second fs development code. When I converted all my partitions to 'ext3' (by adding a journal) everything seemed to go well, but when I rebooted (bad shutdown) the computer during

Hello, last fsck says my /tmp and my /home files system has errors, here is the log from fsck using the read-only option: How to recover from this savely? How to avoid this in future? i am using kernel 2.4.18 with the acl-patches from acl.bestbits.at and the patches for the fileutils and e2fsprogs. If you need more informations please mail.

Hello, I have a server running ext3. The server is a dell poweredge 2500 with a 100G raid 0 on a Perc3/Di raid card (aacraid driver). I've asked about this on the aacraid devel list, and no one had any solutions, and I'm not the only one having this problem, because another person on there replied with nearly the same error message as I am getting. Anyway, anywhere from once every few

hi, is this rpms differ from redhat's rawhide 2.4.5 kernel which seems to contain ext3. so my question that your rpm contain different ext3 than rh's rpm? or I can simple use rh's rawhide rpms? thanks. yours. ps. please reply to my private address to since I'm not on the list. thanks. > Hi, > > Mostly for my own use, I prepared two kernel RPM's with Ext3 in them.