Date: Wed, 01 Dec 2021 16:28:22 -0800 From: "Ronald F. Guilmette" <rfg@tristatelogic.com> To: questions@freebsd.org Subject: Re: mount: Operation not permitted Message-ID: <62889.1638404902@segfault.tristatelogic.com> In-Reply-To: <20211130215453.64dc1b3b49a05bfa9f4b1a83@bobdbob.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20211130215453.64dc1b3b49a05bfa9f4b1a83@bobdbob.com>, Protius <protius@bobdbob.com> wrote: >I have had mount return "Operation not permitted" when the filesystem I'm >attempting to mount needs to be fscked. Was it umounted correctly? Either >way, try fscking it. I really don't think that was or is the issue. I tried adding different sleep delays into my script, which would get executed just after the umount on each partition/filesystem that was just backed up. I tried different small values for the sleep... 1, 2, 3, and finally 4. The 4 second sleep seems to be adequate so far for preventing the problem from reocurring. It's a shame that I had to solve the problem this way, of course. I would like to assert that the problem is being caused by either a bug within the mount command or else possibly in the kernel, but I've learned the hard way never to do that without absolute proof of any such claim. I don't have time to develop that just now, so I'll live with 4 second delays until those prove unworkable. Regards, rfg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?62889.1638404902>