[Bug 89984] Re: NFS broken, "cant read superblock"
Im' closing this report regarding this being by an upgrade. If this is still an issue feel free to reopen. Thanks again for your time. ** Changed in: portmap (Ubuntu) Status: New => Fix Released -- NFS broken, "cant read superblock" https://bugs.launchpad.net/bugs/89984 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 89984] Re: NFS broken, "cant read superblock"
Reinstalling fixes the problem, however the problem returns if you reboot. -- NFS broken, "cant read superblock" https://bugs.launchpad.net/bugs/89984 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 89984] Re: NFS broken, "cant read superblock"
A dist-upgrade (which included a new kernel) fixed the problem for me. -- NFS broken, "cant read superblock" https://launchpad.net/bugs/89984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89984] Re: NFS broken, "cant read superblock"
A clean install of 7.04 64bit on an AMD64 machine sees this problem as well. -- NFS broken, "cant read superblock" https://launchpad.net/bugs/89984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89984] Re: NFS broken, "cant read superblock"
After reinstalling portmap it works for me as well in my VMWare test server. I'll have to install feisty on my desktop again once the jmicron bug is fixed to verify the pormap issue is completely gone for me. -- NFS broken, "cant read superblock" https://launchpad.net/bugs/89984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89984] Re: NFS broken, "cant read superblock"
Ok, it looks like i have NFS back working. What have i done: Removed --purge everything that comes with NFS-Kernel-Server (included the libs). Restart the Computer. Go online with Wlan. Installing all packages new. Last a "sudo mount -a" which was faster then ever. At the moment it works like a charm. I try later to reboot and hopefully it will work then also. -- NFS broken, "cant read superblock" https://launchpad.net/bugs/89984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89984] Re: NFS broken, "cant read superblock"
Me again The best thing of all is: I already have remove --purge portmap nfs-common nfs-kernel-server But i still get: tail -f /var/log/messages Mar 22 11:56:47 amilo kernel: [ 931.008000] RPC: failed to contact portmap (errno -5). Mar 22 11:57:22 amilo kernel: [ 966.008000] portmap: server localhost not responding, timed out [EMAIL PROTECTED]:~$ sudo netstat -npl Password: Aktive Internetverbindungen (Nur Server) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 127.0.0.1:2208 0.0.0.0:* LISTEN 4902/hpiod tcp0 0 0.0.0.0:139 0.0.0.0:* LISTEN 5019/smbd tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN 4876/cupsd tcp0 0 0.0.0.0:445 0.0.0.0:* LISTEN 5019/smbd tcp0 0 127.0.0.1:2207 0.0.0.0:* LISTEN 4905/python udp0 0 0.0.0.0:32768 0.0.0.0:* 4786/avahi-daemon: udp0 0 0.0.0.0:773 0.0.0.0:* - udp0 0 192.168.1.4:137 0.0.0.0:* 5017/nmbd udp0 0 0.0.0.0:137 0.0.0.0:* 5017/nmbd udp0 0 192.168.1.4:138 0.0.0.0:* 5017/nmbd udp0 0 0.0.0.0:138 0.0.0.0:* 5017/nmbd udp0 0 0.0.0.0:68 0.0.0.0:* 5846/dhclient udp0 0 0.0.0.0:53530.0.0.0:* 4786/avahi-daemon: -- NFS broken, "cant read superblock" https://launchpad.net/bugs/89984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89984] Re: NFS broken, "cant read superblock"
Sorry, me again, last time tonight :) After starting portmap demon and nfs-common-utilities i got this [EMAIL PROTECTED]:~$ sudo netstat -npl Aktive Internetverbindungen (Nur Server) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 127.0.0.1:2208 0.0.0.0:* LISTEN 4889/hpiod tcp0 0 0.0.0.0:20490.0.0.0:* LISTEN 23774/rpc.nfsd tcp0 0 0.0.0.0:111 0.0.0.0:* LISTEN 23261/portmap tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN 4863/cupsd tcp0 0 127.0.0.1:2207 0.0.0.0:* LISTEN 4892/python udp0 0 0.0.0.0:32768 0.0.0.0:* 4774/avahi-daemon: udp0 0 0.0.0.0:20490.0.0.0:* 23774/rpc.nfsd udp0 0 0.0.0.0:822 0.0.0.0:* 23542/rpc.statd udp0 0 0.0.0.0:824 0.0.0.0:* 23542/rpc.statd udp0 0 0.0.0.0:68 0.0.0.0:* 17980/dhclient udp0 0 0.0.0.0:53530.0.0.0:* 4774/avahi-daemon: udp0 0 0.0.0.0:111 0.0.0.0:* 23261/portmap udp0432 0.0.0.0:894 0.0.0.0:* - After the start of nfs kernel demon i got this [EMAIL PROTECTED]:~$ sudo netstat -npl Aktive Internetverbindungen (Nur Server) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 127.0.0.1:2208 0.0.0.0:* LISTEN 4889/hpiod tcp0 0 0.0.0.0:111 0.0.0.0:* LISTEN 23261/portmap tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN 4863/cupsd tcp0 0 127.0.0.1:2207 0.0.0.0:* LISTEN 4892/python udp0 0 0.0.0.0:32768 0.0.0.0:* 4774/avahi-daemon: udp0 0 0.0.0.0:68 0.0.0.0:* 17980/dhclient udp0 0 0.0.0.0:53530.0.0.0:* 4774/avahi-daemon: udp0 0 0.0.0.0:111 0.0.0.0:* 23261/portmap For me it is confusing. Where are all the rpc.nfsd and rpc.statd gone? Or is this normal? -- NFS broken, "cant read superblock" https://launchpad.net/bugs/89984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89984] Re: NFS broken, "cant read superblock"
Sorry, its me again. netstat -npl#on client feisty tcp0 0 0.0.0.0:111 0.0.0.0:* LISTEN 18840/portmap -- NFS broken, "cant read superblock" https://launchpad.net/bugs/89984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89984] Re: NFS broken, "cant read superblock"
I installed for testing purposes the debian portmap package 5.26. The portmap demon starts within seconds, but the problem persist. mount: 192.168.1.2:/home/thomas: can't read superblock While starting nfs trough installation (on client) it comes to an rpc time out. I think thats why the can`t read superblock error message comes up. Maybe this helps more. If there is something more that i can help with, tell me. -- NFS broken, "cant read superblock" https://launchpad.net/bugs/89984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89984] Re: NFS broken, "cant read superblock"
Good to see that finally someone else has reproduced this bug, but sad to see that there seems to be no action so far to fix the bug. I've just updated my feisty64 install in VMware and see that the problem persists. -- NFS broken, "cant read superblock" https://launchpad.net/bugs/89984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89984] Re: NFS broken, "cant read superblock"
I can confirm this Bug also. Upgrade from Edgy (March 20, 2007). The Upgrade-process broke down during upgrade when it comes to Portmap 5.24. I had to finish trough Console. Portmap takes a very long time to start or stop. I can see a line "/var/lib/nfs/rpc_pipefs used 0%" in Superkaramba Systemmonitor, if it help. My NFS-Server is Ubuntu Edgy. My old NFS-Client on Edgy worked perfect. Sorry if something is missing, this is my first comment here at launchpad. -- NFS broken, "cant read superblock" https://launchpad.net/bugs/89984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89984] Re: NFS broken, "cant read superblock"
I've reproduced the problem by reinstalling feisty Herd3 and dist- upgrades on my desktop (I cant install herd4 or 5 on my PC due to a different bug). I also installed the x86_64 version of herd5 in VMWare and was able to reproduce the bug. I also installed Debian etch in VMware and did not have the issue. Ubuntu Feisty is the only distro that I've seen this error. My NFS server is running openSUSE 10.2. -- NFS broken, "cant read superblock" https://launchpad.net/bugs/89984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
