[Bug 523484] Re: ureadahead requires /var on root filesystem
rollercoaster
523484 at bugs.launchpad.net
Thu Jan 5 13:36:00 UTC 2012
The fix linked in #29 is better and easier. I don't like to have variable files on / . Thats why we use seperate /var partitions ;)
This is the change to the upstart conf:
sudo sed -i 's+^start on starting mountall+start on mounted MOUNTPOINT=/var+' /etc/init/ureadahead.conf
@Alf Gaida
heretic question: is ureadahead installed in Ubuntu Server? ;)
But I'm also very disappointed of 10.04. It should not be called LTS, it
should be called "Unsupported". I think we can wait until "zappy zebra"
for this to be fixed.
--
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
More information about the foundations-bugs
mailing list