similar to: Bug: 2.2.20pre/ext3 0.0.7a crash apparently in sys_close()

Hi everyone, I've been reading this mailing list once in a while and I have seen that there are quite a few bugs that were resolved since EXT 0.0.7a. I was wondering if using 0.0.7a with kernel 2.2.19 is dangerous or ok because I have had some corrupted files once in a while (using compact flash disk CF on IDE bus). 0.0.7a is the only patch available for kernel 2.2.19 to my knowledge are

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

Hi all, ext3-0.0.7a is now out, at the usual places: ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and propagating now from ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ This fixes one major bug in ext3 recovery for metadata-only journaling. Because recovery can also happen in e2fsck, users should also upgrade to at least e2fsprogs-1.21-WIP-0601 (also provided at the above ftp sites).

The latest errata kernel-2.2.19-6.2.7.src.rpm contains old patches linux-2.2.17-ext3.patch linux-2.2.17-kdb+ext3.patch Is there somewhere a 0.0.7a version of the above that will patch cleanly in the errata kernel (considering all the other patches that get applied before ext3)? I read about ftp://ftp.clusterfilesystem.com/pub/ext3 but when I do $ rpm -qpl

We have a machine that is trying its darndest to house a linux kernel cvs repository. The machine is a dual 733mhz p3 netfinity of some kind. 512M of mem. Filesystem 1k-blocks Used Available Use% Mounted on /dev/sda1 16484504 4015876 11631240 26% / /dev/sda2 31079 3199 26276 11% /boot /dev/sdb2 16516084 32828 15644264 1%

While ripping one of my cds on my laptop this happened: Message from syslogd@theirongiant at Thu Jul 5 09:52:16 2001 ... theirongiant kernel: Assertion failure in do_get_write_access() at transaction.c line 551: "handle->h_buffer_credits > 0" from the kern.log: Assertion failure in do_get_write_access() at transaction.c line 551: "handle->h_buffer_credits > 0"

I get 2 rejects applying 2.2.19-ext3 to latest errata rh 2.2.19 kernel. 1) fs/buffer.c Should I put "J_ASSERT(buf->b_count > 0);" before or after " *(int *)0 = 0;"? ===== ext3 0.0.7a patch --- 934,946 ---- if (buf->b_count) { buf->b_count--; + if (!buf->b_count && + (buf->b_jlist != BJ_None && buf->b_jlist

One of our servers (false) just oopsed. In the middle of lunch. Any advise? On console: false kernel: Assertion failure in journal_start() at transaction.c line 245: "handle->h_transaction->t_journal == journal" In kernel log (ran it through ksymoops): Nov 13 12:35:37 false kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Nov 13 12:35:37

Hi, Doing the following I can generate an assertion in ext3 0.0.7a. I have an ext3 filesystem on /foo. I export /foo via nfs. I then mount via localhost:/foo onto /mnt. Start up a dd to generate a file on the nfs mount. (cd /mnt; dd if=/dev/zero of=./dd.out bs=1024k), then on the localhost filesystem /foo I rm the file. rm -f /foo/dd.out. This results in "ext3_free_inode: bit already

Hello all ! I get the same effect when mounting nfs-exported directories from dom0 in domU. Every mount/umount/showmount command in domU produces the message in the dom0 syslog. I run 2.0.6 compiled from source, with 2.6 dom0 and 2.4 domU on a P4 HT 3.2Ghz. Perhaps this helps to track the problem down. Greetings, Martin ---------- The messages : (dom0 hostname is zen, domU hostname is ftp,

SYSTEM: rh6x based system, 2.2.19-6.2.7 rh errata kernel + 0.0.7a patch, I rebuilt rpm for i686; celeron466, 64MB, PIIX4. root fs is on software raid1 ext2, 6 additional fs's on software raid1 ext2. There's a 3rd HD, not mirrored, which is mounted ext3. EXT3-fs: mounted filesystem with ordered data mode. I enabled journal with tune2fs -j with unmounted fs. The 3 HDs are tuned with

Hi, i am seeing something interesting since the upgrade to 2.2.19/0.0.7a - I am experimenting with the am930 wireless driver and i am crashing on module exit. Everytime i reboot afterwards the var fs on /dev/hda8 is inconsistent [...] Checking all file systems... Parallelizing fsck version 1.21-WIP (01-Jun-2001) /dev/hda7: recovering journal /dev/hda7: clean, 39160/320640 files, 354596/640702

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, after my X froze i had a fs inconsistency after the journal replay [...] EXT3-fs: 03:06: 1 orphan inode deleted EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 64k freed INIT: version 2.78 booting Loading /etc/console-tools/default.kmap.gz Activating swap... Adding Swap: 264560k

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=85 Summary: couldn't write file ,call syscall ,ex. sys_open Product: netfilter/iptables Version: linux-2.4.x Platform: i386 OS/Version: RedHat Linux Status: NEW Severity: major Priority: P2 Component: ip_tables (kernel) AssignedTo:

Assertion failure in journal_add_journal_head() at fs/jbd/journal.c:1679 : "(((&bh->b_count)->counter) > 0) || (bh->b_page && bh->b_page->mapping)" ------------[ cut here ]------------ kernel BUG at fs/jbd/journal.c:1679! invalid operand: 0000 [#2] CPU: 0 EIP: 0060:[<c017637f>] Not tainted EFLAGS: 00010282 EIP is at

Boot options which have been obtained in an architecture-specific fashion have to be copied to /arch.cmd in the rootfs. This implements that functionality for sparc32; the code is identical to sparc64 minus the openprom support for obtaining nfsroot options. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit fc8c0c09f9dd5139dd8d797eaf9fe33962b6cd2c tree

Hi, I've been getting these warnings in syslog since I've been running (Linux) kernels 2.6.31.x and up (I'm currently at 2.6.32.2), they do not show up on 2.6.30.x kernels. Dovecot versions involved were/are 1.2.x, I'm currently at 1.2.9. My system is running Slackware 13.0, but this also happened with 12.2. ------------[ cut here ]------------ WARNING: at

[This email is either empty or too large to be displayed at this time]

Sparc64 has support for a bunch of architecture-specific options taken from the PROM. Convert them to kernel command line form and write the file /arch.cmd in the rootfs, which can be recovered by kinit and processed. The kinit support has already been committed. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit c6e5c5a77681f5bf6f9fea55d031115e9f58ada6 tree