Date: Mon, 17 Sep 2012 15:23:25 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: FS List <freebsd-fs@freebsd.org> Subject: Re: testing/review of atomic export update patch Message-ID: <20120917122325.GR37286@deviant.kiev.zoral.com.ua> In-Reply-To: <1531430179.669311.1347831685957.JavaMail.root@erie.cs.uoguelph.ca> References: <1531430179.669311.1347831685957.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--vk2EvGhio7iZz8DU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 16, 2012 at 05:41:25PM -0400, Rick Macklem wrote: > Hi, >=20 > There is a simple patch at: > http://people.freebsd.org/~rmacklem/atomic-export.patch > that can be applied to a kernel + mountd, so that the new > nfsd can be suspended by mountd while the exports are being > reloaded. It adds a new "-S" flag to mountd to enable this. > (This avoids the long standing bug where clients receive ESTALE > replies to RPCs while mountd is reloading exports.) This looks simple, but also somewhat worrisome. What would happen if the mountd crashes after nfsd suspension is requested, but before resume was performed ? Might be, mountd should check for suspended nfsd on start and unsuspend it, if some flag is specified ? --vk2EvGhio7iZz8DU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlBXFjwACgkQC3+MBN1Mb4h/OACeIEjMZo6AWDlO0dSHDCrkncG6 oZYAnjVapZW44ulwTmWudOhlwpCCFUEF =U8MR -----END PGP SIGNATURE----- --vk2EvGhio7iZz8DU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120917122325.GR37286>