[Samba] Samba 4.15.3 - inotify and fget_ea_dos_attribute errors

[Paul Griffith]

> -----Original Message-----
> From: Jeremy Allison <jra at samba.org>
> Sent: Tuesday, January 18, 2022 2:57 PM
> To: Paul Griffith <paulg at yorku.ca>
> Cc: samba at lists.samba.org
> Subject: Re: [Samba] Samba 4.15.3 - inotify and fget_ea_dos_attribute errors
> 
> On Tue, Jan 18, 2022 at 04:54:59PM +0000, Paul Griffith via samba wrote:
> >Hello,
> >
> >I recently updated our AD joined file server to Samba 4.15.3, I am noticing
> some errors in the log file. They may be nothing but it could be something.
> >
> >File server:   CentOS Linux release 7.9.2009 (Core)
> >
> >#1 -   inotify_add_watch returned Permission denied
> >
> >What would cause this error? I checked the permissions on the directory in
> question, and it is 711,  and ownership is correct.  Any suggestions to further
> debug?
> >
> >[2022/01/18 11:16:09.113410,  1, pid=27967, effective(0, 0), real(0,
> >0)] ../../source3/smbd/notify_inotify.c:442(inotify_watch)
> >  inotify_add_watch returned Permission denied
> >[2022/01/18 11:16:09.113509,  1, pid=27967, effective(0, 0), real(0,
> >0)] ../../source3/smbd/notifyd/notifyd.c:437(notifyd_apply_rec_change)
> >  notifyd_apply_rec_change: sys_notify_watch for [/eecs/home/paulg]
> >returned Permission denied
> >[2022/01/18 11:16:09.159720,  1, pid=27967, effective(0, 0), real(0,
> >0)] ../../source3/smbd/notify_inotify.c:442(inotify_watch)
> >  inotify_add_watch returned Permission denied
> >[2022/01/18 11:16:09.159771,  1, pid=27967, effective(0, 0), real(0,
> >0)] ../../source3/smbd/notifyd/notifyd.c:437(notifyd_apply_rec_change)
> >  notifyd_apply_rec_change: sys_notify_watch for [/eecs/home/paulg]
> >returned Permission denied
> >
> >
> >#2 -   fget_ea_dos_attribute: Cannot get attribute from EA on file biopac:
> Error = Operation not supported
> 
> Sounds like the filesystem doesn't support EA's, or the kernel doesn't
> support getting the EA via the sys_proc_fd_path() method.
> 
> CentOS 7 has an old kernel I believe.
> 
> To track this down you'll need to add more debugs to identify exactly where
> the problem lies.

Hello Jeremy,

    My home directory is mounted from our NFS fileserver, would that be the cause of the error I am seeing? 

Thanks
Paul