I mentioned that this affects jaunty-server, too, but I forgot to
describe how. By default the server edition doesn't rely on if-up.d
mechanism but relies on /etc/rcS.d/S40networking to bring up what is
defined in /etc/network/interfaces and then gives
/etc/rcS.d/S45mountnfs.sh a chance to do NFS
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: drbd8
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
Uname: Linux 2.6.28-15-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
--
drbd devices not automatically mounted via /etc/fstab even witn _netdev
Public bug reported:
Both in jaunty-desktop(i386/amd64) and jaunty-server the drbd subsystem
is started by '/etc/rc2.d/S70drbd' script which does not interact well
with the network-device-based filesystems being mounted by '/etc/network
/if-up.d/mountnfs' after network devices have all come up (a
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33044209/Dependencies.txt
--
drbd devices not automatically mounted via /etc/fstab even witn _netdev
https://bugs.launchpad.net/bugs/443321
You received this bug notification because you are a member of Ubuntu
Server Team,
I'm also running 8.04.1 with linux-image-2.6.24-19-generic
(2.6.24-19.41) and I can confirm this problem.
By running 'while true; do date; ls -il .Xauthority ; sleep 1; done' on
both my Ubuntu client and Debian etch NFS server (running
2.6.18-6-amd64) I can see that doing a 'ssh -X third-machine'
Further testing with various kernel versions seem to confirm this bug to
be specific to NFS clients running a 2.6.24 kernel.
** Changed in: linux (Ubuntu)
Sourcepackagename: openssh = linux
Status: New = Confirmed
--
ssh -X breaks Xauthority on NFS mounted home dir
