similar to: What ext3 release is in 2.2.17-14?

Im intending use Ext3 file system in my web farm. Im using RedHat 6.2 (kernel 2.2.16-3) and Turbo Linux Cluster Server 6.0. I have NO SUCCESS in path my own kernel. I downloaded the following ext3 packages: ext3-0.0.2f.tar.gz (linux-2.2.16-3.kdb.diff , linux-2.2.16-3.ext3.diff ) e2fsprogs-1.20-0.WIP.i386.rpm e2fsprogs-1.20-0.WIP.src.rpm e2fsprogs-1.20-0ext3.i386.rpm

Is there any way (short of not patching it into the kernel) to turn KDB off on a given machine? There are some machines I do not want dropping into kdb when/if it oopses. Thanx, b.

Hello, Now that kernel 2.2.20 is out with security fixes, I'd be interested in using it with ext3. The latest patch for 2.2.19, 0.0.7a, applies with some offset (both with and without kdb), and even compiles (without kdb), but I scarcely know what I am doing so haven't tried it yet. Could people in the know enlighten me on that point? I guess there is little chance for another ext3

When trying to build ext3 as a module, I get the follwing errors during the kernel link: /usr/bin/kgcc -D__KERNEL__ -I/home/brian/src/kernel-2.2.19-pre6mvd/linux-2.2.19pre6-kdb-ext3/include -c -o dummy_sym.o dummy_sym.c ld -m elf_i386 -T /home/brian/src/kernel-2.2.19-pre6mvd/linux-2.2.19pre6-kdb-ext3/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_t ask.o -Map map

hi. i'm using 2.2.18 with ext3-0.0.5e on a dual p3-550 with 1.5 gigs of ram. the system is redhat 6.2-based but with lots of modifications and a clean kernel build. i've been using 2.2.18 and 2.2.17 with ext3 patches on other machines with much success and no problems, up until last night, when the machine mentioned above kernel panicked on me. unfortunately i don't have much of

I see that the ext3 kernel being used is an enterprise kernel which doesn''t build the PCMCIA modules generally. Any chance of getting the SRPM so that testing on a laptop can actually be possible? It''s too much fun to have a laptop and just hit the power button and not have to fsck:) Jeremy -- Jeremy Katz katzj@linuxpower.org | jlkatz@eos.ncsu.edu http://linuxpower.org |

Hello All, I am running Linux 2.4.7-10, 2.4.18-4 and 2.4.19-pre9, I see the following oops quite often (mainly on 2.4.19-pre9 with kdb). All the kernels I use have the kdb patch installed. 1 kmem_cache_alloc (offset 0x125) get_unused_buffer_head journal_write_metadata_buffer journal_commit_transaction kjournald kernel_thread kmem_cache_alloc dis xchg %eax, (%ebx) cmp $0x5a2cf071, %eax (where

Hi Stephen, I posted a similar report on linux-kernel a month ago, but didn't hear anything new from you. So I try it again in this list, this time with some additional info: Using a stock 2.2.17 kernel with NFS-patches and ext-0.0.3b I can reliably lockup the kjournald when extracting two or three tar.gz files (e.g. kernel tar-balls) onto a ext3 filesystem with activated quotas. This

I previously wrote: > I have come across what appears to be a bug in __invalidate_buffers() > w.r.t. the change in ext3-0.0.6 using BH_JDirty instead of BH_Dirty > for buffers held in the journal. If invalidate_buffers() is called > on a device (LVM likes to do this a lot, for whatever reason), it yanks > JDirty buffers out from underneath the journal layer, and causes an > oops

Hi, I have been trying to debug Xen using kdb. However, I am unable to successfully boot dom0 after compiling and installing kdb. Software/hardware config: Base distribution - Debian Lenny (64-bit) on a Dell desktop (Optiplex 780) with a serial cable to another machine. Xen 4.0.1 (without kdb) works fine. Here are the steps I followed to set up Xen-unstable with kdb. 1. Cloned code from

Hi Guys, Thanks for the interest in the xen hypervisor debugger, prev known as kdb. Btw. I''m gonna rename it to xdb for xen-debugger or hdb for hypervisor debugger. KDB is confusing people with linux kdb debugger and I often get emails where people think they need to apply linux kdb patch also... Anyways, attaching patch that is cleaned up of my debug code that I accidentally left in

[ Tried to check the archives but the website seems to be down or something ] On one of our installations, I am seeing messages such as: EXT3-fs warning (device ide0(3,9))): ext3_free_inode: bit already clearned for inode 14 Anybody know exactly what they mean? These would be on a 0.0.6a system. b.

I asked this a few weeks ago but didn''t get a response, so at the risk of being a nag, I''ll abbreviate and restate. I know there are other Xen specific debuggers, but I want to know if there''s any reason why SGI''s kdb, http://oss.sgi.com/projects/kdb, should not be included in a dom0 pv-ops kernel? While the patches apply cleanly and build, the result is that

Hi, kdb: to debug xen hypervisor, could also debug guests gdbsx: to debug PV/HVM linux guests The tree is : http://xenbits.xensource.com/ext/debuggers.hg See README-dbg. You''ll need to setup serial access for kdb. Thanks, Mukesh > > Hi Dan, > > I''m currently using your version of ssplitd as it is. I haven''t tried > kdb. For some reason I

Hi Stephen, We had some starvation/locks happening to us under very heavy load in two cases: - InterMezzo asked ext3 to do a journaled file write (for 1 block) essentially using ext3_write - similarly for truncate. These lockups went away when we started the transaction in InterMezzo and reserved somewhat more space than ext3 does. Any clues as to what this might be? Are the ext3

I updated my kernel from 0.0.3d to 0.0.3e using the "d-e" patch in the 0.0.3e tarball. When I try to boot the new kernel on a machine with an ext3 root filesystem I am getting the message: JFS: Unrecognised features on journal Does this sound feasible or even somewhat expected? Is there any interest in me doing some debugging of this? Is there any way to deal with this without

Apologies for a vague and wooly bug report, but I can't reproduce this on my test systems - I *can* reproduce it on some production ones like a flash.... but that seems to upset our operations guys :-( I am getting a set of crashes on some boxes in the field, apparently related to high network traffic (this only occurs on boxes with ethernet connectivity back to the centre rather than the

I desperately need the ability to quickly recover from a power loss so I am finally going to break down and spend some time with ext3. I dl'ed the ext3-0.0.6b.tar.gz and unzipped it in /usr/src. Then I installed kernel-source-2.2.19-6.2.1.i386.rpm from redhat I then treid to apply the patches: cat ../ext3-0.0.6b/linux-2.2.19pre14.kdb.diff | patch -sp1 cat

I've just set up a brand new system with software raid1 (in degraded mode) with one IDE 20GB drive, using kernel 2.2.19pre16 with ext3 0.0.6b. It's split like this.. 32MB /dev/hda1 /boot 2GB /dev/hda2 / ~18GB /dev/hda3 /home all partitions are marked as 0xfd (autostart raid) with the patches from http://people.redhat.com/mingo/raid-patches for 2.2.17. And I've made all the ext3

I admit I was scepticle of this suggestion - but it actually seems to have worked. COmpiling a straight GENERIC kernel with KDB and DDB included do seem to have made my irq22 interrupt storms go away. Certainly I have spent some time trying to provoke the problem and not managed to make it read it's ugly head again. The thing is though, this doen't make me particularly happy - as I am