Bug#462424: Acknowledgement (linux-image-2.6.23-1-686: Kernel oops in ext3_clear_inode)
I've had an uptime of more than a month since upgrading to 2.6.25. I think this bug can probably be closed. Thanks, Brendan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462424: linux-image-2.6.23-1-686: Kernel oops in ext3_clear_inode
On Friday, 09 May 2008 at 17:19, maximilian attems wrote: how is 2.6.25 from sid doing? installs just fine in testing? I've just installed 2.6.25-1-686. I'll let you know how it holds up. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462424: updated BUG (no openafs)
Hi all, I've finally gotten another crash while running without the openafs module installed. Here's the updated BUG: Feb 17 06:36:50 peyresourde kernel: BUG: unable to handle kernel paging request at virtual address ffef Feb 17 06:36:50 peyresourde kernel: printing eip: Feb 17 06:36:50 peyresourde kernel: f89d0035 Feb 17 06:36:50 peyresourde kernel: *pde = 4067 Feb 17 06:36:50 peyresourde kernel: *pte = Feb 17 06:36:50 peyresourde kernel: Oops: 0002 [#1] Feb 17 06:36:50 peyresourde kernel: SMP Feb 17 06:36:50 peyresourde kernel: Modules linked in: tun des cbc blkcipher binfmt_misc rpcsec_gss_krb5 nfs sit tunnel4 ipv6 ipt_REJECT nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables quota_v2 nfsd exportfs lockd nfs_acl auth_rpcgss sunrpc eeprom lm85 hwmon_vid ide_generic button tpm_infineon tpm tpm_bios parport_pc parport iTCO_wdt i2c_i801 i2c_core intel_agp agpgart snd_hda_intel sky2 snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr tsdev evdev rtc ext3 jbd mbcache dm_mirror dm_snapshot dm_mod raid456 async_xor async_memcpy async_tx xor sd_mod ide_cd cdrom ata_piix usbhid hid ata_generic libata scsi_mod piix generic floppy ehci_hcd ide_core uhci_hcd usbcore thermal processor fan raid1 md_mod Feb 17 06:36:50 peyresourde kernel: CPU:1 Feb 17 06:36:50 peyresourde kernel: EIP:0060:[f89d0035]Not tainted VLI Feb 17 06:36:50 peyresourde kernel: EFLAGS: 00010287 (2.6.23-1-686 #1) Feb 17 06:36:50 peyresourde kernel: EIP is at ext3_clear_inode+0x1a/0x76 [ext3] Feb 17 06:36:50 peyresourde kernel: eax: c0025874 ebx: c00257dc ecx: f7f72740 edx: ffef Feb 17 06:36:50 peyresourde kernel: esi: c0025874 edi: ebp: f78f1f00 esp: f78f1ec8 Feb 17 06:36:50 peyresourde kernel: ds: 007b es: 007b fs: 00d8 gs: ss: 0068 Feb 17 06:36:50 peyresourde kernel: Process kswapd0 (pid: 202, ti=f78f task=f78316b0 task.ti=f78f) Feb 17 06:36:50 peyresourde kernel: Stack: c0025874 c00259ac 0038 c017d698 0038 c002587c c0025874 c017d95d Feb 17 06:36:50 peyresourde kernel:cbfaf4a4 0080 0080 c017db6c 0080 c0025a64 dc489694 Feb 17 06:36:50 peyresourde kernel:00021d04 c0334de8 00a3 00d0 c01587bd 1e6c 0c2b Feb 17 06:36:50 peyresourde kernel: Call Trace: Feb 17 06:36:50 peyresourde kernel: [c017d698] clear_inode+0xa2/0xf0 Feb 17 06:36:50 peyresourde kernel: [c017d95d] dispose_list+0x46/0xc4 Feb 17 06:36:50 peyresourde kernel: [c017db6c] shrink_icache_memory+0x191/0x1b9 Feb 17 06:36:50 peyresourde kernel: [c01587bd] shrink_slab+0xd9/0x138 Feb 17 06:36:50 peyresourde kernel: [c0158b2f] kswapd+0x2a6/0x3fb Feb 17 06:36:50 peyresourde kernel: [c0133ced] autoremove_wake_function+0x0/0 x35 Feb 17 06:36:50 peyresourde kernel: [c0158889] kswapd+0x0/0x3fb Feb 17 06:36:50 peyresourde kernel: [c0133c24] kthread+0x38/0x60 Feb 17 06:36:50 peyresourde kernel: [c0133bec] kthread+0x0/0x60 Feb 17 06:36:50 peyresourde kernel: [c0104ac7] kernel_thread_helper+0x7/0x10 Feb 17 06:36:50 peyresourde kernel: === Feb 17 06:36:50 peyresourde kernel: Code: c7 a1 c0 2a 9e f8 89 da 83 c4 14 5b e9 e4 9c 79 c7 57 56 89 c6 53 8d 98 68 ff ff ff 8b 53 6c 8b 7b 54 85 d2 74 1d 83 fa ff 74 18 f0 ff 0a 0f 94 c0 84 c0 74 07 89 d0 e8 22 9c 79 c7 c7 43 6c ff Feb 17 06:36:50 peyresourde kernel: EIP: [f89d0035] ext3_clear_inode+0x1a/0x76 [ext3] SS:ESP 0068:f78f1ec8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462424: further oops info (2.6.22-3-686)
On Tuesday, 29 January 2008 at 19:05, maximilian attems wrote: On Sat, 26 Jan 2008, Brendan Cully wrote: Rolling back to the previous kernel, I got a very similar oops but with a little more detail in kern.log: Jan 26 03:35:29 peyresourde kernel: BUG: unable to handle kernel paging request at virtual address ffef Jan 26 03:35:29 peyresourde kernel: printing eip: Jan 26 03:35:29 peyresourde kernel: f8cb6fe0Jan 26 03:35:29 peyresourde kernel: *pde = 4067Jan 26 03:35:29 peyresourde kernel: *pte = Jan 26 03:35:29 peyresourde kernel: Oops: 0002 [#1]Jan 26 03:35:29 peyresourde kernel: SMP Jan 26 03:35:29 peyresourde kernel: Modules linked in: des cbc blkcipher binfmt_misc openafs(P) rpcsec_gss_krb5 auth_rpcgss nfs sit tunnel4 ipv6 ipt_REJECT nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables quota_v2 nfsd exportfs lockd nfs_acl sunrpc eeprom lm85 hwmon_vid ide_generic i2c_i801 i2c_core sky2 iTCO_wdt rtc parport_pc parport psmouse pcspkr serio_raw snd_hda_intel snd_pcm snd_timer snd soundcore snd_page_alloc intel_agp agpgart evdev tsdev ext3 jbd mbcache dm_mirror dm_snapshot dm_mod raid456 xor ide_cd cdrom usbhid hid sd_mod piix ata_piix ata_generic libata scsi_mod generic ehci_hcd uhci_hcd floppy usbcore ide_core thermal processor fan raid1 md_mod Jan 26 03:35:29 peyresourde kernel: CPU:1 Jan 26 03:35:29 peyresourde kernel: EIP:0060:[f8cb6fe0]Tainted: P VLI your kernel is tainted can you reproduce aboves trouble without openafs? I'm running without the openafs client installed now. It can take several days for the error to manifest though... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462424: further oops info (2.6.22-3-686)
Rolling back to the previous kernel, I got a very similar oops but with a little more detail in kern.log: Jan 26 03:35:29 peyresourde kernel: BUG: unable to handle kernel paging request at virtual address ffef Jan 26 03:35:29 peyresourde kernel: printing eip: Jan 26 03:35:29 peyresourde kernel: f8cb6fe0Jan 26 03:35:29 peyresourde kernel: *pde = 4067Jan 26 03:35:29 peyresourde kernel: *pte = Jan 26 03:35:29 peyresourde kernel: Oops: 0002 [#1]Jan 26 03:35:29 peyresourde kernel: SMP Jan 26 03:35:29 peyresourde kernel: Modules linked in: des cbc blkcipher binfmt_misc openafs(P) rpcsec_gss_krb5 auth_rpcgss nfs sit tunnel4 ipv6 ipt_REJECT nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables quota_v2 nfsd exportfs lockd nfs_acl sunrpc eeprom lm85 hwmon_vid ide_generic i2c_i801 i2c_core sky2 iTCO_wdt rtc parport_pc parport psmouse pcspkr serio_raw snd_hda_intel snd_pcm snd_timer snd soundcore snd_page_alloc intel_agp agpgart evdev tsdev ext3 jbd mbcache dm_mirror dm_snapshot dm_mod raid456 xor ide_cd cdrom usbhid hid sd_mod piix ata_piix ata_generic libata scsi_mod generic ehci_hcd uhci_hcd floppy usbcore ide_core thermal processor fan raid1 md_mod Jan 26 03:35:29 peyresourde kernel: CPU:1 Jan 26 03:35:29 peyresourde kernel: EIP:0060:[f8cb6fe0]Tainted: P VLI Jan 26 03:35:29 peyresourde kernel: EFLAGS: 00010287 (2.6.22-3-686 #1) Jan 26 03:35:29 peyresourde kernel: EIP is at ext3_clear_inode+0x1a/0x76 [ext3] Jan 26 03:35:29 peyresourde kernel: eax: c0025874 ebx: c00257dc ecx: f7bd1d40 edx: ffef Jan 26 03:35:29 peyresourde kernel: esi: c0025874 edi: ebp: f7427f08 esp: f7427ed0 Jan 26 03:35:29 peyresourde kernel: ds: 007b es: 007b fs: 00d8 gs: ss: 0068 Jan 26 03:35:29 peyresourde kernel: Process kswapd0 (pid: 170, ti=f7426000 task=f784a030 task.ti=f7426000) Jan 26 03:35:29 peyresourde kernel: Stack: c0025874 c00259ac 0019 c017a474 0019 c002587c c0025874 c017a739 Jan 26 03:35:29 peyresourde kernel:c002d68c 0080 0080 c017a945 0080 c0025a64 c0ac2694 Jan 26 03:35:29 peyresourde kernel:000259f4 f7ffeaa0 009b 00d0 c0156971 255e 0ef2 Jan 26 03:35:29 peyresourde kernel: Call Trace: Jan 26 03:35:29 peyresourde kernel: [c017a474] clear_inode+0xa2/0xf0 Jan 26 03:35:29 peyresourde kernel: [c017a739] dispose_list+0x46/0xc4 Jan 26 03:35:29 peyresourde kernel: [c017a945] shrink_icache_memory+0x18e/0x1b6 Jan 26 03:35:29 peyresourde kernel: [c0156971] shrink_slab+0xd9/0x138 Jan 26 03:35:29 peyresourde kernel: [c0156cfd] kswapd+0x296/0x3e7 Jan 26 03:35:29 peyresourde kernel: [c01331b9] autoremove_wake_function+0x0/0x35 Jan 26 03:35:29 peyresourde kernel: [c0156a67] kswapd+0x0/0x3e7 Jan 26 03:35:29 peyresourde kernel: [c01330f2] kthread+0x38/0x5e Jan 26 03:35:29 peyresourde kernel: [c01330ba] kthread+0x0/0x5e Jan 26 03:35:29 peyresourde kernel: [c01049bf] kernel_thread_helper+0x7/0x10 Jan 26 03:35:29 peyresourde kernel: === Jan 26 03:35:29 peyresourde kernel: Code: c3 8d 90 68 ff ff ff a1 c0 99 cc f8 e9 14 fb 4a c7 57 56 89 c6 53 8d 98 68 ff ff ff 8b 53 6c 8b 7b 54 85 d2 74 1d 83 fa ff 74 18 f0 ff 0a 0f 94 c0 84 c0 74 07 89 d0 e8 53 fa 4a c7 c7 43 6c ff Jan 26 03:35:29 peyresourde kernel: EIP: [f8cb6fe0] ext3_clear_inode+0x1a/0x76 [ext3] SS:ESP 0068:f7427ed0 ksymoops 2.4.11 on i686 2.6.22-3-686. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.6.22-3-686/ (default) -m /boot/System.map-2.6.22-3-686 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Error (regular_file): read_ksyms stat /proc/ksyms failed No modules in ksyms, skipping objects No ksyms, skipping lsmod Jan 24 03:57:07 peyresourde kernel: BUG: unable to handle kernel paging request at virtual address ffef Jan 24 03:57:07 peyresourde kernel: f8cd3035 Jan 24 03:57:07 peyresourde kernel: *pde = 4067 Jan 24 03:57:07 peyresourde kernel: Oops: 0002 [#1] Jan 24 03:57:07 peyresourde kernel: CPU:1 Jan 24 03:57:07 peyresourde kernel: EIP:0060:[f8cd3035]Tainted: P VLI Using defaults from ksymoops -t elf32-i386 -a i386 Jan 24 03:57:07 peyresourde kernel: EFLAGS: 00010287 (2.6.23-1-686 #1) Jan 24 03:57:07 peyresourde kernel: eax: c0025874 ebx: c00257dc ecx: f7069dc0 edx: ffef Jan 24 03:57:07 peyresourde kernel: esi: c0025874 edi: ebp: f7853f00 esp: f7853ec8 Jan 24 03:57:07 peyresourde kernel: ds: 007b es: 007b fs: 00d8 gs: ss: 0068
Bug#462424: linux-image-2.6.23-1-686: Kernel oops in ext3_clear_inode
Package: linux-image-2.6.23-1-686 Version: 2.6.23-2 Severity: important For several months (I think ever since I switched from 2.6.17 to 2.6.18 -- prior to that it was rock solid), I've been getting fairly regular Oops in ext3_clear_inode, after which the entire system becomes wedged (ping works, ssh and login do not). The oopses usually happen at 3-4 in the morning, when I'm mirroring an ubuntu repository for use in our lab. Load is typically high (over 4) during this period, and the disk (4 SATA drives under software raid 5) is very busy. The oops looks like so: Jan 24 03:57:07 peyresourde kernel: BUG: unable to handle kernel paging request at virtual address ffef Jan 24 03:57:07 peyresourde kernel: printing eip: Jan 24 03:57:07 peyresourde kernel: f8cd3035 Jan 24 03:57:07 peyresourde kernel: *pde = 4067 Jan 24 03:57:07 peyresourde kernel: *pte = Jan 24 03:57:07 peyresourde kernel: Oops: 0002 [#1] Jan 24 03:57:07 peyresourde kernel: SMP Jan 24 03:57:07 peyresourde kernel: Modules linked in: des cbc blkcipher binfmt_misc openafs(P) sit tunnel4 ipv6 rpcsec_gss_krb5 nfs ipt_REJECT nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables quota_v2 nfsd exportfs lockd nfs_acl auth_rpcgss sunrpc eeprom lm85 hwmon_vid ide_generic button i2c_i801 tpm_infineon tpm tpm_bios iTCO_wdt i2c_core snd_hda_intel parport_pc parport intel_agp agpgart sky2 snd_pcm snd_timer snd soundcore snd_page_alloc rtc pcspkr evdev tsdev ext3 jbd mbcache dm_mirror dm_snapshot dm_mod raid456 async_xor async_memcpy async_tx xor sd_mod ide_cd cdrom ata_piix usbhid hid ata_generic libata scsi_mod piix generic ide_core uhci_hcd ehci_hcd usbcore floppy thermal processor fan raid1 md_mod Jan 24 03:57:07 peyresourde kernel: CPU:1 Jan 24 03:57:07 peyresourde kernel: EIP:0060:[f8cd3035]Tainted: P VLI Jan 24 03:57:07 peyresourde kernel: EFLAGS: 00010287 (2.6.23-1-686 #1) Jan 24 03:57:07 peyresourde kernel: EIP is at ext3_clear_inode+0x1a/0x76 [ext3] Jan 24 03:57:07 peyresourde kernel: eax: c0025874 ebx: c00257dc ecx: f7069dc0 edx: ffef Jan 24 03:57:07 peyresourde kernel: esi: c0025874 edi: ebp: f7853f00 esp: f7853ec8 Jan 24 03:57:07 peyresourde kernel: ds: 007b es: 007b fs: 00d8 gs: ss: 0068 Jan 24 03:57:07 peyresourde kernel: Process kswapd0 (pid: 202, ti=f7852000 task=f78481b0 task.ti=f7852000) Please let me know if you need further information. Thanks! -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.23-1-686 depends on: ii initramfs-tools [linux-initr 0.91d tools for generating an initramfs ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo linux-image-2.6.23-1-686 recommends no packages. -- debconf information: linux-image-2.6.23-1-686/prerm/removing-running-kernel-2.6.23-1-686: true linux-image-2.6.23-1-686/postinst/old-system-map-link-2.6.23-1-686: true linux-image-2.6.23-1-686/preinst/abort-overwrite-2.6.23-1-686: linux-image-2.6.23-1-686/postinst/create-kimage-link-2.6.23-1-686: true linux-image-2.6.23-1-686/preinst/failed-to-move-modules-2.6.23-1-686: linux-image-2.6.23-1-686/preinst/lilo-initrd-2.6.23-1-686: true linux-image-2.6.23-1-686/postinst/depmod-error-initrd-2.6.23-1-686: false linux-image-2.6.23-1-686/preinst/elilo-initrd-2.6.23-1-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.23-1-686/preinst/overwriting-modules-2.6.23-1-686: true linux-image-2.6.23-1-686/preinst/already-running-this-2.6.23-1-686: linux-image-2.6.23-1-686/preinst/initrd-2.6.23-1-686: linux-image-2.6.23-1-686/preinst/abort-install-2.6.23-1-686: linux-image-2.6.23-1-686/postinst/depmod-error-2.6.23-1-686: false linux-image-2.6.23-1-686/postinst/old-dir-initrd-link-2.6.23-1-686: true linux-image-2.6.23-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.23-1-686/preinst/bootloader-initrd-2.6.23-1-686: true linux-image-2.6.23-1-686/prerm/would-invalidate-boot-loader-2.6.23-1-686: true linux-image-2.6.23-1-686/postinst/old-initrd-link-2.6.23-1-686: true linux-image-2.6.23-1-686/postinst/bootloader-error-2.6.23-1-686: linux-image-2.6.23-1-686/postinst/bootloader-test-error-2.6.23-1-686: linux-image-2.6.23-1-686/postinst/kimage-is-a-directory: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#66096: mutt/170: mutt: on too wide query lists lines mutt acts strange
Synopsis: mutt: on too wide query lists lines mutt acts strange Comment added by brendan on Tue, 27 Mar 2007 03:19:08 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#99104: mutt/627: wanted: way to force interactive mode
Synopsis: wanted: way to force interactive mode Comment added by brendan on Tue, 27 Mar 2007 03:30:01 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140432: mutt/1138: mutt shouldn't ask for passphrases for keys that doesn't have a secret-key available
Synopsis: mutt shouldn't ask for passphrases for keys that doesn't have a secret-key available Comment added by brendan on Tue, 27 Mar 2007 03:53:07 +0200 dedupe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#152444: mutt/1269: send_charset doesn't support charset-hook'd charsets
Synopsis: send_charset doesn't support charset-hook'd charsets State-Changed-From-To: open-closed State-Changed-By: brendan State-Changed-When: Wed, 07 Mar 2007 02:48:11 +0100 State-Changed-Why: Applied, thanks. Comment added by brendan on Wed, 07 Mar 2007 02:48:11 +0100 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407754: openssh-server: GSSAPICleanupCredentials doesn't, unless PrivilegeSeparation is enabled
On Saturday, 20 January 2007 at 18:58, Russ Allbery wrote: Brendan Cully [EMAIL PROTECTED] writes: Package: openssh-server Version: 4.3p2-8 It seems that GSSAPI credentials are not cleaned up unless PrivilegeSeparation is enabled. I prefer to keep that off so that I can use pam_krb5 keyboard-interactive authentication when I don't already have keys. pam_krb5 keyboard-interactive should work fine with privilege separation enabled with the libpam-krb5 in etch. Please let me know if it doesn't. You're right, it does seem to be working now. It'd be nice if ssh cleaned up its gssapi credentials when privsep was off, but it's much less important to me now. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407754: openssh-server: GSSAPICleanupCredentials doesn't, unless PrivilegeSeparation is enabled
Package: openssh-server Version: 4.3p2-8 It seems that GSSAPI credentials are not cleaned up unless PrivilegeSeparation is enabled. I prefer to keep that off so that I can use pam_krb5 keyboard-interactive authentication when I don't already have keys. Unfortunately if I do, /tmp quickly fills with old credential caches. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#376174: linux-headers-2.6.17-1-686 depends on nonexistent package linux-kbuild-2.6.17
Package: linux-headers-2.6.17-1-686 Version: 2.6.17-1 % sudo apt-get install linux-headers-2.6.17-1-686 Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-2.6.17-1-686: Depends: linux-kbuild-2.6.17 but it is not installable E: Broken packages This is on unstable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351183: --run does not fix the disk renaming problem
On Tuesday, 06 June 2006 at 08:53, dean gaudet wrote: On Mon, 29 May 2006, Brendan Cully wrote: So I vote heartily to add --run to the yaird mdadm template. Patch attached for your convenience. i think --run is a bad idea... the docs say nothing about it helping to start a degraded array: Insist that mdadm run the array, even if some of the components appear to be active in another array or filesystem. Normally mdadm will ask for confirmation before including such components in an array. This option causes that question to be suppressed. That's run in the for create, build, or grow section of the manual. If you keep going to the for assemble section, you'll find this: -R, --run Attempt to start the array even if fewer drives were given than are needed for a full array. Normally if not all drives are found and --scan is not used, then the array will be assembled but not started. With --run an attempt will be made to start it anyway. If that also sounds a little suspect, further down find this: Normally the array will be started after it is assembled. How- ever if --scan is not given and insufficient drives were listed to start a complete (non-degraded) array, then the array is not started (to guard against usage errors). To insist that the array be started in this case (as may work for RAID1, 4, 5, 6, or 10), give the --run flag. i'm skeptical that at this point in boot any of the components would be in use anywhere else since we're trying to construct the root filesystem. Brendan did you test this patch? from your description it sounds like you had fixed your problem from a rescue disk before developing the patch... If I remember correctly, what I actually did was: - I booted from a rescue disk - let it rebuild for a while - got impatient to run debian again - unpacked the debian ramdisk, added --run by hand, repacked it - rebooted and found peace. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351183: --run does not fix the disk renaming problem
On Tuesday, 06 June 2006 at 14:55, dean gaudet wrote: Can someone come up with a test command that does not mess with actual devices, and returns true for versions of mdadm that properly supports -Ac partitions? Or even better, a complete patch for yaird? ok cool... well according to the mdadm changelog the -Ac partitions bug was fixed in 1.10.0 ... so we'd want to stick something like this into Templates.cfg !case `mdadm --version 21` in !mdadm\ -\ v1.[1-9][^0-9]*) !mdadm --assemble TMPL_VAR NAME=target --uuid TMPL_VAR NAME=uuid \ !TMPL_LOOP NAME=components TMPL_VAR NAME=dev/TMPL_LOOP !;; !*) !mdadm -Ac partitions TMPL_VAR NAME=target --uuid TMPL_VAR NAME=uuid !;; !esac I don't think it'd be a bad idea to leave in --run for the legacy mdadm case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351183: another vote for mdadm --assemble --run
My box lost one of its raid 5 drives the other day. When I rebooted, I found that I couldn't mount my root filesystem because of that missing drive, even though it should have happily assembled in degraded mode. I had to boot from a rescue disk and reassemble the drive from there (which took hours). It would have been much more friendly of the initrd to allow the md device to assemble in degraded mode. I don't think it would be any less safe either. So I vote heartily to add --run to the yaird mdadm template. Patch attached for your convenience. --- Templates.cfg 2006-05-28 14:14:29.0 -0700 +++ Templates.cfg.new 2006-05-29 17:38:55.0 -0700 @@ -315,7 +315,7 @@ SCRIPT /init BEGIN !mknod TMPL_VAR NAME=target b TMPL_VAR NAME=major TMPL_VAR NAME=minor - !mdadm --assemble TMPL_VAR NAME=target --uuid TMPL_VAR NAME=uuid \ + !mdadm --assemble TMPL_VAR NAME=target --run --uuid TMPL_VAR NAME=uuid \ ! TMPL_LOOP NAME=components TMPL_VAR NAME=dev/TMPL_LOOP END SCRIPT END TEMPLATE
Bug#313550: rssh: now wrong path to sftp-server in ssh-krb5
Hi, RSSH now assumes that sftp-server is in /usr/lib/openssh/sftp-server, but the ssh-krb5 package keeps it in /usr/lib/sftp-server. I'm not sure which package is the buggy one, but either way the result is that I can't use rssh and sftp together. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#313550: rssh: now wrong path to sftp-server in ssh-krb5
I just noticed that the latest version of openssh-server includes krb5 support, so I guess the ssh-krb5 package is now obsolete and doesn't need support. Sorry for the noise. On Tuesday, 04 April 2006 at 12:37, Brendan Cully wrote: Hi, RSSH now assumes that sftp-server is in /usr/lib/openssh/sftp-server, but the ssh-krb5 package keeps it in /usr/lib/sftp-server. I'm not sure which package is the buggy one, but either way the result is that I can't use rssh and sftp together. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351258: mutt/2189: mutt segfaults if external query return spaces
Synopsis: mutt segfaults if external query return spaces State-Changed-From-To: open-closed State-Changed-By: brendan State-Changed-When: Thu, 09 Mar 2006 06:03:32 +0100 State-Changed-Why: Fixed in CVS Comment added by brendan on Thu, 09 Mar 2006 06:03:32 +0100 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346073: mutt/2172: crashes (double free) when closing externally modified mailbox
Synopsis: crashes (double free) when closing externally modified mailbox Comment added by brendan on Fri, 10 Feb 2006 01:45:41 +0100 I had no luck reproducing this on a debian x86 unstable box (last updated this afternoon), including libc6 and libc6-i686 2.3.5-13. Nor can I reproduce this on OS X or Ubuntu. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351220: is the header cache being used?
On Sunday, 05 February 2006 at 19:33, Norbert Tretkowski wrote: * Adeodato Simó wrote: * Norbert Tretkowski [Sun, 05 Feb 2006 07:35:18 +0100]: I tested this on three different machines (2x unstable, 1x sarge with mutt backports). All against the same IMAP server? Yes, courier-imap from sarge. Can you try against some other, or with maildirs in the local filesystem? I tried it with a local Maildir, it's fast. Seems to be a problem with imap. I've done tests with 4 Mutt binaries (1.5.11-5 and 1.5.11+cvs20060126-1, both with libdb and gdbm), and I see no important differences among them (no variation between versions; wrt database backend, same as always: gdbm a biiit slower when creating the db, a biiit faster when reading it). I've tried it with [EMAIL PROTECTED] (bincimap) with a folder of 1400 messages, and with a local maildir with 10200 messages. Hmm... imap or imaps? Would you be willing to try imap as well as imaps? (blowing away the caches each time). It'd help narrow down the places I'd have to look.
Bug#351220: is the header cache being used?
Are you sure the header cache was being used? The version was bumped so mutt was probably ignoring your old cache. Try removing the cache files and then opening your mailbox twice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351263: unset imap_idle
This is a known bug in dovecot's IDLE handler (fixed in CVS, I believe). Unset imap_idle to work around it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318470: mutt/2081: cannot interactively select S/MIME key to sign message with
Synopsis: cannot interactively select S/MIME key to sign message with State-Changed-From-To: open-closed State-Changed-By: brendan State-Changed-When: Wed, 05 Oct 2005 21:21:32 +0200 State-Changed-Why: Fixed in CVS. Thanks to Jeff Ito for debugging the problem. Comment added by brendan on Wed, 05 Oct 2005 21:21:32 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320642: mutt/2074: clarify documentation about pop_checkinterval
Synopsis: clarify documentation about pop_checkinterval State-Changed-From-To: open-closed State-Changed-By: brendan State-Changed-When: Tue, 04 Oct 2005 21:00:29 +0200 State-Changed-Why: Fixed in CVS. Comment added by brendan on Tue, 04 Oct 2005 21:00:29 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#96144: mutt/580: mutt stores PGP passphrase insecurely
Synopsis: mutt stores PGP passphrase insecurely State-Changed-From-To: open-closed State-Changed-By: brendan State-Changed-When: Wed, 05 Oct 2005 05:55:17 +0200 State-Changed-Why: Mutt can use gpg-agent, which pushes this problem outside of mutt's domain. Comment added by brendan on Wed, 05 Oct 2005 05:55:17 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330474: mutt/2096: eats mail by setting content-length to zero in mboxes
Synopsis: eats mail by setting content-length to zero in mboxes State-Changed-From-To: open-closed State-Changed-By: brendan State-Changed-When: Fri, 30 Sep 2005 01:07:43 +0200 State-Changed-Why: Fixed in CVS, sorry about that. Comment added by brendan on Fri, 30 Sep 2005 01:07:43 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296940: mutt/2084: unable to open files 2GB
Synopsis: unable to open files 2GB State-Changed-From-To: feedback-closed State-Changed-By: brendan State-Changed-When: Sat, 24 Sep 2005 21:47:20 +0200 State-Changed-Why: Patch tested on Ubuntu ia32, applied. Comment added by brendan on Sat, 24 Sep 2005 21:47:20 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296940: mutt/2084: unable to open files 2GB
Synopsis: unable to open files 2GB State-Changed-From-To: open-feedback State-Changed-By: brendan State-Changed-When: Sat, 24 Sep 2005 01:48:01 +0200 State-Changed-Why: Try the attached patch. Comment added by brendan on Sat, 24 Sep 2005 01:48:01 +0200 It seems this is a system where off_t is 64 bits but long is 32, so we must use fseeko/ftello instead of fseek/ftell. Try the attached patch and see if it works for you. Many more places in the code may need to be changed :( -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329442: imap/2079: segfault with imap host completion
Synopsis: segfault with imap host completion State-Changed-From-To: open-closed State-Changed-By: brendan State-Changed-When: Thu, 22 Sep 2005 05:10:31 +0200 State-Changed-Why: Applied, thanks. Comment added by brendan on Thu, 22 Sep 2005 05:10:31 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329306: mutt/2080: Segfault on reply when content_type is unset
Synopsis: Segfault on reply when content_type is unset State-Changed-From-To: open-closed State-Changed-By: brendan State-Changed-When: Thu, 22 Sep 2005 05:25:12 +0200 State-Changed-Why: Fixed in CVS, thanks for the report. Comment added by brendan on Thu, 22 Sep 2005 05:25:12 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#316388: mutt/2072: Requires GPG_TTY to be set to use gpg-agent
Synopsis: Requires GPG_TTY to be set to use gpg-agent State-Changed-From-To: open-closed State-Changed-By: brendan State-Changed-When: Wed, 21 Sep 2005 06:50:39 +0200 State-Changed-Why: I've applied patch2 (set GPG_TTY if it isn't already set). I suppose in theory there could be security considerations, but I can't think of them. Comment added by brendan on Wed, 21 Sep 2005 06:50:39 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#275229: mutt/1916: mutt: messing up display after viewing signed messages
Synopsis: mutt: messing up display after viewing signed messages State-Changed-From-To: feedback-closed State-Changed-By: brendan State-Changed-When: Thu, 15 Sep 2005 06:03:11 +0200 State-Changed-Why: Unreproducible, no response for 30 days. Comment added by brendan on Thu, 15 Sep 2005 06:03:11 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#228713: mutt/1772: mutt: progress report on imap connections would be nice
Synopsis: mutt: progress report on imap connections would be nice State-Changed-From-To: open-closed State-Changed-By: brendan State-Changed-When: Wed, 07 Sep 2005 09:44:44 +0200 State-Changed-Why: Fixed in CVS. Comment added by brendan on Wed, 07 Sep 2005 09:44:44 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#213017: mutt/1651: record does not work correctly with imap and tunnel enabled
Synopsis: record does not work correctly with imap and tunnel enabled State-Changed-From-To: open-feedback State-Changed-By: brendan State-Changed-When: Tue, 06 Sep 2005 07:56:26 +0200 State-Changed-Why: Can you reproduce this with 1.5.10? Comment added by brendan on Tue, 06 Sep 2005 07:56:26 +0200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#202305: mutt/1593: mutt: Mutt needn't lock mailbox when opening read-only
Synopsis: mutt: Mutt needn't lock mailbox when opening read-only Comment added by brendan on Tue, 06 Sep 2005 07:52:51 +0200 Refiled as change-request. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#82474: mutt/428: mutt: wishlist: request for mono attributes to be applied to color terminals
Synopsis: mutt: wishlist: request for mono attributes to be applied to color terminals Comment added by brendan on Tue, 06 Sep 2005 00:17:40 +0200 Refiled as change-request. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#88860: mutt/498: mutt does not process PGP/MIME in digests
Synopsis: mutt does not process PGP/MIME in digests Comment added by brendan on Tue, 06 Sep 2005 05:54:20 +0200 Cross-reference with #1070. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#76361: mutt/345: mutt: saving/deleting a thread while in limited view doesn't work
Synopsis: mutt: saving/deleting a thread while in limited view doesn't work Comment added by brendan on Sun, 04 Sep 2005 19:21:31 +0200 Refiled as change-request. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#191850: mutt/1234: Some header fields cannot be edited.
Synopsis: Some header fields cannot be edited. Comment added by brendan on Sun, 04 Sep 2005 19:47:01 +0200 Refile as change-request. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#228713: mutt/1772: mutt: progress report on imap connections would be nice
Synopsis: mutt: progress report on imap connections would be nice Comment added by brendan on Sun, 04 Sep 2005 20:13:02 +0200 Refile as change-request. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#279591: mutt/1937: manpage for /usr/bin/mutt (/usr/share/man/man1/mutt.1.gz) contains unescaped hyphens
Synopsis: manpage for /usr/bin/mutt (/usr/share/man/man1/mutt.1.gz) contains unescaped hyphens Comment added by brendan on Sun, 04 Sep 2005 21:32:30 +0200 Refiled as change-request. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#297084: [EMAIL PROTECTED]: Bug#297084: possible fix]
On Saturday, 30 July 2005 at 18:49, Marco d'Itri wrote:
Subject: Bug#297084: possible fix
Reply-To: John Hedges [EMAIL PROTECTED], [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
From: John Hedges [EMAIL PROTECTED]
I get the same problem. I found '\0's in the messages that caused the
hang and this fix works for me - whether it is the right thing I couldn't
say.
John
diff -ruN mutt-1.5.9.orig/imap/message.c mutt-1.5.9/imap/message.c
+++ mutt-1.5.9/imap/message.c 2005-07-29 16:01:13.446252488 +0100
@@ -590,6 +590,9 @@
for (last = EOF, len = 0; (c = fgetc(fp)) != EOF; last = c)
{
+if (c == '\0')
+ continue;
+
if (c == '\n' last != '\r')
buf[len++] = '\r';
This doesn't seem right. For one thing you can end up appending fewer
bytes than you had said you would - I don't think that's going to be
good for most servers. And for another, to quote RFC 3501:
The APPEND command appends the literal argument as a new message to
the end of the specified destination mailbox. This argument SHOULD be
in the format of an [RFC-2822] message. 8-bit characters are
permitted in the message. A server implementation that is unable to
preserve 8-bit data properly MUST be able to reversibly convert
8-bit APPEND data to 7-bit using a [MIME-IMB] content transfer
encoding.
In other words, it sounds like Courier's not compliant. It would be
good if mutt didn't hang though. I'd have to see a trace to understand
better what was happening. I suppose the worst case scenario is that
mutt converts 8-bit bodies to base64 or something itself before
uploading, but that's really not ideal.
pgpYOpVQ3ChNf.pgp
Description: PGP signature
