Date: Sun, 17 Jan 2010 16:36:08 -0600 From: "Zane C.B." <v.velox@vvelox.net> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-fs@FreeBSD.org Subject: Re: odd NFS issues Message-ID: <20100117163608.4867dacf@vixen42.vulpes> In-Reply-To: <Pine.GSO.4.63.1001171336230.4831@muncher.cs.uoguelph.ca> References: <20100116235857.6f126ad0@vixen42.vulpes> <Pine.GSO.4.63.1001171336230.4831@muncher.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/Sd2bElY/0DdfZhKeUWGsQU2 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 17 Jan 2010 13:39:28 -0500 (EST) Rick Macklem <rmacklem@uoguelph.ca> wrote: >=20 >=20 > On Sat, 16 Jan 2010, Zane C.B. wrote: >=20 > > Regardless of if I am mounting a NFS export remotely or locally, I > > get the error below if I do a ls or any thing. > > > > Any suggestions? > > > 1 - Did anything get logged in /var/log/messages? > 2 - What kind of file system is /arc? > (Most tested is done with ufs/ffs and some use zfs. Some file > system types don't know how to do an NFS export and some > probably haven't been tested...) >=20 > Beyond that, doing a packet capture and looking at it in Wireshark > might tell you what's going on. In regards to question one, I am not seeing an thing in there. In regards to question two, it is UFS2. Hmm... I am seeing odd issues with on a tcpdump as below. Rebooting does not help nor does doing a umount -f on the location I am mounting it to. 16:33:58.397823 IP (tos 0x0, ttl 64, id 53470, offset 0, flags [none], prot= o UDP (17), length 68) 127.0.0.1.1263873696 > 127.0.0.1.2049: 40 null 16:33:58.397857 IP (tos 0x0, ttl 64, id 53471, offset 0, flags [none], prot= o UDP (17), length 52) 127.0.0.1.2049 > 127.0.0.1.1263873696: reply ok 24 n= ull 16:33:58.398364 IP (tos 0x0, ttl 64, id 53476, offset 0, flags [none], prot= o UDP (17), length 128) 127.0.0.1.1447583170 > 127.0.0.1.2049: 100 fsinfo [= |nfs] 16:33:58.398392 IP (tos 0x0, ttl 64, id 53477, offset 0, flags [none], prot= o UDP (17), length 60) 127.0.0.1.2049 > 127.0.0.1.1447583170: reply ok 32 f= sinfo ERROR: Stale NFS file handle POST: 16:33:58.398422 IP (tos 0x0, ttl 64, id 53478, offset 0, flags [none], prot= o UDP (17), length 128) 127.0.0.1.1447583171 > 127.0.0.1.2049: 100 fsinfo [= |nfs] 16:33:58.398444 IP (tos 0x0, ttl 64, id 53479, offset 0, flags [none], prot= o UDP (17), length 60) 127.0.0.1.2049 > 127.0.0.1.1447583171: reply ok 32 f= sinfo ERROR: Stale NFS file handle POST: 16:33:58.398463 IP (tos 0x0, ttl 64, id 53480, offset 0, flags [none], prot= o UDP (17), length 128) 127.0.0.1.1447583172 > 127.0.0.1.2049: 100 fsstat [= |nfs] 16:33:58.398484 IP (tos 0x0, ttl 64, id 53481, offset 0, flags [none], prot= o UDP (17), length 60) 127.0.0.1.2049 > 127.0.0.1.1447583172: reply ok 32 f= sstat ERROR: Input/output error POST: 16:33:58.398507 IP (tos 0x0, ttl 64, id 53482, offset 0, flags [none], prot= o UDP (17), length 128) 127.0.0.1.1447583173 > 127.0.0.1.2049: 100 fsinfo [= |nfs] 16:33:58.398527 IP (tos 0x0, ttl 64, id 53483, offset 0, flags [none], prot= o UDP (17), length 60) 127.0.0.1.2049 > 127.0.0.1.1447583173: reply ok 32 f= sinfo ERROR: Stale NFS file handle POST: --Sig_/Sd2bElY/0DdfZhKeUWGsQU2 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAktTkOAACgkQqrJJy0yxYQALZgCfaWIyWVJfUvMKqRjhpFmXfaI9 nR8An3X2XPOUgFMON4GORlYQv5Gk7Q9b =9uhS -----END PGP SIGNATURE----- --Sig_/Sd2bElY/0DdfZhKeUWGsQU2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100117163608.4867dacf>