More on my segmentation problems. Just looking at the end of each kernel message, they always end with: EIP [XXXXX] jbd2_journal_data_metadata-XXX This occurs when I try to copy data from my main partition to a backup partition or make a tarball. Both partitions are setup with flex_bg,meta_bg,uninit_bg with ordered data mode using noatime,nodiratime,journal_async_commit mount parameters. Again, the snapshot from 062508/0019hrs GMT -- ext4-patch-queue-b5db22ef52ed53d8e3fa978a5a29e1609c9333aa.tar.gz works fine patching a clean linux-2.6.26-rc6 source and exhibits no problems whatsoever. Starting with the next snapshot (062608/0042hrs GMT) is where my segfaults start. This continues using the newest snapshot from 062608/2251hrs GMT. I have patched the source from the individual snapshots mentioned as well as just pulling and updating my ext4-patch-queue folder with the same results. If I roll the kernel back to the 062508/0019 snapshot, the problems vanish. No errors noted during e2fsck -fvy on either partition. This is driving me crazy! Gary -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
