nfs-common 1:1.2.2-4
nfs-kernel-server 1:1.2.2-4
portmap 6.0.0-2
I'm seeing this issue -- or what appears to be the same issue -- on a
machine that was upgraded from lenny to squeeze. Specifically, the
export list is empty immediately after booting:
img2:/# shutdown -r now
...
imadev:~$ ssh ro
We have a heterogeneous network of systems here, including many
HP-UX 10.20 workstations, with a lot of NFS cross-mounting. After
upgrading a machine from lenny to squeeze, one of the very first
problems I encountered was that it failed to automount my home directory.
Eventually (with some sugges
Package: nfs-kernel-server
Version: 1:1.2.2-4
Severity: normal
The export list (from rpc.mountd) shows only one host, even when a file
system has been exported to many hosts.
img2:~# showmount -e
Export list for img2:
/data2 jabba.eeg.ccf.org
/data1 jabba.eeg.ccf.org
img2:~# grep /data1 /etc/exp
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u3
Severity: normal
After upgrading this machine to Debian 8.3 (from Debian 8.2), the kernel
would not boot. I wrote these messages down:
[time stamp] Unpacking initramfs ...
(bunch of stuff that scrolls by too quickly, followed by a stack trace)
Changing "allow-hotplug eth0" to "auto eth0" in /etc/network/interfaces
appears to work around the problem in squeeze. I do not quite understand
why that works, though.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas.
Package: linux-image-2.6.32-5-686
Version: 2.6.32-31
I upgraded a machine from Lenny to Squeeze, and it failed to mount one
of the disks. Here is a large swath of dmesg from the failing kernel:
[0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-31)
(b...@decadent.org.uk) (gcc version 4.3.
Package: nfs-kernel-server
Version: 1:1.3.4-2.1
Severity: normal
The NFS server starts before DNS is working, causing exportfs to fail:
wooledg:~$ sudo systemctl status nfs-kernel-server
[sudo] password for wooledg:
* nfs-server.service - NFS server and services
Loaded: loaded (/lib/systemd/sy
I believe I was able to get this working by making a change to the
/etc/network/interfaces file:
# allow-hotplug eth0
auto eth0
iface eth0 inet dhcp
I replaced the allow-hotplug with auto. Now, after booting, it appears
to be working:
wooledg:~$ sudo systemctl status nfs-server
* nfs-server.ser
Package: nfs-kernel-server
Version: 1:1.2.8-9
Severity: normal
The no_root_squash option appears to work on i386, but not on amd64.
wooledg@wooledg:~$ grep '^[^#]' /etc/exports
/home -no_subtree_check arc1(ro,no_root_squash,sync)
arc1:~# ls /net/hosts/wooledg/home/wooledg/.bash*
/net/h
ent, and a huge step backwards. Having to
add ",sync" to every field of every line was already bad enough and
that's just 5 characters. My /etc/exports is incredibly ugly now.
Thank god for vim's search-and-replace.
--
Greg Wooledge | "T
Package: linux-image-2.6.26-1-686
Version: 2.6.26-13lenny2
Neither mii-tool nor ethtool can set my network interface to full
duplex. This is a huge problem here.
img2:/usr/bin# mii-tool eth0
eth0: no autonegotiation, 100baseTx-HD, link ok
img2:/usr/bin# mii-tool -F 100baseTx-FD eth0
img2:/usr/bi
First, I updated to 2.6.26-2-686 (from Lenny), but this has the same
problem for me. No command I know will set that NIC to full duplex
under that kernel.
I tried building a custom 2.6.29.1 kernel next, but it panics when
it can't mount /dev/md0 as the root file system. I'm not in the mood
to tr
On Fri, Apr 24, 2009 at 12:29:23AM +0100, Ben Hutchings wrote:
> Do you also expect to get a gigabit link or only 100 megabit?
The other end is set to 100/full. That is what I want to set the NIC to.
> Please run "mii-tool -v eth0".
img2:~# uptime
08:37:59 up 1 min, 1 user, load average: 0.2
On Sun, May 30, 2010 at 02:41:49PM +0200, Moritz Muehlenhoff wrote:
> Hi,
> The next release of Debian (6.0, code name Squeeze) will be based
> on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
> us whether the problem persists. If so, we should report it upstream
> to the ke
14 matches
Mail list logo
