similar to: 2.2.19: Assertion failure in ext3_new_block() at balloc.c line 709

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

I have ext3 0.0.6b + 2.2.19 and cannot get ext3 to compile as a module. If I try to modularize it, or turn in off completely, the kernel build fails. Is there an easy fix for this, or is there something that I am missing? Thanks. Peter

After approx. two weeks of uptime. This host always has some network activity, and when it happened, it was either running or had just finished making backup of about 1200MB (from few ext3 to one ext3 filesystem). kernel was still alive to network pings and services responded, but trying to ssh failed (just hanged there before opening session but after giving last login info). telneting to pop3

Hi, While doing some stress testing with presto module from the intermezzo project layered over ext3, I got the following assertion failure: Jan 17 23:09:55 planck kernel: Assertion failure in jfs_prelock_buffer_check() at journal.c line 410: "bh->b_jlist == 0 || bh->b_jlist == BJ_LogCtl || bh->b_jlist == BJ_IO || bh->b_jlist == BJ_Data" Jan 17 23:09:55 planck kernel:

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

I have seen this error in many postings, but the solutions seem not to apply in this case. This error happens during a small file transfer (gif image) and after 75% of a 165G rsync job (the building file list portion is complete.) Most solutions I saw were related to not having enough RAM or running out of disk space. Check out the machine specs below the error. rsync: writefd_unbuffered

Back again with another oops, which looks suspiciously similiar to the one i posted some days ago (https://listman.redhat.com/pipermail/ext3-users/2002-May/003587.html). Jun 11 12:11:30 castor kernel: Assertion failure in journal_write_metadata_buffer() at journal.c:406: "buffer_jdirty(jh2bh(jh_in))" ksymoops 0.7c on i686 2.4.18-4custom. Options used -V (default) -k

> On Wed, Sep 03, 2003 at 03:49:12PM -0400, Matt Miller wrote: >> I have seen this error in many postings, but the solutions seem not to >> apply in this case. This error happens during a small file transfer >> (gif image) and after 75% of a 165G rsync job (the building file list >> portion is complete.) Most solutions I saw were related to not having >>

Right now I'm building a 2.4.17 kernel on an HPPA Linux system. The kernel it ships with supports ext2 only. Has anybody tried ext3 on HPPA? -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandt@charite.de Charite Campus Virchow-Klinikum Tel. +49 (0)30-450 570-155 Referat V A - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 "A man who

Hi, just had an oops while spool uucp mails via uuxqt->postfix->procmail to multiple mailboxes on an UDMA IDE drive on my Laptop. All filesystems are ext3 and i am running 2.2.19 + ext3 + ide udma patches. When rebooting the system hang - After another reboot everything went smooth. invalid operand: 0000 CPU: 0 EIP: 0010:[<c014ca15>] Using defaults from ksymoops -t elf32-i386

Hi, just got this oops on one of my production servers (4way smp + highmem). Is it fixed in newer kernels or is it something new? Load is steadily growing and i cant even do a 'ps ax'... invalid operand: 0000 CPU: 0 EIP: 0010:[<c0170396>] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010282 eax: 0000001d ebx: 00000000 ecx: c02d5f88 edx:

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

Hi everyone, I am trying to use the function as.date() from the "dates" package in R 2.10.0 to convert a character date to a Julian date, as follows: > as.date("02-MAY-01", order="mdy") # convert May 2, 2001 to a Julian date [1] 2May1 However, when trying to convert a character date from the year 2000 to a Julian date, I get an <NA> instead of the desired

Hi, Please consider the following loop: using v4f32 = float __attribute__((__vector_size__(16))); void fct6(v4f32 *x) { #pragma clang loop vectorize(enable) for (int i = 0; i < 256; ++i) x[i] = 7 * x[i]; } After compiling it with: clang++ -O3 -march=native -mtune=native \ -Rpass=loop-vectorize,slp-vectorize -Rpass-missed=loop-vectorize,slp-vectorize

--------------------------------------------------------------------- Red Hat, Inc. Red Hat Security Advisory Synopsis: kernel 2.2 and 2.4: syncookie vulnerability Advisory ID: RHSA-2001:142-15 Issue date: 2001-10-26 Updated on: 2001-11-02 Product: Red Hat Linux Keywords: syncookie security kernel Cross references: Obsoletes:

After a bit of searching through these archives I haven't found quite my problem described yet, so let me bounce this off you guys: Red Hat 7.2, I run up2date whenever patches come out; right now I'm using kernel 2.4.9-21. Things have been quite pleasant for several months, but in the last week I have begun receiving the following error messages: Feb 22 08:06:27 medmeta kernel:

Hi, i am seeing a crash in ext3_new_block quiet often today on 2.2.19 0.0.7a fsck 1.21 ksymoops 2.3.4 on i686 2.2.19. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.19/ (default) -m /boot/System.map-2.2.19 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the

Hi all! I just upgraded dovecot from 2.2.2 to 2.2.4. Now I can't login to imap, proces imap throws segfault. Here is snip from dovecot.log: 2013-06-25T23:06:47.824321+02:00 meteor dovecot: imap-login: Login: user=<marcin at mejor.pl>, method=PLAIN, rip=2001:470:1f0b:1ab3:1bc:3b24:d355:b142, lip=2001:470:1f15:1b61::2, mpid=44562, TLS, session=<PaQ86ADgegAgAQRwHwsaswG8OyTTVbFC>

We are using MySQL, and love the idea of using zfs for this. We are used to using Direct I/O to bypass file system caching (let the DB do this). Does this exist for zfs? This message posted from opensolaris.org

The following 6 patches cleanup the jbd code and kill about 200 lines. First of 4 patches can apply to 2.6.13-git8 and 2.6.13-mm2. The rest of them can apply to 2.6.13-mm2. fs/jbd/checkpoint.c | 179 +++++++++++-------------------------------- fs/jbd/commit.c | 101 ++++++++++-------------- fs/jbd/journal.c | 11 +- fs/jbd/revoke.c | 158