Re: Bug#1130266: barfs on lost+found if mail is on its own filesystem

Subject: Re: Bug#1130266: barfs on lost+found if mail is on its own filesystem

Date: Wed, 11 Mar 2026 07:39:14 +0900

To: Marc Haber, 1130266@bugs.debian.org, notmuch@notmuchmail.org

Cc:

From: David Bremner


Marc Haber <mh+debian-packages@zugschlus.de> writes:

>
> I have my mail in ~/.mail, and that's its own filesystem because my 
> Maildir is not much, eh, HUGE.
>
> Notmuch doesn't much like that:
>
> Warning: failed to open directory /home/mh/.mail/lost+found: Permission denied
> Found 3311631 total files (that's not much mail).
> Error opening directory /home/mh/.mail/lost+found: Permission denied
> No new mail.
> Note: A fatal error was encountered: Something went wrong trying to read or write a file
>
> Neither ignore=lost+found nor ignore=/home/mh/mail/lost+found seems to 
> help here.
>

I reassigned to notmuch, since the "Error" message is coming from
notmuch.

Running "notmuch new" with 

           drwx------ 2 root root 4096 Mar 11 07:22 lost+found

(but _not_ a separate file system)

I get

    Error opening directory /home/bremner/Maildir/lost+found: Permission denied
    No new mail.
    Note: A fatal error was encountered: Something went wrong trying to read
    or write a file

For me

    ignore=.git;_notmuch_metadata;.gitignore;lost+found

seems to work, but I haven't tested on a separate file system yet.

If you can duplicate the problem with the "notmuch" command, without
using notmuch-mutt, that would be helpful.


_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org

Thread: