Comment 11 for bug 523484

Thanks... but İ'm not sure İ understand what to do ;-)

Regars,

Olivier

________________________________
De : Scott James Remnant <email address hidden>
À : <email address hidden>
Envoyé le : Lun 17 mai 2010, 19h 33min 21s
Objet : [Bug 523484] Re: ureadahead requires /var on root filesystem

The reason that the files are clumbed in /var/lib/ureadahead right now
is that it needs to be easy to wipe them for reprofiling. Constant-
reprofiling would mean we could just put the pack in
$MOUNTPOINT/.ureadahead or something

The need for the temporary /var/lib/ureadahead/debug mount goes away too
since /sys is now always mounted on boot by the kernel/init daemon

--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You received this bug notification because you are a direct subscriber
of a duplicate bug.

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 unsubscribe from this bug, go to:
https://bugs.launchpad.net/ureadahead/+bug/523484/+subscribe