[Bug 523484] Re: ureadahead requires /var on root filesystem

[Nicolas Michel]

Still there. On a production server (maverick). As you know, production
servers are always setup with separated /var, /home, /tmp to make it
stronger to disks full ...

Not really clean indeed seing all these errors at the boot process ...
Even if it doesn't hurt.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/523484

Title:
  ureadahead requires /var on root filesystem

Status in über-readahead:
  Invalid
Status in “ureadahead” package in Ubuntu:
  Triaged

Bug description:
  I have the following mountpoints defined that use different
  partitions:

  /
  /boot
  /home
  /opt
  /usr
  /var

  These nodes are located on different partitions to enable greater control over the system and prevent unusable states.
  ureadahead.conf uses the following event:
    start on starting mountall
  Which fails for me since /var is not yet mounted when mountall starts leading to ureadahead errors about missing pack files.

  ureadahead-other.conf in turn uses
    start on mounted DEVICE=[/UL]* MOUNTPOINT=/?
  I have yet to find out what that means but I see that ureadahead-other is terminated with error status 4 (i.e. no pack file)

  I think that ureadahead configuration files should be ready for such kind of layout.
  I have fixed the first item by rewriting the rule as start on mounted MOUNTPOINT=/var but I don't know what to do with second item.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ureadahead/+bug/523484/+subscriptions