similar to: ext3 kernel 2.4.13

I am having some trouble compiling ext3 for the 2.4.13 kernel. It appears that the journaling source file is corrupted: In file included from sysctl.c:33: /src/linux-2.4.13/include/linux/jbd.h: In function `buffer_jbd': /src/linux-2.4.13/include/linux/jbd.h:241: `BH_JBD' undeclared (first use in this function) /src/linux-2.4.13/include/linux/jbd.h:241: (Each undeclared identifier is

Hello I am on Athlon 1Gz, kernel 2.4.8. I was running a perl pgm with a lot of disk access, deletions and symlinks creations... Maybe It is due to the kernel version. Could you please inform me if must upgrade to a more recent kernel ? Thanks a lot the kernel logs are : in errors logs Oct 18 17:31:16 tadorne kernel: Assertion failure in journal_revoke_Rb5884a32() at revoke.c:307:

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

Kernel 2.4.8 on an Athlon 500. e2fsprogs-1.23 ext3 compiled as a module. I used "tune2fs" to make /boot and /home into ext3, and remounted them OK. (I am so amazed to see the system come right back without an lengthy fsck on these two file systems after a power off! Well done!) I also used "tune2fs -j" on /, it created a /.journal file. The debugfs features command shows

Hi All, I''m currently running Xen stable (3.0.2-2) with Linux kernel 2.6.16.29. I have a strange problem with *one* of my domU''s, it seems like as soon as I do some heavy disk I/O, the filesystem goes read-only with this on the console: -- end_request: I/O error, dev hda1, sector 8822 Aborting journal on device hda1. ext3_abort called. EXT3-fs error (device hda1):

Hello. I am trying to boot CentOS 4 from a copy of an ext3 software RAID 1 filesystem (md) which has been copied to a normal ext3 filesystem (hd). I am almost getting there, exept that the system hangs after booting the kernel. I copied the datas from the /boot and / partitions to two similar partitions on the backuped disk with mirrordir (can also be done with cp or dd). I have setup the new

I have the exact same issue on several Sunfire v20z (hardware LSI RAID controler). Under high IO load, the raid controler starts complaining with disk errors : [163442.483878] mptbase: ioc0: LogInfo(0x11070000): F/W: DMA Error [163445.172333] sd 2:0:0:0: [sda] Unhandled error code [163445.172338] sd 2:0:0:0: [sda] Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK [163445.172345] sd 2:0:0:0:

when i convert my filesystem to ext3 using tune2fs -j /dev/hdb1 it create's it fine but when i change it in fstab to auto. when i reboot it says fsck.auto and there is a problem when it says that can someone please help. Dustin Schuemann andkidx@yahoo.com --------------------------------- Do You Yahoo!? Make international calls for as low as $0.04/minute with Yahoo! Messenger.

Hi all i installed Redhat beta Roswell, then i updated to Kernel 2.4.8 patched him and installed the newest util-linux + e2fprogs without any custoumized Options. Bootloader is Grub. Now when i boot he says mount -O or -0 is an invalid Option. tune2fs -j /dev/hdXX says "The filesystem already has a journal" lsmod says that no jbd or ext3 Modules is loadet but i have pachted the Kernel

Hi, I am a new ext3 user and I am having problems similar to what many people are facing on this list. I have done everything as the emails suggest. I am using SuSE 7.3 with the the 2.4.10 kernel and ext3 compiled as a module. Because it is 2.4.10 kernel, I created all my journals from a rescue disk and everything seems to be working right for the non-root filesystems. My fstab has all my

Hi I am trying to have a built in initramfs along with the traditional initrd. So I mount the initrd from the initramfs, but am facing problems in trying to run the 'linuxrc'. Following are the issues: 1. I mount the initrd from the initramfs and exceve 'linuxrc'. It starts executing linuxrc, but gives the following errors and panics: Red hat nash version 3.4.42 starting

Ok So I''ve been able to successfully create a CentOS5 virt-install on xen using LVM created partitions. But have many problems trying to install 4.4 (It does not work with virt-install hence you have to try another method). I Created a name, name-tmp, name-swap, name-root paritions. I did mke2fs and mkswap no problem everything is good. I went on further to mount the name-tmp and

Chris Mason wrote: > > > Hi guys, > > Here's a new patch against 2.4.8-pre8, updated to Al's new super > handling. The differences between the original are small, > but they are big enough that I want extra testing from the > LVM guys (and ext3/XFS). ext3 will probably lock up on unmount with 2.4.8-pre8. The fix is to replace fsync_dev with fsync_no_super in

Steve, 1) go to /etc/asterisk 2) open modules.conf for editing using vi 3) add this line: noload=pbx_wilcalu.so 4) Save the file 5) Restart asterisk Lightup the candles, open the Cabernet Savignon ( or whatever your prefernce) and call your girlfriend. ;) Seshu -----Original Message----- From: asterisk-users-bounces@lists.digium.com

This patch contains the following possible cleanups: - make needlessly global functions static - #if 0 the following unused global functions: - journal.c: __journal_internal_check - journal.c: journal_ack_err - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL's: - journal.c: journal_check_used_features -

Hi, A couple of our important servers, both running FC4 but one i386 and one x86_64, have been crashing recently. They both are running ext3 data=journal with large external journals and high commit intervals. Both machines use the gdth driver for their hardware RAID sets, if that's of any use. I think the hardware is good in both cases. I hope someone finds this data useful enough to be

Dear R mailing group, I am having extreme - and mysterious - trouble installing R. I tried simply dl ing R-2.3.1.tar.gz, and unzipping it, but after doing so, nowhere could I find a file called R-2.3.1.exe. I did however find an R-2.3.1.exe.manifest. I therefore tried the command line installation command - given in R-admin.pdf. This command is: tar zxvf R-2.3.1.tgz This is strange

Okay, after playing around a bit more, I'm getting two oopes in a row when running dbench 16 or dbench 32. Decoded, here they are: Assertion failure in unmap_underlying_metadata() at buffer.c:1530: "!buffer_jlist_eq(old_bh, 3)" kernel BUG at buffer.c:1530! Oops: Exception in kernel mode, sig: 4 NIP: C003BB34 XER: 00000000 LR: C003BB34 SP: CF881E00 REGS: cf881d50 TRAP: 0700 Using

I used to be able to install the efax application from efax.com but it seems to hang now when I click the first "Next" button. cpu is spiked and just continues to run endlessly until I kill it. Here's the debug information if anyone can help... Invoking /usr/lib/wine/wine.bin msgrplus.exe ... warn:ntdll:NtCreateFile L"\\??\\C:" not found (c0000034)

An ext3 patch for the latest Linus kernel is at http://www.uow.edu.au/~andrewm/linux/ext3/ The changes are quite small: - Tided up some code now that quotas in Linus and -ac kernels are synced up. - Fix a race which can cause a null-pointer deref in ext3_writepage(). This bug has been there for a long time, but only manifested in 2.3.13-pre for some reason. I've tested this pretty