Since it seems this bug manifests itself only after certain 'apt upgrade' runs
that call ureadahead triggers, would backporting the fix from Vivid ureadahead
package ver. 0.100.0-19 be an option to resolve it?
I'm thinking of the fix for
For me it's the mtab entry for tracefs on a non-existing mount point in
/var/lib/ureadahead/debugfs/tracing that is causing problems. It does
affect VMware snapshots when quiescing is required too.
Since it's a different entry then in this post I opened a new bug report
in #1659684
--
You
Just to note, 'mountall' also clears that mtab entry, but it also nukes
contents of /tmp in the process, which might not be good if someone is
running Passenger, which apparently keeps socket files in there (i.e.
/tmp/passenger.1.0.xxx/generation-0/request )
--
You received this bug notification
Public bug reported:
After a patching and a reboot cycle (possibly only the ones that involve
running ureadahead triggers) a leftover mount entry is present in
/etc/mtab pointing to /var/lib/ureadahead/debugfs/tracing
root@localhost:~$ mount
/dev/mapper/sysvg-root on / type ext4
4 matches
Mail list logo
