bind mounts cause lots of "init: ureadahead-other main process (1234) terminated with status 4" messages

Bug #502837 reported by Martin Pitt
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
ureadahead (Ubuntu)
New
Low
Unassigned

Bug Description

Binary package hint: ureadahead

During boot, I get some 25 messages

  init: ureadahead-other main process (1234) terminated with status 4

(with different pids). These seem to come from the "start on mounted" rule in /etc/init/ureadahead-other.conf when the boot process does all the bind mounts in my /etc/fstab

  $ grep bind /etc/fstab
  /home /home/dchroot/sid/home none bind 0 0
  [... 28 of those ...]

Is there a possibility to refine the upstart rule to not trigger on bind mounts?

Martin Pitt (pitti)
Changed in ureadahead (Ubuntu):
importance: Undecided → Low
Revision history for this message
Bob Hill (hill-robert) wrote :

During Ubuntu 09.10 boot, the message "init: ureadahead-other main
process (473) terminated with status 4" also appears on my system.

/etc/fstab is as follows:
     /dev/sda3 / ext4 errors=remount-ro 0 1
     /dev/sda6 /d ext3 defaults 0 2
     /dev/sda5 swap swap sw 0 0
     tmpfs /tmp tmpfs defaults 0 0
Note /dev/sda6 is a data partition. The rest is self-explanatory.

/var/lib/ureadahead contains TWO pack files:
     "pack" (presumably for the root file system);
     "tmp.pack" (presumably for the /tmp file system).
/var/lib/ureadahead does NOT contain a pack file named "d.pack".

Ubuntu Bug 432360 contains the following text:
"ureadahead has better support for separate filesystems, when
 tracing it will generate additional pack files for each of the
 separate mounts (each one individually optimised) - and uses
 the mountall-generated 'mount' event to run over those."

How can I investigate why ureadahead generates pack files for
the root and /tmp file systems, but not for the /d file system?

Revision history for this message
Lars Ola Liavåg (l-liavag) wrote :

I too have the mentioned boot messages.

Revision history for this message
nullservice (itanium128) wrote :

is this resovled? my box can not boot!!!Not even single user mode!

My box is dell precision 340, I am jumping upgrading from 8.04 to 10.04 with ubuntu i686

the system hangs after a full screen of udev warnings(after I tried my method 3 in the following, before is the same as Daniel Añez Scott 's screen shot! )

my system is upto today's upstart package and ureadahead package.
I have separated /boot / /tmp on different partions as
sda1 /boot
sda2 swap
sda3 /tmp
sda5 /
sda6 /home

I tried the following, none of them work

1,change /etc/ureadahead.con and made it mount on localfilesystem
2, disable non critical partitions in /etc/fstab while only keep /boot / partitions
3 change /etc/ureadahead.conf to normal exit with status 0 and 4

Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

@nullservice If your system can't boot, that's a separate bug which you should file. This bug is purely cosmetic.

Revision history for this message
Marco Diaz (zethabyte) wrote :

I tried everything, but nothing I can fix this problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.