Four years passed...
Seriously?
Trusty will be the third LTS release with the bug. What is the point to use LTS
releases if such pure-Ubuntu bugs are not fixed fore years?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Sun, 2014-02-23 at 14:00 +, Pavel Malyshev wrote:
Four years passed...
What is the point to use LTS releases if such pure-Ubuntu bugs are not fixed
fore years?
I asked myself that same question a while ago. This was my
conclusion/solution:
$ cat /etc/issue
Fedora release 20
This bug exists for me in 14.04 alpha. All my top level root folders are
mounted on a single ext4 partition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523484
Title:
ureadahead requires /var on
Addendum to post #52, running the command given in post #50 fixed the
issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523484
Title:
ureadahead requires /var on root filesystem
To
Targeting this to 13.11, this bug got mentioned a few times on IRC over
the past week in relation to Ubuntu Touch.
The current consensus is that Clint's idea (comment #34) is the best way
to fix this in a generic way and that fix should definitely be
implemented for 14.04 LTS.
** Changed in:
Just a reminder this is still a issue in raring (13.04) and this command fixed
it
sudo sed -i 's+^start on starting mountall+start on mounted MOUNTPOINT=/var+'
/etc/init/ureadahead.conf
ureadahead should check is /var is ready then continue, so the above
would not be needed
i also get status
So 2 years passed and this bug does not even have an assignment...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523484
Title:
ureadahead requires /var on root filesystem
To manage notifications
There is a clear statement from JSR: There will be a fix eventually.
Sooner or later. This was 2 years ago ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523484
Title:
ureadahead requires /var
Why ureadahead does not have an option to change pack storage directory?
This bug can be workarounded easily if I'm able to create /ureadahead and set
that option in ureadahead-other.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm currently running 11.10 and worked around the problem by copying
/var/lib/ureadahead to / and the pointing a /var/lib/ureadahead symlink
to /ureadahead both in the /var partition and from the root partition
(accessed using the bind mount trick in comment 17). Now, when I next
I'll get to see
The bug is still there in 12.04...
it seems that nothing has been done about it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523484
Title:
ureadahead requires /var on root filesystem
To
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
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
@rollercoaster
i finally fixed the problems with ubuntu ureadahead, mdadm, mountall and
plymouth. i run my servers on debian stable or sid. ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523484
FYI: to mr Wait for it to be fixed in Maverick ;-): the bug is still
there on Oneiric.
A fix on the line of #17 works nice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523484
Title:
ureadahead
@Maxim #39
The basic idea seems good, but there are more reliable ways to detect a
separate /var partition:
! mountpoint -q /var || sed -i 's|^start on starting mountall|start on
mounted MOUNTPOINT=/var|' /etc/init/ureadahead.conf
--
You received this bug notification because you are a member
I suppose this could easily be fixed within the package scripts. Just
let the scripts check if the package is installed on a system with
separate /var and modify the to be installed init file accordingly.
I currently use something like this in a local standalone postinstall
script, i guess it
This is still an issue in Ubuntu Server 11.04.
Isn't it a relatively common use case for /var to be on its own
partition on a server?
Either fix the ureadahead behavior, or eliminate it from the server
builds entirely. Most server admins don't care much about boot speed,
but they do care about
Is this another bug, which will never be fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523484
Title:
ureadahead requires /var on root filesystem
To manage notifications about this bug go
On 11-06-12 02:10 AM, afunix wrote:
Is this another bug, which will never be fixed?
Seems so. Throw it on the every growing pile. Like the NFS4/KRB5 bug
that has been ignored for going on (or is it over?) 6 months now.
TBH, I am starting to look at different distros. I am getting tired of
I am running 11.04 64-bit and also have /var as a separate partition.
Not only ureadahead(-other) but others such as dbus, gdm and dpkg cannot
create files under /var/lib since the required directories are non-
existent. The last thing I remember doing before boot failure was
software upgrade this
I just have a couple of thoughts on this bug.
* The earlier comment that ureadahead could just buffer this in memory
and write later wouldn't be all that difficult to implement. The
potential for a lot of data is unknown to me (on my two systems I
checked, the file is around 700kb), so that may
@hedgehog#29
Brillant simple patch! Works like a charm now.
--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I had this problem, trying to boot Ubuntu 10.04 from a mirrored GPT
system, failed until I moved var back to the / partition. Then it worked
fine.
--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You received this bug notification because you are a member of
So, if ureadahead is not the guilty party, who is?
I have a few 10.04 LTS servers which I have configured with separated
/var and they have been working fine so far knock on wood.
I have another 10.04 LTS machine in which I created a separate partition
for /var but forgot to configure it during
On Sat, 2010-10-30 at 04:59 +, hedgehog wrote:
and if you want to track another bug report:
[URL=https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/542334][B]boot
fails [...] ureadahead [...] terminated with status 5[/B][/URL]
Why would I want to track that bug report? It's
This **very** simple fix worked for me:
[URL=http://ubuntuforums.org/showpost.php?p=9555086postcount=9][B]sentinella86[/B][/URL]
and if you want to track another bug report:
[URL=https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/542334][B]boot
fails [...] ureadahead [...] terminated
Actually Brian I have a case like narcelio, I installed a fresh copy of
Ubuntu 10.10 and created a separate partition for /var. After I tried to
reboot and got unreadahead main process (336) terminated with status 5
and after that it just doesnt complete the booting process. The monitor
comes off.
On Tue, 2010-10-26 at 20:31 +, Ainsley Harewood wrote:
After I tried to
reboot and got unreadahead main process (336) terminated with status 5
and after that it just doesnt complete the booting process.
Right. This is a known and common problem. It's not caused by
ureadahead though.
@Ainsley Harewood:
There is a simple proof that ureadahead don't harm your boot process. Chroot
into the machine and purge ureadahead. Then reboot. If the machine dont boot,
solve the problem. If the machine boot, your problem is solved.
To clearify some things: In a perfect world ureadahead
So ureadahead will never support configurations with separate /var ?
Can this be fixed in upstart configuration with start on mounted DEVICE=[/UL]*
MOUNTPOINT=/var as suggested in original bug description?
--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You
Any proof of a link with ureadahead? Would be interesting for others to
give some details on this (first, to know if we can make a migration
with /var on another part).
--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You received this bug notification
On Mon, 2010-10-25 at 01:53 +, narcelio wrote:
I´ve just upgraded my Ubuntu 10.04 to 10.10 and it can't boot anymore.
Which you must be assuming is a problem with ureadahead, yes, or you
would not be posting to this bug.
More than likely your bug is not with ureadahead but one of the many
I´ve just upgraded my Ubuntu 10.04 to 10.10 and it can't boot anymore.
--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
To combine those last two comments, instead of using:
rm -rf /var/lib/ureadahead
I went for:
mv /var/lib/ureadahead /.ureadahead
which took an existing debugfs directory with it. That was the only
content of the directory at the time. Other than that it all seems to be
working fine, although
Will the bug be fixed for Maverick or is Maverick going to bet still
another release where running a system (sanely IMHO) with /var on a
separate partition is just not a supported configuration?
A separate /var is not a supported configuration. LOL.
--
ureadahead requires /var on root
michel that is a great solution and worked for me (separate /var
filesystem).
there is one thing missing though:
mkdir /.ureadahead/debugfs
-matt
--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You received this bug notification because you are a member
A simple fix for this problem:
1. Create directory to store data in root filesystem: mkdir /.ureadahead
2. Mount your root fs somewhere, to be able to access it: mount / /mnt/tmp -o
bind
3. Make two links to the new storage location:
rm -rf /var/lib/ureadahead
ln -s /.ureadahead
'I gotta say, it gets pretty tiring to continually be upgrading Ubuntu
releases only to find a whole bag of problems that will be fixed in the
next release'
Welcome to linux. On the other hand, you didn't pay for it. On the third
hand, half the problem here is that linux lets you see these error
One thing to add, though: you guys REALLY should be testing with var as
a separate partition. The whole reason for var is that it is files which
grow and change, and the reason for splitting it off from the rest of
the filesystem was so that you can put it on its own partition and not
have it
Thanks... but İ'm not sure İ understand what to do ;-)
Regars,
Olivier
De : Scott James Remnant sc...@canonical.com
À : omeunier2...@yahoo.fr
Envoyé le : Lun 17 mai 2010, 19h 33min 21s
Objet : [Bug 523484] Re: ureadahead requires /var on root filesystem
On Tue, 2010-05-18 at 08:11 +, Oliv' wrote:
Thanks... but İ'm not sure İ understand what to do ;-)
Wait for it to be fixed in Maverick ;-)
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You received
On Tue, 2010-05-18 at 10:03 +, Scott James Remnant wrote:
Wait for it to be fixed in Maverick ;-)
You are kidding right? Please tell me you are kidding.
I gotta say, it gets pretty tiring to continually be upgrading Ubuntu
releases only to find a whole bag of problems that will be fixed
On Tue, 2010-05-18 at 10:34 +, Brian J. Murrell wrote:
You are kidding right? Please tell me you are kidding.
I gotta say, it gets pretty tiring to continually be upgrading Ubuntu
releases only to find a whole bag of problems that will be fixed in the
next release.
It's pretty tiring
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
[SOLVED] OK, so you thought you were smart and installed Ubuntu with
/var on its own partition so that way runaway log files can't take down
your whole system. (wasn't this theory valid back when hard drives we
measured in Megabytes?)
Well I am that smart guy and I got the readahead error.
Here
On Sat, 2010-05-15 at 13:26 +, Trey WebStandardCSS Brister wrote:
Well I am that smart guy and I got the readahead error.
Not smart enough... :-)
Boot to Ubuntu live CD
Not needed. If you want access to what's in the /var that's on the root
filesystem (i.e. what's under the /var that
Hi there.
If have the same issue on my server system with new lucid installed.
Every 10. boot or so the system hangs up and must be killed.
This could possibly be linked to this issue here.
--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You received this
So what's up now? Is there a workaround?
Should it be removed from installations with /var as separate partition?
The FHS only really allows us /var to store things like this, sadly
Does this mean there won't be any fix at all?
--
ureadahead requires /var on root filesystem
~sigh~ Yet another bug with regard to boot-up and separate /var. Would
it be at all possible for the users/developers/testers of all of this
bootup (i.e. upstart, mountall, etc.) software to routinely build their
(test) systems with a separate /var? This seems like an all-too-common
use-case
Can ureadahead collect data in memory until /var/lib/ureadahead becomes
ready?
--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
The FHS only really allows us /var to store things like this, sadly
** Summary changed:
- ureadahead.conf assumes that /var/lib/ureadahead is available on startup
+ ureadahead requires /var on root filesystem
** Changed in: ureadahead (Ubuntu)
Importance: Undecided = Medium
** Changed in:
52 matches
Mail list logo
