[Bug 443321] Re: drbd devices not automatically mounted via /etc/fstab even witn _netdev
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 mounts and mounts labeled with '_netdev' mount option. The default startup of drbd in /etc/rc2.d/S70drbd comes again much later in the sequence. I originally planned to enter this as a "Wishlist" item and not a bug (but ubuntu-bug didn't let me do that) since I fully understand the complications in setups where drbd device sync / pri/sec / mounts must be handled by a HA system like heartbeat. I was kind of wondering if there were a safe way to enable the simple functionality for the cases where /etc/fstab mounts with '_netdev' (only on one machine, the "primary one") could work "out of the box"? I would expect HA cases not to rely on /etc/fstab in any case, though there might be other '_netdev' mounts. Checking for 'drbd.*_netdev' mount lines in /etc/fstab, maybe? In any case, I'm really happy with drbd functionality and robustness in my current setup where I run a three-disk raid0 in my desktop as '/home' and have drbd mirroring that onto a single 2TB disk in a small server. It has survived r8169 driver timeouts, r8168 driver giving bad data (md5 checksums enabled!), any network problem or up/down sequence I've thrown at it and I have _never_ had to reboot either machine because of drbd, it has always "obeyed" the 'drbdadm' and not "locked up". And the performance is great! :-) I hope you can make the transition to DKMS for the kernel module (not being included in the mainline Ubuntu kernel anymore) a smooth experience! -- 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, which is subscribed to drbd8 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 443321] Re: drbd devices not automatically mounted via /etc/fstab even witn _netdev
** 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, which is subscribed to drbd8 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 443321] [NEW] 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 typical system will reach '/etc/rc2.d/S70drbd start' much before than network will be up). I'm not sure if this is really a "solid" solution but since calling '/etc/init.d/drbd start' again after it has already been called seems quite benign, I have just added the script '/etc/network/if-up.d/drbd-start' (note the naming alphabetically _before_ 'mountnfs' in that directory) with the contents: - #! /bin/sh /etc/init.d/drbd start - and I have labeled my drbd mounts in /etc/fstab with the '_netdev' option: - /dev/drbd1 /home ext3 _netdev,relatime 0 2 /dev/drbd2 /local ext3 _netdev,relatime 0 3 - This causes the "if-up" system (regardless whether it is NetworkManager-originated or due to interfaces listed in /etc/network/interfaces) to first bring up drbd devices and then mount the network-dependent drbd devices. Works beautifully for me, in the simple situation where I don't want to use an HA manager to shift the primary/secondary roles around, I just want my "main" computer to be primary and mount the devices by default and the "secondary" to skip all mounting. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: drbd8-utils 2:8.3.0-1ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: drbd8 Uname: Linux 2.6.28-15-generic x86_64 ** Affects: drbd8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- 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, which is subscribed to drbd8 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 443321] apport-collect data
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 https://bugs.launchpad.net/bugs/443321 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 269954] Re: ssh -X breaks Xauthority on NFS mounted home dir
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 https://bugs.launchpad.net/bugs/269954 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 269954] Re: ssh -X breaks Xauthority on NFS mounted home dir
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' indeed
replaces the ~/.Xauthority file in my home directory: the inode number
changes on the server but not on my Ubuntu desktop.
With the 'defaults' mount options in my /etc/fstab, my desktop continues
to show old ~/.Xauthority inode number and stat() data for 60 seconds,
then 'ls -l' starts returning 'ls: cannot access .Xauthority: Stale NFS
file handle'. A command line 'stat .Xauthority' returns the same error.
Doing any of 'ls .', 'cat .Xauthority >/dev/null', 'touch .Xauthority'
will immediately cure this, letting 'ls -l .Xauthority' show the correct
and updated info, the same as in the NFS server.
With the 'noac' mount option in my /etc/fstab the behavior is otherwise
the same as in the above, but the 60 second timeout disappears and 'stat
.Xauthority' starts to return 'Stale NFS file handle' immediately after
'ssh -X third-machine' has replaced the file at 'third-machine' and the
NFS server.
With the 'sync' mount option in /etc/fstab the behavior is just like in
the case of 'defaults' mount option.
I find it quite likely that this has actually nothing to do with the way
OpenSSH does the updating of '.Xauthority' file (i.e. many other
applications revise files by replacing them with a new version) but the
way '~/.Xauthority' is apparently often used, by just 'stat()'ting it,
leads to exposure of this problem. It looks to me more like a kernel
NFS client problem.
I'm a bit puzzled why 'lstat64(".Xauthority", ...)' would fail with
stale NFS handle whereas a 'open(".Xauthority", ...)' will work just
fine---why the former gets out-of-date directory info and the latter
gets the correct, updated one?
--
ssh -X breaks Xauthority on NFS mounted home dir
https://bugs.launchpad.net/bugs/269954
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
