Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Nov 2010 11:17:43 -0600
From:      Josh Paetzel <josh@tcbug.org>
To:        stable@freebsd.org
Cc:        imp@freebsd.org, rmacklem@uoguelph.ca, re@freebsd.org
Subject:   Re: NFS regression on recent STABLE
Message-ID:  <201011231117.49879.josh@tcbug.org>
In-Reply-To: <201011230833.59085.josh@tcbug.org>
References:  <201011230833.59085.josh@tcbug.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart7464145.Ap4Gex3xgb
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Tuesday, November 23, 2010 08:33:52 am Josh Paetzel wrote:
> I've been involved with a project at work doing some fun things with NFS.
> Recently due to changes in a available hardware we did a complete refresh
> of the system.  New HBAs, new storage boxes, and due to some internal
> software confusion we updated the OS on the head from 8.1-R with zpool 15
> backported to STABLE.
>=20
> Our primary client that we were using against this setup was a ESXi 4.1
> machine.  In a nutshell, it didn't work.  Long description is, ZFS would
> deadlock and any operation on the pool would hang.  The ESXi instance wou=
ld
> mark the NFS mount as unavailable.  I initially thought this could be due
> to any number of factors, we have new HBAs in the  mix, new storage boxes,
> a new version of zpool, and one test case.
>=20
> Meanwhile, back at the ranch, I have a somewhat similar setup at home.
> FreeBSD 8.1 NFS server, ESXi 4.1 box mounting an NFS exported ZFS
> filesystem from the FreeBSD box as a datastore.
>=20
> Last night I pulled that box up to STABLE, rebooted it, and a minute after
> it rebooted the ESXi box marked the NFS datastore as unavailable.  I
> checked the FreeBSD machine and sure enough it hung doing an ls on the
> zpool.
>=20
> I ran a few tests, and as soon as the ESXi box mounts the NFS export it
> hangs the ZFS filesystem.  If I don't mount it up, the NFS server does
> fine. Thinking it might be a ZFS problem I moved the mount to a UFS
> filesystem. While this doesn't cause the box to hang on filesystem
> operations, the mount goes unavailable.
>=20
> The only other client I have on my network is a FreeBSD 8.1 box, and that
> has no issues
>=20
> All of this is with the standard NFS server, I haven't yet tested with the
> experimental server.

Thanks to kib for helping resolve this.

In a nutshell, at one point there was a problem in STABLE, it was fixed, an=
d=20
my local cvsup mirror fell out of sync and while I thought I was seeing a=20
problem from a system updated last night, I was getting an old rev.

Updating the system to a mirror that isn't broken fixed the problem.

=2D-=20
Thanks,

Josh Paetzel

--nextPart7464145.Ap4Gex3xgb
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (FreeBSD)

iQEcBAABAgAGBQJM6/c9AAoJEKFq1/n1feG2FjsIAK+ikMfUWiUkUEDKxSjprASg
UCeuLr2YEnpUwmEnV77a6BUPCH1DYcHHm3rFixyY8aZGlmXTP1BosteSY+oKHu1Q
1gVwJwb+g2LhvanZnHlpY7zhBRzZSQB2ew5gJaoilW01ulQjoTptbBfFBXCq0MPO
0Thi0bYYkODtUOOtIRun0P+s5uT3bdAlmlqHRYFvYO3y8rfoQe0QOctzP5UFiMkb
8Y8DHzc254TSf793g+R0F9I9SclCeBqCwUiLEw1c4o3leR1P5jvldh09oNkSgxuY
SBOfh9bqSTcFOn8DMtXgJwSfqV5bSVK9qBGrgy9i4/d4WBilOJnPfVqtR/WizLA=
=6VM9
-----END PGP SIGNATURE-----

--nextPart7464145.Ap4Gex3xgb--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011231117.49879.josh>