[Bug 203323] Re: fsck/usplash: device names not fully reported
** Branch linked: lp:ubuntu/sysvinit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/203323 Title: fsck/usplash: device names not fully reported To manage notifications about this bug go to: https://bugs.launchpad.net/e2fsprogs/+bug/203323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 203323] Re: fsck/usplash: device names not fully reported
** Branch unlinked: lp:~ubuntu-branches/ubuntu/karmic/sysvinit/karmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/203323 Title: fsck/usplash: device names not fully reported -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 203323] Re: fsck/usplash: device names not fully reported
** Branch linked: lp:ubuntu/karmic/sysvinit -- fsck/usplash: device names not fully reported https://bugs.launchpad.net/bugs/203323 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 203323] Re: fsck/usplash: device names not fully reported
Thanks for the logsave patch. It's probably a good idea to apply it (in Debian, preferably), but I think I'll stick to the direct fsck.ext[23] killing in the usplash fsck integration. If I would kill the entire fsck -A, then one ESC would abort *all* checks, not just the one on the current partition. This could hide checks which are done for genuinely broken file systems, so I'd rather avoid this. -- fsck/usplash: device names not fully reported https://bugs.launchpad.net/bugs/203323 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 203323] Re: fsck/usplash: device names not fully reported
This bug was fixed in the package e2fsprogs - 1.40.8-2ubuntu2 --- e2fsprogs (1.40.8-2ubuntu2) hardy; urgency=low * Fix progress information when fsck'ing multiple partitions. (LP: #203323) * Treat ext4 and ext4dev file systems as fsck'able. * Patches taken from upstream bug tracker: https://sourceforge.net/tracker/index.php?func=detailaid=1926023group_id=2406atid=102406 Thanks a lot to Theodore Ts'o! -- Martin Pitt [EMAIL PROTECTED] Thu, 27 Mar 2008 17:03:53 +0100 ** Changed in: e2fsprogs (Ubuntu) Status: Confirmed = Fix Released -- fsck/usplash: device names not fully reported https://bugs.launchpad.net/bugs/203323 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 203323] Re: fsck/usplash: device names not fully reported
The logsave patch is in the e2fsprogs maint branch so it will be in the next release of Debian unstable's e2fsprogs, and/or e2fsprogs 1.40.9. Best regards, -- Ted -- fsck/usplash: device names not fully reported https://bugs.launchpad.net/bugs/203323 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 203323] Re: fsck/usplash: device names not fully reported
Ah, this happens if fstab specifies different check order priorities for different partitions (by default all non-root FSes are priority 2 and thus checked in parallel). -- fsck/usplash: device names not fully reported https://bugs.launchpad.net/bugs/203323 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 203323] Re: fsck/usplash: device names not fully reported
In the case where several devices are e2fsck'ed in parallel, using fsck -A -C3 only reports progress for the first device; there is no further output on FD 3 for the other devices. This causes usplash to not report any progress in this case, which is difficult to work around in the usplash scripts. That needs to be fixed in e2fsck itself. ** Changed in: sysvinit (Ubuntu) Status: In Progress = Fix Committed ** Also affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Changed in: e2fsprogs (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) Status: New = Confirmed -- fsck/usplash: device names not fully reported https://bugs.launchpad.net/bugs/203323 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 203323] Re: fsck/usplash: device names not fully reported
** Bug watch added: SourceForge.net Tracker #1926023 http://sourceforge.net/support/tracker.php?aid=1926023 ** Also affects: e2fsprogs via http://sourceforge.net/support/tracker.php?aid=1926023 Importance: Unknown Status: Unknown -- fsck/usplash: device names not fully reported https://bugs.launchpad.net/bugs/203323 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 203323] Re: fsck/usplash: device names not fully reported
This bug was fixed in the package sysvinit - 2.86.ds1-14.1ubuntu42 --- sysvinit (2.86.ds1-14.1ubuntu42) hardy; urgency=low * debian/initscripts/lib/init/usplash-fsck-functions.sh: - When pressing ESC, do not kill the logsave command (since this does not reliably kill the subprocess), but the fsck.ext[23] processes directly. (LP: #203322) - When checking multiple partitions in succession, print the name of the next device when it comes to its turn. NB that this still does not work with checking multiple partitions in parallel, that's an fsck bug. (LP: #203323) - Use usplash 0.5.17's new FAIL_NO_USPLASH mode to avoid being stuck at reading from the usplash FIFO if usplash died during fsck. - Also output fsck progress information to the current console. This looks quite dodgy ATM, but is better than not printing anything at all if usplash died in between. -- Martin Pitt [EMAIL PROTECTED] Wed, 26 Mar 2008 13:35:10 +0100 ** Changed in: sysvinit (Ubuntu) Status: Fix Committed = Fix Released -- fsck/usplash: device names not fully reported https://bugs.launchpad.net/bugs/203323 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 203323] Re: fsck/usplash: device names not fully reported
- When pressing ESC, do not kill the logsave command (since this does not reliably kill the subprocess), but the fsck.ext[23] processes directly. (LP: #203322) The following attached bug should address this issue in logsave as well. It may help you since otherwise you're probably having to do some grody things to get the fsck.ext[234] pid. Also, please see the souceforge bug for some patches I'd like you to evaluate to see if they address the problems from the fsck/e2fsck side. Thanks!! ** Attachment added: 0001-logsave-Pass-any-SIGTERM-or-SIGENT-signals-to-child.patch http://launchpadlibrarian.net/12895039/0001-logsave-Pass-any-SIGTERM-or-SIGENT-signals-to-child.patch -- fsck/usplash: device names not fully reported https://bugs.launchpad.net/bugs/203323 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 203323] Re: fsck/usplash: device names not fully reported
** Changed in: sysvinit (Ubuntu) Status: New = In Progress -- fsck/usplash: device names not fully reported https://bugs.launchpad.net/bugs/203323 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
