https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235047
Bug ID: 235047
Summary: Samba, FreeBSD 12 and ZFS
Product: Base System
Version: 12.0-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: misc
Assignee: b...@freebsd.org
Reporter: gerard_seib...@outlook.com
Created attachment 201235
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201235&action=edit
Error messages emited by Samba
freebsd-version 12.0-RELEASE-p2
FreeBSD scorpio.seibercom.net 12.0-RELEASE-p2 FreeBSD 12.0-RELEASE-p2 GENERIC
amd64
samba48-4.8.7
Ever since updating from FreeBSD 11 to FreeBSD 12, I have experienced a
problem with samba. While still on FreeBSD 11, I configured a Windows
10 machine to write backups of selected directories to my FreeBSD
machine. That worked perfectly. No problems were detected and
everything was backed up correctly. However, after updating to FreeBSD
12 a problem has arisen. While the backups do apparently succeed
successfully, the screen on my FreeBSD machine fills up with error
messages while the backup is happening. I have attached a copy of the latest
error messages.
I posted on the Samba mail forum and received this reply:
You're getting this due to the error code being returned in errno
not being one that Samba expects. Here's the underlying code:
ret = quotactl(path, cmd, id, qblk);
if (ret == -1) {
/* ENOTSUP means quota support is not compiled in. EINVAL
* means that quotas are not configured (commonly).
*/
if (errno != ENOTSUP && errno != EINVAL) {
DEBUG(0, ("failed to %s quota for %s ID %u on %s:
%s\n",
(cmd & QCMD(Q_GETQUOTA, 0)) ? "get" :
"set",
(cmd & QCMD(0, GRPQUOTA)) ? "group" :
"user",
(unsigned)id, path, strerror(errno)));
}
Looks like your system is returning ENOENT here in errno, not ENOTSUP or
EINVAL.
Since this worked correctly on FreeBSD 11, I believe that I can safely assume
that something changed drastically between FreeBSD 11 & FreeBSD 12. I did
notice that ZFS was updated. Perhaps that is the cause of this.
In any case, I don't know exactly where to report this, so I thought I would
start here.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
