Date: Sat, 1 May 2004 17:27:22 -0600 From: Tillman Hodgson <tillman@seekingfire.com> To: FreeBSD-Questions <freebsd-questions@freebsd.org> Subject: Re: NFS occassionally gives "permission" denied in the middle of a large transfer Message-ID: <20040501232722.GC9547@seekingfire.com> In-Reply-To: <20040427021650.GQ92049@seekingfire.com> References: <20040426182547.GF92049@seekingfire.com> <20040426183717.GF2771@dan.emsphone.com> <20040426184324.GH92049@seekingfire.com> <20040426184710.GA22344@dan.emsphone.com> <20040426224633.GN92049@seekingfire.com> <20040426230855.GB22344@dan.emsphone.com> <20040427021650.GQ92049@seekingfire.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 26, 2004 at 08:16:50PM -0600, Tillman Hodgson wrote:
> On Mon, Apr 26, 2004 at 06:08:56PM -0500, Dan Nelson wrote:
> > That's probably it, then. /sbin/mount has code that sends SIGHUP to
> > mountd on any mount operation. Which implies that any manual mount
> > request, including NFS mounts would, cause the problem. Amd calls the
> > mount syscall directly, bypassing /sbin/mount.
> >
> > Ideally, mountd would be able to compare the current and new export
> > settings and only update the ones that changed, or have a way to create
> > a new mountlist and ask the kernel to replace the old one in a single
> > atomic operation.
>
> I'll disable the umount/mount stuff from my dump script for /home and
> run periodic/weekly by hand to test this.
After a fair amount of testing, I can now report that all servers all
backing up via dump to an NFS export without problems. Thanks!
-T
--
I've found that nurturing one's Zen nature is vital to dealing with
technology. Violence is pretty damn useful too.
- A.S.R. quote (Lionel Lauer)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040501232722.GC9547>