Bug#677097: mountall-bootclean.sh nukes udev's data in /run

June 11th, 2012 - 12:30 pm ET by Jakub Wilk | Report spam
Package: initscripts
Version: 2.88dsf-27
Severity: important
Usertags: serious

mountall-bootclean.sh removes files from /run, but these may include
files created by init scripts earlier in the same boot process. I
observed this because the script nuked files in /run/udev/, leaving my X
server without any input devices.

(In case you have trouble reproducing this, adding an artifical sleep of
a few seconds to mountall-bootclean.sh should ease triggering the
problem.)


Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.3.0-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initscripts depends on:
ii coreutils 8.13-3.2
ii debianutils 4.3.1
ii libc6 2.13-33
ii lsb-base 4.1+Debian6
ii mount 2.20.1-5
ii sysv-rc 2.88dsf-27
ii sysvinit-utils 2.88dsf-27

Versions of packages initscripts recommends:
ii e2fsprogs 1.42.2-2
ii psmisc 22.17-1

Jakub Wilk



To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 2 repliesReplies Make a reply

Similar topics

Replies

#1 Roger Leigh
June 16th, 2012 - 01:20 pm ET | Report spam
On Mon, Jun 11, 2012 at 06:20:45PM +0200, Jakub Wilk wrote:
mountall-bootclean.sh removes files from /run, but these may include
files created by init scripts earlier in the same boot process. I
observed this because the script nuked files in /run/udev/, leaving
my X server without any input devices.

(In case you have trouble reproducing this, adding an artifical
sleep of a few seconds to mountall-bootclean.sh should ease
triggering the problem.)



This is definitely with -27? All init scripts are current, with no
versions from earlier releases being held back?

This was supposed to have been fixed in -24, in commit 32d0678.
Did you have a /run/.clean flagfile created prior to
mountall-bootclean running?

I'll try reproducing with the sleep (might be later in the week; I'm
about to set off to a conference).


Thanks,
Roger

.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800



To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Replies Reply to this message
#2 Jakub Wilk
June 16th, 2012 - 03:10 pm ET | Report spam
* Roger Leigh , 2012-06-16, 18:10:
mountall-bootclean.sh removes files from /run, but these may include
files created by init scripts earlier in the same boot process. I
observed this because the script nuked files in /run/udev/, leaving my
X server without any input devices.

(In case you have trouble reproducing this, adding an artifical sleep
of a few seconds to mountall-bootclean.sh should ease triggering the
problem.)



This is definitely with -27?



Yes.

All init scripts are current, with no versions from earlier releases
being held back?



Yes.

This was supposed to have been fixed in -24, in commit 32d0678.
Did you have a /run/.clean flagfile created prior to mountall-bootclean
running?



No, and /run/.tmpfs didn't exist either.

As far as I can see, it's because /etc/init.d/bootmisc.sh removed the
flag files before mountall-bootclean.sh was run.

Jakub Wilk



To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
email Follow the discussion Replies Reply to this message
Help Create a new topicReplies Make a reply
Search Make your own search