I'm still experiencing the problem that aufs is mounted before the
underlying mount is ready:
Snippet from mountall debug log (see full log in attachment)
update_mount: /var/lock: /var/lock none tmpfs nodev,noexec,nosuid,showthrough
update_mount: /media/aufs: /media/aufs none aufs
br:/media/sdb1
Hi,
I've also seen this problem on my system, where I use AUFS overlays over
squashfs filesystems. I'm not sure if I understand the ubuntu-boot ppa
page correctly, in that there doesn't seem to be any mention of updated
mountall there but I am under the impression that the fixes mentioned in
this
Hi
forget what I said about "the 0.2.0~boot4 does not return, it has to be killed
with ctrl+c".
I was not aware of it is working in the foreground, so I killed it.
The issue involved in this bug is solved.
Thanks,
Vicenç.
--
aufs fstab entries require ordering logic
https://bugs.launchpad.net/
On Sat, 2009-10-10 at 12:51 +, vj wrote:
> Here it is, hope it helps.
>
> ** Attachment added: "mountall--debug.txt"
>http://launchpadlibrarian.net/33404847/mountall--debug.txt
>
Unfortunately this is significantly truncated :-(
How did you terminate mountall?
Scott
--
Scott James Rem
Here it is, hope it helps.
** Attachment added: "mountall--debug.txt"
http://launchpadlibrarian.net/33404847/mountall--debug.txt
--
aufs fstab entries require ordering logic
https://bugs.launchpad.net/bugs/433537
You received this bug notification because you are a member of Ubuntu
Bugs, whic
On Fri, 2009-10-09 at 17:30 +, vj wrote:
> Yes, it's still running after boot
> I've stopped it and executed again with the --debug option.
> The result is the same as version 0.2.0~boot2 (few lines changed their order
> relative to version 0.2.0~boot4).
> Nothing is printed after it stops, n
Yes, it's still running after boot
I've stopped it and executed again with the --debug option.
The result is the same as version 0.2.0~boot2 (few lines changed their order
relative to version 0.2.0~boot4).
Nothing is printed after it stops, neither after ctrl+c hit.
--
aufs fstab entries require
This bug was fixed in the package mountall - 0.2.0
---
mountall (0.2.0) karmic; urgency=low
[ Colin Watson ]
* Always check the root filesystem if --force-fsck is used, regardless of
passno. LP: #435707.
[ Johan Kiviniemi ]
* Have each fsck instance create a lock for eac
On Fri, 2009-10-09 at 14:03 +, vj wrote:
> * the 0.2.0~boot4 does not return, it has to be killed with ctrl+c
> When tried to boot the new version it worked fine.
>
After booting, if you run "sudo status mountall" is it still running?
If so, could you run "sudo stop mountall", then "sudo mo
Hi,
there are two differences between mountall 0.2.0~boot2 and 0.2.0~boot4 debug
file:
* pid numbers
* lines "update_mount" related to the aufs mount appear two lines later
and one difference in behavior:
* the 0.2.0~boot4 does not return, it has to be killed with ctrl+c
When tried to boot the
Sorry about the issues with the previous PPA versions, as usual things
worked just fine when I tested it in the various rigs I have here - of
course it flatly failed when installed on normal systems because I
hadn't actually tested that ;)
I've uploaded a new ~boot4 version, this one feels much be
On Thu, 2009-10-08 at 15:04 +, vj wrote:
> I'he tried to execute mountall --debug (version 0.2.0~boot2) on an already
> started system and it worked ok. The result is attached.
> But when I tried to boot the system it hanged with the following error:
> rm: cannot remove /focefsck: Read-only
Hi,
I'he tried to execute mountall --debug (version 0.2.0~boot2) on an already
started system and it worked ok. The result is attached.
But when I tried to boot the system it hanged with the following error:
rm: cannot remove /focefsck: Read-only file system
init: mountall post-stop process (3
I've uploaded a new mountall package to the ubuntu-boot PPA:
https://launchpad.net/~ubuntu-boot/+archive/ppa
I would appreciate it if you could install this and try it out.
*BEFORE* you reboot though, could you run "sudo mountall --debug >
mountall.log 2>&1" and attach that to this bug - then aft
** Branch linked: lp:~ubuntu-core-dev/ubuntu/karmic/mountall/ubuntu
--
aufs fstab entries require ordering logic
https://bugs.launchpad.net/bugs/433537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
** Changed in: mountall (Ubuntu Karmic)
Status: In Progress => Fix Committed
--
aufs fstab entries require ordering logic
https://bugs.launchpad.net/bugs/433537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
** Changed in: mountall (Ubuntu)
Status: Triaged => In Progress
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
** Changed in: mountall (Ubuntu)
Milestone: None => ubuntu-9.10
** Also affects: mountall (Ubuntu Karmic)
Importance: Medium
Actually, let's just re-use this bug for the aufs ordering issue
** Changed in: mountall (Ubuntu)
Importance: Undecided => Medium
** Changed in: mountall (Ubuntu)
Status: Won't Fix => Triaged
--
aufs fstab entries require ordering logic
https://bugs.launchpad.net/bugs/433537
You recei
18 matches
Mail list logo
