<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">Hello, finally got a chance to reinstall the whole server, I have no done it twice, last thing was to use ext3 instead of ext4 (just a wild guess). But I still the same error. I guess I need to change the whole server. But this has worked, I just can't understand what the problem is. Kenneth </div> <blockquote cite="mid:CAEo=5Pz07LnQ+2SteyFjZYn4Y+a7PhLYkeW7h0Rw-6h_vaZcPA@mail.gmail.com" type="cite"> That date error is very suspicious. Yeah, windowsish solution indeed :-( Run memtest before the install as a flaky dimm can cause these errors as well. <div class="gmail_quote">On May 2, 2013 1:40 AM, "Kenneth Lundström" <<a moz-do-not-send="true" href="mailto:kenneth.lundstrom@nudata.fi">kenneth.lundstrom@nudata.fi</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi, sounds like an Windows fix, please reinstall :=) But that is just what I decided needs to be done, I emailed the client and will head out to client tomorrow morning. One strange thing I noticed by mistake is the dates on folders. [root@ltsp tmp]# ll /opt/ total 4 drwxr-xr-x. 5 root root 4096 Mar 17 1913 ltsp LTSP was hardly thought of 1913. I tried to look in different logs but can't see any file errors. But I see some folders being dated to 1913. Should matter for NFS, but if filesystem is that messed up no wonder NFS doesn't work. Kenneth <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Totally strange. I saw a blurb on a Ubuntu page where there was a kernel bug related to ext4 filesystem shared out by NFS. However, even though it showed the same error, it was still mountable from a remote machine. I have a vanilla CentOS 6.4 with kernel 2.6.32-358 I tested the NFS server on with no issues. /etc/exports: /home *(rw,no_root_squash,async) disables NFSv4 in /etc/sysconfig/nfs turned off iptables for the test actually have selinux in enforcing mode mounted remotely with no issues or errors on starting nfs service. At this point, I think there's a problem with the hard drive. The top level inode collections are screwed up and NFS can't "do it's thing" because it can't read the filesystem metadata. I would run 'badblocks' on the drive and reinstall (lousy answer and bad sysadmin solution but short of running strace on everything it may be the fastest way to working) with a fresh drive format. </blockquote> _______________________________________________ K12OSN mailing list <a moz-do-not-send="true" href="mailto:K12OSN@redhat.com" target="_blank">K12OSN@redhat.com</a> <a moz-do-not-send="true" href="https://www.redhat.com/mailman/listinfo/k12osn" target="_blank">https://www.redhat.com/mailman/listinfo/k12osn</a> For more info see <<a moz-do-not-send="true" href="http://www.k12os.org" target="_blank">http://www.k12os.org</a>> </blockquote> </div> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ K12OSN mailing list <a class="moz-txt-link-abbreviated" href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a> For more info see <a class="moz-txt-link-rfc2396E" href="http://www.k12os.org"><http://www.k12os.org></a></pre> </blockquote> </body> </html>