Re: [Jfs-discussion] Recover+Notify

[<DKL...@au...>]

I'm having to send this through my webmail since spamcop has blacklisted
our IBM mail gateway. :-(

On Mon, 2005-12-05 at 16:18 +0100, Nico Schottelius wrote:
> Hello!
> 
> Dave Kleikamp [Mon, Sep 19, 2005 at 08:34:08AM -0500]:
> > On Sun, 2005-09-18 at 12:48 +0200, Nico Schottelius wrote:
> > [...]
> > > [mutt]
> > > 2. When using mutt with reiser or xfs, it reacts differently when
I have
> > >    a mailbox opened: With jfs new messages are _not_ automatically
shown.
> > >    With reiser or xfs, mutt seems to get notified, when the current
> > >    directory (Maildir/new) gets a new mail.
> > > 
> > >    Is that a problem of
> > >       a) dnotify
> > >       b) inotify
> > >       c) mutt?
> > 
> > I don't know about this.  jfs doesn't do anything special to support
> > dnotify or inodify.  They are implemented in the vfs.  There may be
> > something that jfs is failing to do that I'm not aware of.  This is
> > going to take some investigation.  I will put it on my todo list, but
> > would appreciate it if anyone out there wants to look into this.
> 
> Are there any news?

Originally, I thought the problem may have been explained by this post
by Peter Grandi:
http://sourceforge.net/mailarchive/message.php?msg_id=13136173

But looking at this post again reminds me of a recent fix that I hadn't
connected to the mutt problem.

On Thu, 2005-09-29 at 19:48 +0100, Peter Grandi wrote:
> Perhaps the timeout value was different in the two cases.
> 
> More improbably it may be instead that in some circumstances JFS
> does not update the modified time of a directory when a new file
> is added to it, but I haven't noticed.

A bug was recently reported that the mtime (& ctime) of a directory is
not being updated when a file is linked into the directory:
http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=988a6490a793b73ff23aa3baf87b337152178e4d

I'm not sure if mutt adds files to a directory with a link, but this may
possibly explain the problem.  This bug is fixed in 2.6.15-rc1.

> I am now using 2.6.14, it's the same behaviour.
> 
> Nico
> 
-- 
David Kleikamp
IBM Linux Technology Center