[Bug 382842] Re: aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3
We found this to be a race condition supposedly within aufs. The script
that mounts the overlay does the following:
# perform the aufs root mount
modprobe aufs
mount -t aufs -o br:${localroot}=rw:${netroot}=nfsro aufsroot ${rootmnt}
Doing this results in the described problem - df reports 0 bytes free on
${rootmnt}.
The fix is rather easy while a little annoying:
# perform the aufs root mount
modprobe aufs
# wait a second to avoid a race condition; see
https://bugs.launchpad.net/bugs/382842
sleep 1
mount -t aufs -o br:${localroot}=rw:${netroot}=nfsro aufsroot ${rootmnt}
This all happens within the initrd, by the way.
Perhaps this should be documented somewhere.
--
aufs fails to report free space when the readonly-branch comes via nfs and the
readwrite-branch via a local ext3
https://bugs.launchpad.net/bugs/382842
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382842] Re: aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3
There is a workaround available (sleep 1) ** Changed in: linux (Ubuntu) Status: New => In Progress -- aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3 https://bugs.launchpad.net/bugs/382842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382842] Re: aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3
** Attachment added: "lspci -vvvn" http://launchpadlibrarian.net/27418945/lspci-vnvn.log -- aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3 https://bugs.launchpad.net/bugs/382842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382842] [NEW] aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3
Public bug reported: Jaunty, kernel 2.6.28-11-generic, aufs Usecase: machines bootet via PXE with an NFS r/o Root filesystem; an aufs branch that overlays a local r/w ext3 partition. Expected results (as was before with feisty, hardy and unionfs): everything works as expected. Actual results: df reports 0 bytes free (which is false, as I can write to / until the ext3-overaly is full), so apt-get install and other applications that depend on knowing the amount of free space available beforehand fail. We tested a few different flavours: aufs r/o branch on CDROM, r/w branch on local ext3 -> works as expected aufs r/o branch on local ext3, r/w branch on local ext3 -> works as expected aufs r/o branch on CDROM, r/w branch on ramdisk -> works as expected aufs r/o branch on NFS, r/w branch on ramdisk -> works as expected For this configuration, the corresponding entries from /proc/mounts: aufsroot / aufs rw,si=e2d0eebb2bca55d4,xino=/local-root/.aufs.xino,br:/local-root=rw:/net-root=ro+wh 0 0 tmpfs /local-root tmpfs rw,size=786432k 0 0 129.70.xxx.xxx:/readonly-jaunty64 /etc/netboot/readonly nfs ro,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nointr,nolock,proto=tcp,timeo=7,retrans=10,sec=sys,addr=129.70.xxx.xxx 0 0 aufs r/o branch on NFS, r/w branch on local ext3 -> reports 0 bytes free For this configuration, the corresponding entries from /proc/mounts: rootfs / rootfs rw 0 0 129.70.xxx.xx:/readonly-jaunty64 /net-root nfs ro,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nointr,nolock,proto=tcp,timeo=7,retrans=10,sec=sys,addr=129.70.xxx.xxx 0 0 aufsroot / aufs rw,si=b196f1ef99f70379,xino=/local-root/.aufs.xino,br:/local-root=rw:/net-root=ro+wh 0 0 /dev/sda8 /local-root ext2 rw,errors=continue 0 0 129.70.xxx.xxx:/readonly-jaunty64 /etc/netboot/readonly nfs ro,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nointr,nolock,proto=tcp,timeo=7,retrans=10,sec=sys,addr=129.70.xxx.xxx 0 0 /dev/sda8 /etc/netboot/writeable ext2 rw,errors=continue 0 0 lin...@kaboom:/tmp$ lsb_release -rd Description:Ubuntu 9.04 Release:9.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3 https://bugs.launchpad.net/bugs/382842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382842] Re: aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3
** Attachment added: "dmesg" http://launchpadlibrarian.net/27418919/dmesg.log -- aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3 https://bugs.launchpad.net/bugs/382842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382842] Re: aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3
** Attachment added: "version.log" http://launchpadlibrarian.net/27418966/version.log -- aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3 https://bugs.launchpad.net/bugs/382842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382842] Re: aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3
** Attachment added: "uname -a" http://launchpadlibrarian.net/27418954/uname-a.log -- aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3 https://bugs.launchpad.net/bugs/382842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382842] Re: aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3
I forgot to mention that this unfortunatly makes jaunty unusable for us at the moment :/, and I didn't yet manage to rebuild linux- image-2.6.28-11-generic with an updated aufs - perhaps there is an easy way to do it that I didn't discover yet? -- aufs fails to report free space when the readonly-branch comes via nfs and the readwrite-branch via a local ext3 https://bugs.launchpad.net/bugs/382842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218126] Re: xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
Just a 'me too'. Trying to boot the kernel from proposed updates works for a few seconds and results in an invalid opcode (). Dom0 is Debian Etch with Xen 3.1, domU is Hardy. -- xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785' https://bugs.launchpad.net/bugs/218126 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75324] Re: Gnome file chooser/selector is way to small
The patch from above seems to fix it for me, although there's an empty window of the same small size as before, and the next blink it's gone bigger and fully loaded. This happens only when in Compiz, not metacity. -- Gnome file chooser/selector is way to small https://bugs.launchpad.net/bugs/75324 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 415824] [NEW] Can't install in chroot because /proc is not mounted
Public bug reported: Description:Ubuntu 9.04 Release:9.04 When installing this package inside our netboot tree, the following happens: (Reading database ... 367010 files and directories currently installed.) Preparing to replace libndesk-dbus-glib1.0-cil 0.4.1-1ubuntu1 (using .../libndesk-dbus-glib1.0-cil_0.4.1-1ubuntu1_all.deb) ... Removing libndesk-dbus-glib1.0-cil from Mono W: removing assembly: Mono requires /proc to be mounted. failed! Unpacking replacement libndesk-dbus-glib1.0-cil ... Preparing to replace libndesk-dbus1.0-cil 0.6.0-1ubuntu1 (using .../libndesk-dbus1.0-cil_0.6.0-1ubuntu1_all.deb) ... Removing libndesk-dbus1.0-cil from Mono W: removing assembly: Mono requires /proc to be mounted. failed! Unpacking replacement libndesk-dbus1.0-cil ... Can not write log, openpty() failed (/dev/pts not mounted?) Setting up libndesk-dbus1.0-cil (0.6.0-1ubuntu1) ... * Installing 1 assembly from libndesk-dbus1.0-cil into Mono E: installing Assembly /usr/lib/cli/ndesk-dbus-1.0/NDesk.DBus.dll failed Setting up libndesk-dbus-glib1.0-cil (0.4.1-1ubuntu1) ... * Installing 1 assembly from libndesk-dbus-glib1.0-cil into Mono E: installing Assembly /usr/lib/cli/ndesk-dbus-glib-1.0/NDesk.DBus.GLib.dll failed This in fact hinders *any* installation of mono packages inside a chroot. Mounting /proc is no option, as this might interfere with the running system (we have Debian Etch Servers providing the netboot-roots for ubuntu hardy and jaunty clients and have had some pretty bad experiences while installing packages with /proc mounted inside the chroot). Sorry for the briefness of this report but I believe you get the picture. Lukas ** Affects: mono (Ubuntu) Importance: Undecided Status: New -- Can't install in chroot because /proc is not mounted https://bugs.launchpad.net/bugs/415824 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32963] Re: Xv movies on 810/i945 gives horrible color, Gamma
Same problem here, with a i855gm: :00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) :00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Both of the different xvattr-settings from Paul Sladen above fix the bad image quality while playing. -- Xv movies on 810/i945 gives horrible color, Gamma https://launchpad.net/bugs/32963 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54189] Re: LVM support forgotten in newest kernel update?
*** This bug is a duplicate of bug 54002 *** ** This bug has been marked a duplicate of bug 54002 LVM/MD root filesystem not found by uuid -- LVM support forgotten in newest kernel update? https://launchpad.net/bugs/54189 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: LVM/MD root filesystem not found by uuid
Same problem here. root on LVM, boot hangs on "waiting for root filesystem". Also, my home is on LVM, which doesn't get mounted because the fstab was converted to UUIDs, and for my LVM Volumes, no entries in /dev/disk/by-uuid/ get created. ** Bug 54189 has been marked a duplicate of this bug -- LVM/MD root filesystem not found by uuid https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52579] Re: Rhythmbox plays only one song, then produces obscure error message
This is also happening in Totem, so I guess it's totally rhythmbox- unrelated and really gstreamer related. It happens regardless what gstreamer output device I select, so it's somehow related to the decoder I think. ** Changed in: gstreamer0.10 (Ubuntu) Sourcepackagename: rhythmbox => gstreamer0.10 -- Rhythmbox plays only one song, then produces obscure error message https://bugs.launchpad.net/bugs/52579 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52579] Re: Rhythmbox plays only one song, then produces obscure error message
Could you point me to the dup then or explain why the problem I'm having is a totally different one or tell me what more information I can give? reopening it for now. Thanks! ** Changed in: rhythmbox (Ubuntu) Status: Invalid => New -- Rhythmbox plays only one song, then produces obscure error message https://bugs.launchpad.net/bugs/52579 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness
With the latest updates in gutsy this problem seems to be gone for me. I just did a dist-upgrade and nearly didn't notice it, my laptop just worked without lagging much. I'm hooked :) -- Lukas -- Heavy Disk I/O harms desktop responsiveness https://bugs.launchpad.net/bugs/131094 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness
I can confirm this problem on latest Gutsy. It bothered me a while, but shamefully I didn't yet took the time to report it and I forgot wether this first appeared in feisty or in gutsy. My system was upgraded at least since feisty, possibly also since dapper. I actually can't remember when I last installed ubuntu from scratch. Attached are the outputs of dmesg, hdparm -tT, smartctl -a, lspci -vvn and a vmstat 2 during my latest dist-upgrade that made the system heavily unresponsive (again). Also, while tracker is indexing, or evolution is starting or any other normal disk-io is happening, the system becomes unusable. Dist-upgrades of only a few packages take ages. If there's anything I can do to help identify the root cause, please ask. ** Attachment added: "dmesg, hdparm -tT, smartctl -a, lspci -vvn and a vmstat 2" http://launchpadlibrarian.net/9523385/debug.txt -- Heavy Disk I/O harms desktop responsiveness https://bugs.launchpad.net/bugs/131094 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness
And as this was mentioned before I thought it might be important: I'm using LVM. Attached is the complete disk-layout on my system. ** Attachment added: "pvdisply; vgdisplay; lvdisplay; fdisk -l" http://launchpadlibrarian.net/9523592/lvm.txt -- Heavy Disk I/O harms desktop responsiveness https://bugs.launchpad.net/bugs/131094 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness
I run your test, the numbers seem quite equal to yours, but during the test my system became unresponsive like hell. Switching desktops (from web to evolution) took more than 20 seconds (probably due to swapping, I have 768MB RAM), subsequent switches took up to five seconds. I could see the drawing while I tried scrolling in evolutions' folder list. vim took ages to load etc. pp - all in all very sluggish. ** Attachment added: "logfile" http://launchpadlibrarian.net/9525343/logfile -- Heavy Disk I/O harms desktop responsiveness https://bugs.launchpad.net/bugs/131094 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52579] Re: Rhythmbox plays only one song, then produces obscure error message
reopened with latest comment ** Changed in: rhythmbox (Ubuntu) Status: Invalid => New -- Rhythmbox plays only one song, then produces obscure error message https://bugs.launchpad.net/bugs/52579 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52579] Re: Rhythmbox plays only one song, then produces obscure error message
I don't know if this is the same bug, but it might look so. I'm using 0.11.2-0ubuntu3 on latest gutsy, and when I try to listen to this stream: http://radio.uni-bielefeld.de/stream/hertz-q5.m3u rhythmbox stops playing after one song. It plays the first few seconds of the next and then simply stops, albeit the UI thinks it's still playing. When I click on play again, I get an error message: Couldn't start playback Internal data flow error. the output of rhythmbox -d is attached (with playlist related entries removed). ** Attachment added: "Log of rhythmbox" http://launchpadlibrarian.net/9525303/rb.log -- Rhythmbox plays only one song, then produces obscure error message https://bugs.launchpad.net/bugs/52579 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54635] Re: slow overall performance (because of highmem support and/or AGP settings?)
I have a problem that seems very related in hardy; when using 1gb of ram bootup takes anything from 5 to 20 minutes, afterwards the system is fast as normal. With only 768MB Ram, bootup takes about a minute. Just that this bug doesn't get closed. I'll report back with hopefully more information within the next few days. -- slow overall performance (because of highmem support and/or AGP settings?) https://bugs.launchpad.net/bugs/54635 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 202861] Re: gvfs-sftp hangs after network disconnect
The same here. Also, the panel hangs indefinitly or keeps crashing and restarting until I kill gvfsd, gvfsd-sftp and nautilus. -- gvfs-sftp hangs after network disconnect https://bugs.launchpad.net/bugs/202861 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 430224] Re: init: support chroots
Using a global upstart instance to manage the chroot wouldn't work - simply because you want to be able to run a Ubuntu chroot from a Debian Lenny host, or a RHEL host, or whatever. (We actually serve a Lucid netboot nfs-root from Debian Etch atm). You can't expect every linux distribution in the world to use upstart. Just a hint to keep that in mind when fixing this bug, please. -- init: support chroots https://bugs.launchpad.net/bugs/430224 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
