Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#27622 - [initscripts] Problems with unmounting HDDs after initscript updates

Attached to Project: Arch Linux
Opened by Mathias Anselmann (matse) - Monday, 19 December 2011, 02:56 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 25 January 2012, 11:00 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Today I did a system update (just one package - initscripts) and at the next boot I realized a "recovering journal" message. I had a look at my /var/log/boot and realized that there is a coherence with the initscript updates and the "recovering journal" messages in my boot log:

Extracts of my boot log:
Sun Nov 13 05:36:16 2011: myboot: recovering journal

Wed Nov 23 22:56:24 2011: myboot: recovering journal
Wed Nov 23 22:56:24 2011: /dev/mapper/myvg1-lvdl: recovering journal

Mon Dec 19 03:22:02 2011: myboot: recovering journa
Mon Dec 19 03:22:02 2011: /dev/mapper/myvg1-lvdl: recovering journal

And here my pacman.log:
[2011-11-13 04:42] installed initscripts (2011.10.2-1)
[2011-11-18 17:02] upgraded initscripts (2011.10.2-1 -> 2011.11.3-1)
[2011-12-19 03:20] upgraded initscripts (2011.11.3-1 -> 2011.12.1-1)


At least it might be possible that these two things correlate.
I use a luks encrypted root partition and on top of it is a lvm.
This task depends upon

Closed by  Tom Gundersen (tomegun)
Wednesday, 25 January 2012, 11:00 GMT
Reason for closing:  No response
Comment by Mathias Anselmann (matse) - Monday, 19 December 2011, 03:03 GMT
As requested here is some additional info:
My whole boot log: http://paste.xinu.at/mnd8/
My fstab: http://paste.xinu.at/iMk/
My rc.conf: http://paste.xinu.at/NNu/
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 19 December 2011, 05:36 GMT
Oops I voted accidentally, instead of watching.
Comment by Tom Gundersen (tomegun) - Monday, 19 December 2011, 08:24 GMT
@matse: are you able to reproduce this, or was it a one-off? Does it happen on every reboot or just some reboots?
Comment by Andrew Gaydenko (student975) - Monday, 19 December 2011, 08:43 GMT
At my case I have met /var (checking/restoring from journal) once only - on rebooting just after initscripts upgrading. Next reboot was clean.
Comment by Tom Gundersen (tomegun) - Monday, 19 December 2011, 08:50 GMT
@student975:
Probably what is happening is that there is a bug when /etc/mtab is not a symlink. However, as of this release we force /etc/mtab to become a symlink on next reboot so the problem would only occur once. At the moment I cannot see a clean way to fix this (creating the symlink at install/shutdown creates problems of its own), but suggestions (preferably in the form of patches) are welcome :-)
Comment by Andrew Gaydenko (student975) - Monday, 19 December 2011, 08:58 GMT
Are there real file systems demanding that clean way at all (I mean file systems which are unable to restore on next boot)? :) I have post a message just for information (as a use case), but I didn't vote the task. Also at my case there were tmpfs for /var/lock and /var/run - as described here: https://bbs.archlinux.org/viewtopic.php?id=132127
Comment by Mathias Anselmann (matse) - Monday, 19 December 2011, 09:03 GMT
@tomegun: It happened to me after every initscripts update since I use luks with lvm (about beginning of november this year), and just after these update. All other reboots are fine (I don't know whether I had this issue already without luks and lvm).
I do not yet really get why unmounting isn't working as expected, here /etc/mtab is a symlink to /proc/self/mounts - does an initscripts update change /etc/mtab?
Comment by Tom Gundersen (tomegun) - Monday, 19 December 2011, 09:12 GMT
@matse: before /etc/mtab was recretade by initscripts on every boot. As of this release we just symlink it to /proc/self/mounts if it was not already. This means that your mtab will probably be changed on the first reboot after upgrading (assuming it used to be a regular file) and from then on all shutdowns should be fine.
"Every initscripts update since November this year" should be this one and one more, is that correct?
Comment by Mathias Anselmann (matse) - Monday, 19 December 2011, 09:14 GMT
@tomegun: Oh I see, thanks for the explanation! And no, it was this one and two more (first time I realized it was with initsripts update to 2011.10.2-1).
Comment by Tom Gundersen (tomegun) - Monday, 19 December 2011, 09:16 GMT
@matse: ok, thanks for the info. It is a bit odd that this has happened three times in a row. I hope this will be the last ;-) (Yell if not!)
Comment by Mathias Anselmann (matse) - Monday, 19 December 2011, 09:18 GMT
@tomegun: OK. Thanks for the support, I will have a look at it and report here if I ever get the issue again.

//Edit: Just were reminded today of this issue (when it was closed) and want to report that last two initscripts updates both worked fine and the issue didn't occur again!

Loading...