[Bug 317781] Re: Ext4 data loss
I strongly agree with Aigars Mahinovs in comment 98, the problem here is not the delayed sync to disk; the problem is the significant discrepancy in time between truncating the old data and syncing the new data. Particularly in case (2), the nice thing to do here is to make renaming a file depend on flushing pending data for the file: either delay syncing the rename, or force the flush on the data. As a developer, I can understand how (1) would be risky if power loss occurred between the truncate and data flush. But (2) should be *made to be* a safe operation (even if not POSIX required), particularly if this can be done without a huge performance loss. By delaying the rename until after the data flush, this shouldn't be a problem. -- Ext4 data loss https://bugs.launchpad.net/bugs/317781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440338] Re: reading data from firewire drive stalls, ieee1394 errors appear in messages
This continues to be a problem in the 9.10 release. I find the easiest solution for myself is to disable ACPI since this is an always-on media center. Any thoughts on whether the ATA command passthrough hiccup is specific to this model of hard drive enclosure, or potentially a more widespread problem? If so, this could be causing subtle performance problems with firewire drives. Perhaps we can request that the ieee1394 driver be patched to avoid the long block associated with this error, but also pm-utils could try to detect and avoid failed calls to hdparm... (the driver blockage may be unavoidable?) -- reading data from firewire drive stalls, ieee1394 errors appear in messages https://bugs.launchpad.net/bugs/440338 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482870] Re: ibus causes application crash when using chinese py input method
I have also seen this on a 9.10 desktop installation a few weeks ago, but I didn't figure out what was causing the application crashes other than some association with using py input method. I don't have access to that machine anymore and can't replicate this on a current 9.10 netbook remix installation. The 9.10 machine was an update from 8.10 and 9.04, previously using SCIM, perhaps this is an artifact of switching from SCIM to ibus...? *shrug* -- ibus causes application crash when using chinese py input method https://bugs.launchpad.net/bugs/482870 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438605] Re: external firewire disk not mounted on boot
This looks related to mine: bug #440338 -- external firewire disk not mounted on boot https://bugs.launchpad.net/bugs/438605 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440338] Re: reading data from firewire drive stalls, ieee1394 errors appear in messages
I've done some research, it looks like the ATA command which is being passed through the SCSI-over-firewire connection is IDENTIFY PACKET DEVICE (for errors with "a1" in the next to last byte of the hex dump) and IDENTIFY DEVICE (for errors with "ec" as the next to last byte). So something is trying to directly query the device (SMART check for drive health?), and apparently my enclosure chipset either doesn't support the passthrough, or the drive doesn't respond and is giving the abort. I will attempt to followup with the enclosure manufacturer, but also if we could figure out what is triggering this query and disable it that would be helpful so I can use my media center again :) -- reading data from firewire drive stalls, ieee1394 errors appear in messages https://bugs.launchpad.net/bugs/440338 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440338] Re: reading data from firewire drive stalls, ieee1394 errors appear in messages
I should also add this may be related to bug #438605. I replicated the problem with another disk (500MB seagate barracuda 7200.10) in another enclosure of the same model (Macally G-S350SUA). I tried running smartctl -a -d sat /dev/sdb and it locked up. ctrl-C and kill -9 were unable to kill the process, but when I turned off the drive (already unmounted) then it exited, with the following in /var/log/messages: Oct 4 15:24:07 ginger kernel: [ 9467.000117] ieee1394: sbp2: aborting sbp2 command Oct 4 15:26:09 ginger kernel: [ 9467.000146] sd 7:0:0:0: [sdb] CDB: ATA command pass through(16): 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 Oct 4 15:26:09 ginger kernel: [ 9467.007586] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Oct 4 15:26:09 ginger kernel: [ 9528.000141] ieee1394: sbp2: aborting sbp2 command Oct 4 15:26:09 ginger kernel: [ 9528.000170] sd 7:0:0:0: [sdb] CDB: ATA command pass through(16): 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 Oct 4 15:26:09 ginger kernel: [ 9589.000410] ieee1394: sbp2: aborting sbp2 command Oct 4 15:26:20 ginger kernel: [ 9589.000439] sd 7:0:0:0: [sdb] CDB: ATA command pass through(16): 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 Oct 4 15:26:20 ginger kernel: [ 9600.424528] INFO: task smartctl:4707 blocked for more than 120 seconds. Oct 4 15:26:20 ginger kernel: [ 9600.424547] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 4 15:26:20 ginger kernel: [ 9600.424561] smartctl D c080b3a0 0 4707 4574 0x0004 Oct 4 15:26:20 ginger kernel: [ 9600.424583] db7d1c38 0082 db4ab960 c080b3a0 c1925a88 c080b3a0 35a0fd6c 089c Oct 4 15:26:20 ginger kernel: [ 9600.424610] c080b3a0 c080b3a0 c1925a88 c080b3a0 359e31f9 089c c080b3a0 cbaf6a80 Oct 4 15:26:20 ginger kernel: [ 9600.424635] c19257f0 db7d1ce8 7fff db7d1cec db7d1c94 c0569b15 db7d1c4c 0096 Oct 4 15:26:20 ginger kernel: [ 9600.424660] Call Trace: Oct 4 15:26:20 ginger kernel: [ 9600.424700] [] schedule_timeout+0x185/0x200 Oct 4 15:26:20 ginger kernel: [ 9600.424728] [] ? __blk_run_queue+0x6e/0x120 Oct 4 15:26:20 ginger kernel: [ 9600.424750] [] ? elv_insert+0x116/0x1f0 Oct 4 15:26:20 ginger kernel: [ 9600.424767] [] wait_for_common+0xa2/0x120 Oct 4 15:26:20 ginger kernel: [ 9600.424783] [] ? default_wake_function+0x0/0x10 Oct 4 15:26:20 ginger kernel: [ 9600.424799] [] wait_for_completion+0x12/0x20 Oct 4 15:26:20 ginger kernel: [ 9600.424814] [] blk_execute_rq+0x75/0xd0 Oct 4 15:26:20 ginger kernel: [ 9600.424827] [] ? blk_end_sync_rq+0x0/0x30 Oct 4 15:26:20 ginger kernel: [ 9600.424842] [] ? blk_recount_segments+0x1e/0x40 Oct 4 15:26:20 ginger kernel: [ 9600.424857] [] ? blk_rq_bio_prep+0x6a/0x80 Oct 4 15:26:20 ginger kernel: [ 9600.424876] [] ? blk_rq_append_bio+0x1f/0x60 Oct 4 15:26:20 ginger kernel: [ 9600.424892] [] ? blk_rq_map_kern+0xbe/0x120 Oct 4 15:26:20 ginger kernel: [ 9600.424909] [] sg_scsi_ioctl+0x20f/0x330 Oct 4 15:26:20 ginger kernel: [ 9600.424926] [] scsi_cmd_ioctl+0x21f/0x480 Oct 4 15:26:20 ginger kernel: [ 9600.424941] [] ? kobject_get+0x12/0x20 Oct 4 15:26:20 ginger kernel: [ 9600.424962] [] ? _spin_lock+0x8/0x10 Oct 4 15:26:20 ginger kernel: [ 9600.424981] [] sd_ioctl+0x8d/0xe0 Oct 4 15:26:20 ginger kernel: [ 9600.425006] [] ? filemap_fault+0xa8/0x340 Oct 4 15:26:20 ginger kernel: [ 9600.425020] [] __blkdev_driver_ioctl+0x6a/0x80 Oct 4 15:26:20 ginger kernel: [ 9600.425035] [] blkdev_ioctl+0x91/0x610 Oct 4 15:26:20 ginger kernel: [ 9600.425055] [] block_ioctl+0x2f/0x50 Oct 4 15:26:20 ginger kernel: [ 9600.425068] [] ? block_ioctl+0x0/0x50 Oct 4 15:26:20 ginger kernel: [ 9600.425084] [] vfs_ioctl+0x1c/0x90 Oct 4 15:26:20 ginger kernel: [ 9600.425097] [] do_vfs_ioctl+0x71/0x310 Oct 4 15:26:20 ginger kernel: [ 9600.425113] [] ? do_page_fault+0x19b/0x380 Oct 4 15:27:18 ginger kernel: [ 9600.425126] [] sys_ioctl+0x5f/0x80 Oct 4 15:27:18 ginger kernel: [ 9600.425142] [] syscall_call+0x7/0xb I have checked that I don't have smartd running (both via ps and checking /etc/smartd.conf), and also I don't normally see the "deprecated SCSI ioctl" warning during I/O stalls, which I would guess smartd would also trigger assuming they mostly use the same underlying code, so this leads me to believe this isn't coming from a smartmontools based check, but then I still don't know what might be sending these SAT passthrough commands. -- reading data from firewire drive stalls, ieee1394 errors appear in messages https://bugs.launchpad.net/bugs/440338 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440347] Re: screen goes black after 10 minutes, while watching mplayer full screen
** Changed in: metacity (Ubuntu) Status: New => Fix Released -- screen goes black after 10 minutes, while watching mplayer full screen https://bugs.launchpad.net/bugs/440347 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440347] Re: screen goes black after 10 minutes, while watching mplayer full screen
This has gone away with recent apt-get upgrades, so no longer an issue. Still would be nice to know what was triggering the screen-blanking though, it still happens at the mythtv menu system, just not during mplayer. Perhaps a function of mythtv itself? Launching mplayer from the commandline (not just within mythtv) will wake the screen and keep it awake. -- screen goes black after 10 minutes, while watching mplayer full screen https://bugs.launchpad.net/bugs/440347 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440338] Re: reading data from firewire drive stalls, ieee1394 errors appear in messages
I have tracked down the source of the sbp2 passthrough commands. ps ax -F during 'normal' operation, then again during a stall, then see what's different: root 5313 1017 0 459 480 0 21:35 ?S 0:00 /bin/sh -c /etc/acpi/power.sh root 5314 5313 0 459 508 0 21:35 ?S 0:00 /bin/sh /etc/acpi/power.sh root 5319 5314 0 459 564 0 21:35 ?S 0:00 /bin/sh /usr/sbin/pm-powersave root 5336 5319 0 459 552 0 21:35 ?S 0:00 /bin/sh /usr/lib/pm-utils/power.d/95hdparm-apm false root 5346 5336 0 426 400 0 21:35 ?D 0:00 hdparm -i /dev/sdb root 5347 5336 0 463 560 0 21:35 ?S 0:00 grep -q AdvancedPM=yes These are consistently found every time. Running the hdparm command manually does indeed trigger the error. Stopping acpid fixes the video hiccups. I have a feeling someone more familiar with acpid configuration could figure out the 'proper' fix so it doesn't requery hdparm so often. Moving to the acpid package. -- reading data from firewire drive stalls, ieee1394 errors appear in messages https://bugs.launchpad.net/bugs/440338 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440338] Re: reading data from firewire drive stalls, ieee1394 errors appear in messages
Looks like the 95hdparm-apm script in particular needs to do something about not calling hdparm unnecessarily... on drives where it is not supported (e.g. my external firewire enclosure) this causes a stall on access to the drive which interrupts things like video playback. ** Package changed: linux (Ubuntu) => pm-utils (Ubuntu) -- reading data from firewire drive stalls, ieee1394 errors appear in messages https://bugs.launchpad.net/bugs/440338 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440338] Re: reading data from firewire drive stalls, ieee1394 errors appear in messages
I see that this bug is still alive and well in the release candidate... this bug makes realtime tasks (like watching videos) from (some?) external firewire drives unusable due to frequent skips and pauses. Perhaps should be fixed for the release? -- reading data from firewire drive stalls, ieee1394 errors appear in messages https://bugs.launchpad.net/bugs/440338 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440338] Re: reading data from firewire drive stalls, ieee1394 errors appear in messages
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/32844107/Dependencies.txt -- reading data from firewire drive stalls, ieee1394 errors appear in messages https://bugs.launchpad.net/bugs/440338 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440338] [NEW] reading data from firewire drive stalls, ieee1394 errors appear in messages
Public bug reported: When playing video from an external ieee1394 drive with mplayer (unsure if it occurs other times too), the video will stall at an irregular interval. After a second or two it will start playing again. During this time, 'top' reports ~100% CPU utilization waiting for I/O (%wa), and the following lines are dumped in /var/log/messages: Oct 1 23:13:42 ginger kernel: [260307.000180] ieee1394: sbp2: aborting sbp2 command Oct 1 23:13:42 ginger kernel: [260307.000213] sd 2:0:0:0: [sdb] CDB: ATA command pass through(16): 85 08 2e 00 00 00 00 00 00 00 00 00 00 40 a1 00 Oct 1 23:13:42 ginger kernel: [260362.84] ieee1394: sbp2: aborting sbp2 command Oct 1 23:13:42 ginger kernel: [260362.000103] sd 2:0:0:0: [sdb] CDB: ATA command pass through(16): 85 08 2e 00 00 00 00 00 00 00 00 00 00 40 ec 00 Oct 1 23:13:42 ginger kernel: [260370.000194] ieee1394: sbp2: aborting sbp2 command Oct 1 23:13:42 ginger kernel: [260370.000221] sd 2:0:0:0: [sdb] CDB: ATA command pass through(16): 85 08 2e 00 00 00 00 00 00 00 00 00 00 40 a1 00 This happens about once every 1-20 minutes, averaging about 4 or 5 minutes (pretty irregular, I don't see a pattern). Also, going back in the log there is a steady stream of these messages, even when the machine is otherwise idle. So it is not access via mplayer, that is simply a symptom that makes it obvious (and annoying). The external drive is a 1TB western digital caviar green WD10EADS living in a Macally G-S350SUA firewire 400 enclosure. I presume the ubuntu-bug has already collected by other system information. ProblemType: Bug Architecture: i386 Date: Thu Oct 1 23:14:03 2009 DistroRelease: Ubuntu 9.10 Package: linux-generic 2.6.31.11.22 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic SourcePackage: linux-meta Uname: Linux 2.6.31-11-generic i686 ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- reading data from firewire drive stalls, ieee1394 errors appear in messages https://bugs.launchpad.net/bugs/440338 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440347] [NEW] screen goes black after 10 minutes, while watching mplayer full screen
Public bug reported: Binary package hint: metacity This is a laptop running as a media center. I have power manager set to never blank the screen. I am also running a minimal session: metacity& xrandr --output LVDS --off --output S-video --mode 800x600 sleep 10; # to let pulseaudio get its act together so mythtv doesn't freak out mythfrontend I see no screensaver and gnome-screensaver-command reports: $ gnome-screensaver-command -q ** Message: Screensaver is not running! Any user interaction (keyboard, mouse) wakes it up. When mplayer exits, that also wakes it up. IR remote signals (e.g. pausing video in mplayer) does NOT wake it up. Why does it blank the screen and how to stop that? Thanks! ProblemType: Bug Architecture: i386 Date: Thu Oct 1 23:44:28 2009 DistroRelease: Ubuntu 9.10 Package: metacity 1:2.28.0-0ubuntu1 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic SourcePackage: metacity Uname: Linux 2.6.31-11-generic i686 ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- screen goes black after 10 minutes, while watching mplayer full screen https://bugs.launchpad.net/bugs/440347 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440347] Re: screen goes black after 10 minutes, while watching mplayer full screen
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/32844373/Dependencies.txt -- screen goes black after 10 minutes, while watching mplayer full screen https://bugs.launchpad.net/bugs/440347 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs