Reiserfs not terminating properly, results in 'trans replayed' at next boot.

[Szebenyi Bálint]

Description: Ubuntu 12.10
Release: 12.10

reiser4progs:
  Telepítve: (nincs)
  Jelölt: 1.0.7-6.3fakesync2
  Verziótáblázat:
     1.0.7-6.3fakesync2 0
        500 http://hu.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages

reiserfsprogs:
  Telepítve: 1:3.6.21-1build2
  Jelölt: 1:3.6.21-1build2
  Verziótáblázat:
 *** 1:3.6.21-1build2 0
        500 http://hu.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
        100 /var/lib/dpkg/status

An up to date systemd as of 2012. 10. 31.

Upon shutdown I see that 'waiting for all processes to terminate [fails]', upon booting I can see that lots of trans replayed items delay booting which comes from abnormal reiserfs shutdown. This is a fresh ubuntu install, with lvm on luks configuration.
/var is on reiserfs, all the others are on ex4.
Apart from this slow boot everything is OK, however this is not too good in the long run.

Are there any logs I can help you with? (I just don't know where they are)

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1073568/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Szebenyi Bálint (szebenyib)]

I believe that is has something to do with upstart. Where I have written systemd consider it to be upstart, I just thought that ubuntu uses systemd, it looked similar.

[Szebenyi Bálint (szebenyib)]

This bug still persist and it delays my boot by a long time (a minute or so). Could somebody at least give an advice where to start looking for a solution?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Szebenyi Bálint (szebenyib)]

This is all I could get from /var/log/kern.log:

[code]
Jan 5 21:43:12 moon kernel: [ 85.113833] REISERFS (device dm-6): found reiserfs format "3.6" with standard journal
Jan 5 21:43:12 moon kernel: [ 85.113843] REISERFS (device dm-6): using ordered data mode
Jan 5 21:43:12 moon kernel: [ 85.113845] reiserfs: using flush barriers
Jan 5 21:43:12 moon kernel: [ 85.128061] REISERFS (device dm-6): journal params: device dm-6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Jan 5 21:43:12 moon kernel: [ 85.128330] REISERFS (device dm-6): checking transaction log (dm-6)
Jan 5 21:43:12 moon kernel: [ 85.204864] REISERFS (device dm-6): Using r5 hash to sort names
Jan 5 21:43:12 moon kernel: [ 86.004945] type=1400 audit(1357418591.727:11): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=1168 comm="apparmor_parser"
Jan 5 21:43:12 moon kernel: [ 86.005354] type=1400 audit(1357418591.731:12): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1168 comm="apparmor_parser"
Jan 5 21:43:12 moon kernel: [ 86.005565] type=1400 audit(1357418591.731:13): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=1168 comm="apparmor_parser"
Jan 5 21:43:12 moon kernel: [ 86.144426] type=1400 audit(1357418591.867:14): apparmor="STATUS" operation="profile_load" name="system_tor" pid=1169 comm="apparmor_parser"
Jan 5 21:43:12 moon kernel: [ 86.167980] type=1400 audit(1357418591.891:15): apparmor="STATUS" operation="profile_load" name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper" pid=1166 comm="apparmor_parser"
Jan 5 21:43:12 moon kernel: [ 86.168288] type=1400 audit(1357418591.891:16): apparmor="STATUS" operation="profile_load" name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper//chromium_browser" pid=1166 comm="apparmor_parser"
Jan 5 21:43:12 moon kernel: [ 86.169819] type=1400 audit(1357418591.895:17): apparmor="STATUS" operation="profile_load" name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-uccsconfigure/uccsconfigure-session-wrapper" pid=1167 comm="apparmor_parser"
Jan 5 21:43:12 moon kernel: [ 86.170219] type=1400 audit(1357418591.895:18): apparmor="STATUS" operation="profile_load" name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-uccsconfigure/uccsconfigure-session-wrapper//chromium_browser" pid=1167 comm="apparmor_parser"
Jan 5 21:43:12 moon kernel: [ 86.170610] type=1400 audit(1357418591.895:19): apparmor="STATUS" operation="profile_load" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=1165 comm="apparmor_parser"
Jan 5 21:43:12 moon kernel: [ 86.170959] type=1400 audit(1357418591.895:20): apparmor="STATUS" operation="profile_load" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser" pid=1165 comm="apparmor_parser"
Jan 5 21:43:13 moon kernel: [ 87.414285] ppdev: user-space parallel port driver
Jan 5 21:43:14 moon kernel: [ 88.824617] vboxdrv: Found 4 processor cores.
Jan 5 21:43:14 moon kernel: [ 88.825121] v...

[Szebenyi Bálint (szebenyib)]

Managed to take a shot from my laptop when shutting down. See attached the image.

[Steve Langasek (vorlon)]

If the 'killing all remaining processes' step has failed, then you have some processes on your system, not managed by upstart, that are either deadlocked or are respawning and preventing themselves from being killed. In either case, upstart does the best it can to shut down anyway, but when processes are misbehaving and trying to avoid shutting down, this sometimes means an unclean filesystem.