kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #124804
[Bug 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory
http://paste.ubuntu.com/11768305/
That link shows upstart-monitor output during the libc6 upgrade. I see
the mountall job starting, then later I see a mounted event for /tmp
which triggers the mounted-tmp job, which is what ends up clearing out
/tmp. In fact, generally it looks to me like many of the startup jobs
are running, so I suspect upstart must be emitting a startup event.
Just glancing briefly at the upstart code, it seems to support a restart
flag to be passed on reexec which would prevent the startup event from
being emitted. The logic is a bit weird though - on re-exec upstart only
seems to pass --restart if the current upstart isn't a re-exec ... so if
you re-execed twice you don't want the flag?
Anyway, I think at this point I'll throw it back over to Steve, as I
don't see any evidence at all that this is a kernel issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1464442
Title:
installing or upgrading libc6 in Trusty removes all content from /tmp
directory
Status in eglibc package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Incomplete
Bug description:
We are seeing an issue with installation of dkms package during a
curtin installation which ends up with /tmp directory being wiped
clean. This is very bad for curtin as it saves critical installation
files in /tmp.
It turns out that it's the of upgrading libc6, which is triggered as a
result of installing dependencies, that removes content of /tmp. For
example, installation of gcc results in the same result since it ends
up with libc6 being upgraded. The only way that this won't be
recreated is if the latest libc6 is already installed.
This problem does not exist in precise. It can also be recreated by
installing the .deb file for any version in trusty including 2.17.
========================================================================
ubuntu@host:~$ ls /tmp
tmpHHbRkP
ubuntu@sirrush:~$ sudo apt-get install libc6
sudo: unable to resolve host sirrush
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libc-dev-bin libc6-dev
Suggested packages:
glibc-doc
Recommended packages:
manpages-dev
The following packages will be upgraded:
libc-dev-bin libc6 libc6-dev
3 upgraded, 0 newly installed, 0 to remove and 148 not upgraded.
Need to get 6,714 kB of archives.
After this operation, 6,144 B disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6-dev amd64 2.19-0ubuntu6.6 [1,910 kB]
Get:2 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc-dev-bin amd64 2.19-0ubuntu6.6 [68.9 kB]
Get:3 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6 amd64 2.19-0ubuntu6.6 [4,735 kB]
Fetched 6,714 kB in 0s (18.5 MB/s)
Preconfiguring packages ...
(Reading database ... 57798 files and directories currently installed.)
Preparing to unpack .../libc6-dev_2.19-0ubuntu6.6_amd64.deb ...
Unpacking libc6-dev:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
Preparing to unpack .../libc-dev-bin_2.19-0ubuntu6.6_amd64.deb ...
Unpacking libc-dev-bin (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
Preparing to unpack .../libc6_2.19-0ubuntu6.6_amd64.deb ...
Unpacking libc6:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
Processing triggers for man-db (2.6.7.1-1) ...
Setting up libc6:amd64 (2.19-0ubuntu6.6) ...
Setting up libc-dev-bin (2.19-0ubuntu6.6) ...
Setting up libc6-dev:amd64 (2.19-0ubuntu6.6) ...
Processing triggers for libc-bin (2.19-0ubuntu6.3) ...
ubuntu@host:~$ ls /tmp
ubuntu@host:~$
========================================================================
This is very recreatable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+subscriptions