Bug#763966: linux-image-3.16-2-amd64: Fail to write on ext3 filesystem of an external USB hard drive
I found my drive (Maxtor OneTouch II) is reporting a write cache, which makes the kernel issue SYNCHRONIZE_CACHE requests, but the drive does not support SYNCHRONIZE_CACHE. A change in the 3.16 SCSI layer makes flush errors get processed correctly instead of ignored. I just reported the issue to linux-scsi to start. I'm thinking this will end up as a USB storage quirk. -- Jeff DeFouw m...@plorb.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601141: grub-pc: install_devices check always fails with multiple devices
Package: grub-pc Version: 1.98+20100804-6 Severity: normal Tags: patch Multiple install devices are stored with comma separators. When the postinst script checks for the existence of each device, it does not remove the commas, so it will always fail. Every upgrade asks again for install devices because the test thinks they're missing. Another section of postinst removes the commas with sed, so I copied that in the included patch. -- Package-specific info: *** BEGIN /proc/mounts /dev/mapper/root-root / ext3 rw,relatime,errors=remount-ro,data=writeback 0 0 /dev/md0 /boot ext3 rw,noatime,errors=continue,data=ordered 0 0 *** END /proc/mounts *** BEGIN /boot/grub/device.map (hd0) /dev/disk/by-id/ata-WDC_WD5001ABYS-01YNA0_WD-WCAS87478871 (hd1) /dev/disk/by-id/ata-WDC_WD5001ABYS-01YNA0_WD-WCAS87644777 (hd2) /dev/disk/by-id/ata-WDC_WD5001ABYS-01YNA0_WD-WCAS87724489 *** END /boot/grub/device.map *** /tmp/remove-commas-from-dev-list.patch --- a/grub-pc.postinst 2010-10-23 13:34:51.0 -0400 +++ b/grub-pc.postinst 2010-10-23 13:35:39.0 -0400 @@ -434,7 +434,7 @@ else db_get grub-pc/install_devices valid=1 -for device in $RET; do +for device in `echo $RET | sed -e 's/,/ /g'` ; do if [ ! -e $device ]; then valid=0 break -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages grub-pc depends on: ii debconf [debconf-2.0]1.5.36 Debian configuration management sy ii grub-common 1.98+20100804-6 GRand Unified Bootloader, version ii libc62.11.2-6Embedded GNU C Library: Shared lib ii libdevmapper1.02.1 2:1.02.48-3 The Linux Kernel Device Mapper use ii ucf 3.0025+nmu1 Update Configuration File: preserv grub-pc recommends no packages. Versions of packages grub-pc suggests: ii desktop-base 5.0.6 common files for the Debian Deskto -- debconf information: grub2/kfreebsd_cmdline: * grub2/device_map_regenerated: * grub-pc/linux_cmdline: * grub2/linux_cmdline: grub-pc/install_devices_failed: false * grub-pc/chainload_from_menu.lst: false grub-pc/kopt_extracted: false grub-pc/postrm_purge_boot_grub: false grub-pc/disk_description: grub2/kfreebsd_cmdline_default: quiet * grub2/linux_cmdline_default: quiet grub-pc/install_devices_empty: false * grub-pc/install_devices: /dev/disk/by-id/ata-WDC_WD5001ABYS-01YNA0_WD-WCAS87724489, /dev/disk/by-id/ata-WDC_WD5001ABYS-01YNA0_WD-WCAS87644777, /dev/disk/by-id/ata-WDC_WD5001ABYS-01YNA0_WD-WCAS87478871 grub-pc/install_devices_failed_upgrade: true grub-pc/partition_description: * grub-pc/install_devices_disks_changed: /dev/disk/by-id/ata-WDC_WD5001ABYS-01YNA0_WD-WCAS87724489, /dev/disk/by-id/ata-WDC_WD5001ABYS-01YNA0_WD-WCAS87644777, /dev/disk/by-id/ata-WDC_WD5001ABYS-01YNA0_WD-WCAS87478871 grub-pc/mixed_legacy_and_grub2: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539154: mdadm monitor spins with start-failed raid0
I figured out what's causing this. I sent the following message to the
linux-raid mailing list. The included patch may not be complete, because
it may cause an undesired change of behavior.
You can reproduce the problem by creating a raid0 with two disks,
stopping it, and then assembling it with --run and only one disk.
It will try to start but fail. In this start-failed state, it will be
processed by mdadm --monitor --scan in a way that causes it to spin
forever. If that's not enough, I have a script that reproduces the
problem using loopback devices.
- Forwarded message from Jeff DeFouw je...@i2k.com -
Date: Mon, 28 Jun 2010 02:34:33 -0400
From: Jeff DeFouw je...@i2k.com
To: linux-r...@vger.kernel.org
Subject: mdadm monitor spins with start-failed raid0
mdadm --monitor --scan (--oneshot) spins indefinitely without sleeping
when an inactive start-failed raid0 or linear array is found in
/proc/mdstat. By start-failed I mean something attempts to
(automatically) assemble and start the array, but the array fails to
start. In my case, an old raid0 is missing a disk. The mdstat parser
assumes all entries have a personality string, but inactive arrays
don't.
md0 : inactive sda3[0]
2915712 blocks
The first disk (sda3[0] in this case) is copied as the level string.
The mismatch gets the raid0/linear array into the statelist, which is
immediately rejected by the statelist loop. The rejection occurs
without marking the mdstat entry as used, so the array is seen as a new
entry again, the sleep/break is skipped, a new duplicate state is added
to the statelist, and the loop starts again immediately.
Fixing the parser is simple, but fixing it leads to Monitor ignoring ALL
inactive arrays discovered by mdstat. This is because the mdstat loop
requires a level string. If Monitor should process mdstat-discovered
start-failed arrays (as it currently does), then either the level will
have to be checked using GET_ARRAY_INFO, or raid0/linear arrays will
have to be rejected later.
This patch only shows how to fix the parser.
---
mdstat.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/mdstat.c b/mdstat.c
index 4a9f370..fdca877 100644
--- a/mdstat.c
+++ b/mdstat.c
@@ -168,9 +168,10 @@ struct mdstat_ent *mdstat_read(int hold, int start)
char *eq;
if (strcmp(w, active)==0)
ent-active = 1;
- else if (strcmp(w, inactive)==0)
+ else if (strcmp(w, inactive)==0) {
ent-active = 0;
- else if (ent-active =0
+ in_devs = 1;
+ } else if (ent-active 0
ent-level == NULL
w[0] != '(' /*readonly*/) {
ent-level = strdup(w);
--
1.7.1
--
Jeff DeFouw je...@i2k.com
- End forwarded message -
--
Jeff DeFouw je...@i2k.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#402692: gnucash: crash on tabbing in register entry
On Thu, Dec 28, 2006 at 11:16:01AM -0800, Thomas Bushnell BSG wrote: On Wed, 2006-12-27 at 11:46 -0500, Jeff DeFouw wrote: This just happened to me. Looks like the gnucash developers think this is a gtk+ problem. http://bugzilla.gnome.org/show_bug.cgi?id=364946 The referenced bugzilla report does not describe similar symptoms AFAICT. There are a dozen others that have all been marked as a duplicate of that one. Here's one specifically about tabbing in the description field: http://bugzilla.gnome.org/show_bug.cgi?id=383806 I installed the gtk and glib debug symbol libraries but I haven't been able to reproduce the problem in any case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402692: gnucash: crash on tabbing in register entry
This just happened to me. Looks like the gnucash developers think this is a gtk+ problem. http://bugzilla.gnome.org/show_bug.cgi?id=364946 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
