search for: config_jbd_debug

Tried to compile 0.9.0 with kernel 2.4.6 on a RH7.1 machine with the latest gcc updates installed. gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o sysctl.o sysctl.c sysctl.c:317: `journal_oom_retry' undeclared here (not in a function) sysctl.c:317: initializer

Hi, Andrew - The ext3-0.0.6 patch doesn't build if CONFIG_JBD_DEBUG is set and CONFIG_BUFFER_DEBUG is not set, because include/linux/buffer-trace.h is missing a definition for BUFFER_TRACE2 in one branch of a #ifdef. One-liner patch appended. <b

Hello, I recently switched from 2.2 to 2.4 kernel. Each partition already contains a journal. I tried kernel-2.4.5-0.2.9 from RedHat Rawhide, where ext3/jbd is modularized. For the people who want to try this kernel, you first need to rebuild it, and enable CONFIG_JBD_DEBUG. This solves an unresolved symbol in jbd.o which prevents ext3 to load. (This issue will be solved in next RawHide) My question is on how to tell the kernel to mount the real root partion as ext3, when you load the ext3 module in the initrd ? RAMDISK: Compressed image found at block 0 Freeing in...

...ce left on the device */ - unlock_super (sb); - return 0; + goto out; search_back: /* @@ -694,6 +694,7 @@ got_block: J_ASSERT_BH(bh, !ext3_test_bit(j, bh->b_data)); BUFFER_TRACE(bh, "setting bitmap bit"); ext3_set_bit(j, bh->b_data); + performed_allocation = 1; #ifdef CONFIG_JBD_DEBUG { @@ -815,6 +816,11 @@ out: ext3_std_error(sb, fatal); } unlock_super (sb); + /* + * Undo the block allocation + */ + if (!performed_allocation) + DQUOT_FREE_BLOCK(inode, 1); return 0; } -

An ext3 patch against linux 2.4.10 is at http://www.uow.edu.au/~andrewm/linux/ext3/ This patch is *lightly tested* - ie, it boots and does stuff. The changes to ext3 are small, but the kernel which it patches has recently changed a lot. If you're cautious, please wait a couple of days. The patch retains the buffer-tracing code. This will soon be broken out into a separate patch to make

...s': fs/fs.o(.text+0x1f0fc): undefined reference to `BUFFER_TRACE2' fs/fs.o: In function `ext3_new_block': fs/fs.o(.text+0x1fc6e): undefined reference to `BUFFER_TRACE2' make: *** [vmlinux] Error 1 ...... The (hopefully) relevant part of my config is : CONFIG_EXT3_FS=y CONFIG_JBD=y CONFIG_JBD_DEBUG=y CONFIG_FAT_FS=y CONFIG_MSDOS_FS=y CONFIG_VFAT_FS=y CONFIG_TMPFS=y CONFIG_ISO9660_FS=y CONFIG_MINIX_FS=m CONFIG_PROC_FS=y CONFIG_DEVPTS_FS=y CONFIG_EXT2_FS=y CONFIG_PARTITION_ADVANCED=y CONFIG_MSDOS_PARTITION=y If you need more info, just ask. I am not subscribed, so please CC me. Thanks, Mich...

...2fs -j /dev/hda3" and changed /etc/fstab to ext3. However, when I boot up, the filesystem still gets mounted as ext2. I've been trying to figure out why for many days now.. any ideas? Here's my setup: ---- Debian GNU/Linux unstable Linux kernel 2.4.13 CONFIG_EXT3_FS=y CONFIG_JBD=y CONFIG_JBD_DEBUG=y CONFIG_EXT2_FS=y $ mount --version mount: mount-2.11l I'm using util-linux 2.11l I'm using grub 0.90-11 to boot.. contents of menu.lst: title Linux 2.4.13 with ext3 support kernel /boot/k2413-01 root=/dev/hda3 boot $ cat /etc/fstab /dev/hda3 / ext3 defaults,errors=remount-ro 0 1 /d...

...alues: CONFIG_EXT3_FS=y CONFIG_EXT3_DEFAULTS_TO_ORDERED=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_EXT4_FS=y # CONFIG_EXT4DEV_COMPAT is not set CONFIG_EXT4_FS_XATTR=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_JBD2=y # CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set CONFIG_FS_POSIX_ACL=y =================== Let me know if you need any more details. Reproducing this (or finding a good test to trigger this) is proving to be diff...

...is not set CONFIG_EXT3_FS=y CONFIG_EXT3_DEFAULTS_TO_ORDERED=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y CONFIG_EXT4_FS=y CONFIG_EXT4_FS_XATTR=y # CONFIG_EXT4_FS_POSIX_ACL is not set # CONFIG_EXT4_FS_SECURITY is not set # CONFIG_EXT4_DEBUG is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_JBD2=y # CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set CONFIG_JFS_FS=y # CONFIG_JFS_POSIX_ACL is not set # CONFIG_JFS_SECURITY is not set # CONFIG_JFS_DEBUG is not set # CONFIG_JFS_STATISTICS is not set # CONFIG_XFS_FS is not set # CONFIG_GFS2_FS...

...and non-ext3-aware kernels mount partitions as plain ext2fs. any ideas? Thanks, Stefan Some info about my system (have I forgotten anything important?) ================================================================ I have compiled ext3 into the 2.4.16 kernel: CONFIG_EXT3_FS=y CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set /proc/filesystems mentions that nodev rootfs nodev bdev nodev proc nodev sockfs nodev tmpfs nodev shm nodev pipefs ext3 ext2 msdos nodev nfs tune2fs -l /dev/hda1 tune2fs 1.25 (20-Sep-2001) Filesystem volume name: <none> Last mounted o...

...ls. Special code will probably be needed to simulate crashes during truncate - with this shotgun approach the fs tends to go immutable before *any* of the truncate has committed, and it's as if nothing ever happened. The `ro-after' code and submit_bh() changes are conditional on CONFIG_JBD_DEBUG. So. The big outstanding issue is the VM livelock. It only happens on SMP. If you have a huge amount of dirty data in the system (a big `dd if=/dev/zero of=foo' will do it), everything goes happily for 10-20 seconds and then it freezes. The write drop-behind code should be cutting in here...

...5 21:33:56 2002 +++ linux-akpm-akpm/fs/ext3/super.c Thu Dec 5 21:33:56 2002 @@ -47,6 +47,8 @@ static void ext3_mark_recovery_complete( static void ext3_clear_journal_err(struct super_block * sb, struct ext3_super_block * es); +static int ext3_sync_fs(struct super_block * sb); + #ifdef CONFIG_JBD_DEBUG int journal_no_write[2]; @@ -454,6 +456,7 @@ static struct super_operations ext3_sops delete_inode: ext3_delete_inode, /* BKL not held. We take it */ put_super: ext3_put_super, /* BKL held */ write_super: ext3_write_super, /* BKL held */ + sync_fs: ext3_sync_fs, write_super_lockfs: ext...

Hello. I have installed the ext3 file system on a test system, and sometimes I have a problem: I get an assert from within jbd-kernel.c, and whatever prgram was writing to the disk when this happens is unable to continue. The system is a server I built, which I named "dax". It is running Debian unstable, and I updated it to all the latest packages in Debian unstable as of today.

...19:58:32.000000000 +0900 @@ -582,8 +582,10 @@ * Wait for a specified commit to complete. * The caller may not hold the journal lock. */ -void log_wait_commit (journal_t *journal, tid_t tid) +int log_wait_commit (journal_t *journal, tid_t tid) { + int err = 0; + lock_kernel(); #ifdef CONFIG_JBD_DEBUG lock_journal(journal); @@ -600,6 +602,12 @@ sleep_on(&journal->j_wait_done_commit); } unlock_kernel(); + + if (unlikely(is_journal_aborted(journal))) { + printk(KERN_EMERG "journal commit I/O error\n"); + err = -EIO; + } + return err; } /* @@ -1326,7 +1334,7 @@...

Hi, My gateway/firewall/mailserver machine has been running 2.4.13 for a day or so now. Its basically a stock Linus kernel + ext3-0.9.13 patch (for -pre6, with the rej fixed). I'm getting this in /proc/meminfo: total: used: free: shared: buffers: cached: Mem: 130179072 117489664 12689408 0 46854144 69632 Swap: 1073987584 10907648 1063079936 MemTotal: 127128

Hello, my linux show me that: server2 root # ip route add default scope global nexthop via 192.168.5.1 dev eth2 weight 1 nexthop via 192.168.160.1 dev eth0 weight 1 RTNETLINK answers: Invalid argument What can I do???? Thanks Matias --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.726 / Virus Database: 481 - Release Date:

This is just a rediff and retest - no ext3 changes in this release. http://www.uow.edu.au/~andrewm/linux/ext3/ The latest diff is against linux-2.4.9. The version of ext3 in -ac kernels is current. -ac's ext3 has the "buffer tracing" debug code removed from the non-ext3 files, so the 2.4.9 diff is more useful for bug hunting. I should generate a diff against -ac to enable

...SD Card support # # CONFIG_MMC is not set # # InfiniBand support # # CONFIG_INFINIBAND is not set # # File systems # CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set # # XFS support # # CONFIG_XFS_FS is not set CONFIG_MINIX_FS=y # CONFIG_ROMFS_FS is not set # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/...

Hello everybody! As I wrote in my mail the previous week ("BUG: 2.4.19pre1 & journal_thread & open filehandles") I followed the problem a little bit further. Here's my patch; I beg the ext3-maintainers (Stephen, Andreas, Andrew) to have a look at it and submit it to Marcelo and Linux for inclusion. (2.4 is for now for me more important than 2.5). Patch ----- On every

...SD Card support # # CONFIG_MMC is not set # # InfiniBand support # # CONFIG_INFINIBAND is not set # # File systems # CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set # # XFS support # # CONFIG_XFS_FS is not set CONFIG_MINIX_FS=y # CONFIG_ROMFS_FS is not set # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/...