Processed: Re: Bug#410204: linux-image-2.6.18-4-amd64: Data corruption on dm-crypt+XFS
Processing commands for [EMAIL PROTECTED]: severity 410204 important Bug#410204: linux-image-2.6.18-4-amd64: Data corruption on dm-crypt+XFS Severity set to `important' from `critical' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410204: linux-image-2.6.18-4-amd64: Data corruption on dm-crypt+XFS
Hi Sami, I'm told that dmcrypt+XFS has never worked in the upstream kernel or in Debian, so this is essentially an unsupported configuration. But you've filed this bug as critical with the justification that it causes serious data loss. Did you lose data as a result of this bug? Could you explain the process by which that happened? It's my impression that this combination is so unreliable that it will oops before you really have a chance to try to use it for storing data, so you can't really lose any data if you can't put it there in the first place. Based on the status as a known-buggy and unsupported config I think this bug should be downgraded to non-RC status for etch, but I'd like to be sure first that I understand the impact of any real-world risk of data loss. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410204: linux-image-2.6.18-4-amd64: Data corruption on dm-crypt+XFS
Package: linux-image-2.6.18-4-amd64 Version: 2.6.18.dfsg.1-10 Severity: critical Tags: patch Justification: causes serious data loss The current latest 2.6 kernel in unstable causes serious data loss when using XFS over dm-crypt due to a bug or a number of bugs in dm-crypt. Generally XFS metadata corruption sooner or later causes an oops. It's not clear if this will be triggered by anything else than XFS, but that triggers it easily and often. A fix was merged upstream in 2.6.18.6 ([PATCH] dm crypt: Fix data corruption with dm-crypt over RAID5), but is not apparently included in the Debian kernel (or at least I ran into this with a very similar backtrace). See: 1. http://bugzilla.kernel.org/show_bug.cgi?id=7258 (There's some kind of patch referenced in comment #4 and available at http://marc.theaimsgroup.com/?l=linux-kernelm=116503133222152w=2) Also note 2. http://bugzilla.kernel.org/show_bug.cgi?id=7799 (esp. the last comment: Bug in dmcrypt. There's been several bugs in dmcrypt that only XFS has triggered and the last of these that I know about was fixed in 2.6.19.) Sami -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.18-4-amd64 depends on: ii coreutil 5.97-5.3The GNU core utilities ii debconf 1.5.11 Debian configuration management sy ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-1 ext2 file system utilities and lib ii initramf 0.85e tools for generating an initramfs ii module-i 3.3-pre4-1 tools for managing Linux kernel mo ii yaird [l 0.0.12-18 Yet Another mkInitRD linux-image-2.6.18-4-amd64 recommends no packages. -- debconf information: linux-image-2.6.18-4-amd64/postinst/kimage-is-a-directory: linux-image-2.6.18-4-amd64/postinst/bootloader-test-error-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/lilo-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/initrd-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/failed-to-move-modules-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/old-initrd-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-amd64/postinst/old-dir-initrd-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/prerm/removing-running-kernel-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/already-running-this-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/abort-install-2.6.18-4-amd64: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-amd64/preinst/abort-overwrite-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/depmod-error-initrd-2.6.18-4-amd64: false linux-image-2.6.18-4-amd64/postinst/create-kimage-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/postinst/depmod-error-2.6.18-4-amd64: false linux-image-2.6.18-4-amd64/postinst/bootloader-error-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/old-system-map-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/bootloader-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/overwriting-modules-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/elilo-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/prerm/would-invalidate-boot-loader-2.6.18-4-amd64: true signature.asc Description: Digital signature
Bug#410204: linux-image-2.6.18-4-amd64: Data corruption on dm-crypt+XFS
On Thu, Feb 08, 2007 at 05:11:32PM +0200, Sami Liedes wrote: XFS, but that triggers it easily and often. A fix was merged upstream in 2.6.18.6 ([PATCH] dm crypt: Fix data corruption with dm-crypt over RAID5), but is not apparently included in the Debian kernel (or at least I ran into this with a very similar backtrace). See: Hmm, seems it (the entire 2.6.18.6) IS included in the Debian kernel. I wonder which fix is missing then, or if the bug is still in the vanilla kernel tree. Here's the oops: Feb 8 04:43:08 lh kernel: Filesystem dm-7: Disabling barriers, not supported by the underlying device Feb 8 04:43:08 lh kernel: XFS mounting filesystem dm-7 Feb 8 04:43:08 lh kernel: Ending clean XFS mount for filesystem: dm-7 Feb 8 04:46:10 lh kernel: Unable to handle kernel NULL pointer dereference at RIP: Feb 8 04:46:10 lh kernel: [802a749a] page_to_pfn+0x0/0x33 Feb 8 04:46:10 lh kernel: PGD 24a6c067 PUD 1da31067 PMD 0 Feb 8 04:46:10 lh kernel: Oops: [1] SMP Feb 8 04:46:10 lh kernel: CPU 0 Feb 8 04:46:10 lh kernel: Modules linked in: sha256 aes dm_crypt snd_intel8x0 xfs ipt_owner ipt_REJECT xt_state xt_tcpudp iptable_filter ipt_MASQUERADE iptable_nat ip_nat ip_conntrack nfnetlink ip_tables x_tables radeon drm binfmt_misc freq_table ppdev lp button ac battery ipv6 nls_iso8859_1 nls_cp437 vfat fat ext2it87 hwmon_vid i2c_isa eeprom usbmouse ide_cd cdrom tsdev snd_ac97_codec snd_ac97_bus snd_opl3_lib snd_pcm_oss snd_mixer_oss snd_hwdep snd_mpu401 snd_mpu401_uart i2c_nforce2 snd_rawmidi snd_seq_device analog i2c_core parport_pc parport snd_pcm snd_timer psmouse serio_raw snd snd_page_alloc gameport evdev floppy soundcore pcspkr ext3 jbd mbcache dm_mirror dm_snapshot dm_mod ide_generic sd_mod ide_disk sata_nv libata scsi_mod 3c59x mii forcedeth generic amd74xx ide_core ehci_hcd ohci_hcd thermal processor fan Feb 8 04:46:10 lh kernel: Pid: 198, comm: pdflush Not tainted 2.6.18-4-amd64 #1 Feb 8 04:46:10 lh kernel: RIP: 0010:[802a749a] [802a749a] page_to_pfn+0x0/0x33 Feb 8 04:46:10 lh kernel: RSP: 0018:81003e7e97d8 EFLAGS: 00010297 Feb 8 04:46:10 lh kernel: RAX: RBX: 81000bce2640 RCX: Feb 8 04:46:10 lh kernel: RDX: 0056 RSI: 81000bce2640 RDI: Feb 8 04:46:10 lh kernel: RBP: 81003b3c8000 R08: R09: 810037ade870 Feb 8 04:46:10 lh kernel: R10: R11: 81000c1a1ec0 R12: 81000bce2640 Feb 8 04:46:10 lh kernel: R13: R14: R15: 81003e8f8088 Feb 8 04:46:10 lh kernel: FS: 2b4d40df3d20() GS:80521000() knlGS:f7b446c0 Feb 8 04:46:10 lh kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b Feb 8 04:46:10 lh kernel: CR2: CR3: 1e0c6000 CR4: 06e0 Feb 8 04:46:10 lh kernel: Process pdflush (pid: 198, threadinfo 81003e7e8000, task 810037ade870) Feb 8 04:46:10 lh kernel: Stack: 8022bf96 810037ade870 d400 Feb 8 04:46:10 lh kernel: 8101 0001 81000bce2640 81003e8f8088 Feb 8 04:46:10 lh kernel: 8100192517c0 810007f997a8 0056 0002a000 Feb 8 04:46:10 lh kernel: Call Trace: Feb 8 04:46:10 lh kernel: [8022bf96] blk_recount_segments+0x7e/0x21b Feb 8 04:46:10 lh kernel: [802bb9ae] __bio_clone+0x71/0x8a Feb 8 04:46:10 lh kernel: [802bb9fc] bio_clone+0x35/0x3d Feb 8 04:46:10 lh kernel: [8822776a] :dm_crypt:crypt_map+0xcd/0x304 Feb 8 04:46:10 lh kernel: [880d92bf] :dm_mod:__map_bio+0x47/0x9b Feb 8 04:46:10 lh kernel: [880d9c1f] :dm_mod:__split_bio+0x172/0x37d Feb 8 04:46:10 lh kernel: [880da432] :dm_mod:dm_request+0x101/0x110 Feb 8 04:46:10 lh kernel: [80219f55] generic_make_request+0x13a/0x14d Feb 8 04:46:10 lh kernel: [80231028] submit_bio+0xcb/0xd2 Feb 8 04:46:10 lh kernel: [8022aaa5] __bio_add_page+0x188/0x1ce Feb 8 04:46:10 lh kernel: [883ccd8b] :xfs:xfs_submit_ioend_bio+0x1e/0x27 Feb 8 04:46:10 lh kernel: [883cd7c3] :xfs:xfs_page_state_convert+0xa2f/0xb6e Feb 8 04:46:10 lh kernel: [883cdb30] :xfs:xfs_vm_writepage+0xa7/0xdd Feb 8 04:46:10 lh kernel: [8021ac61] mpage_writepages+0x1a6/0x34d Feb 8 04:46:10 lh kernel: [883cda89] :xfs:xfs_vm_writepage+0x0/0xdd Feb 8 04:46:10 lh kernel: [80256d07] do_writepages+0x20/0x2f Feb 8 04:46:10 lh kernel: [8022dbd7] __writeback_single_inode+0x1b4/0x38b Feb 8 04:46:10 lh kernel: [880d9a46] :dm_mod:dm_any_congested+0x38/0x3f Feb 8 04:46:10 lh kernel: [880db58a] :dm_mod:dm_table_any_congested+0x46/0x63 Feb 8 04:46:10 lh kernel: [8021edb1] sync_sb_inodes+0x1d1/0x2b5 Feb 8 04:46:10 lh kernel: [802901be]
