From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: nfs@lists.sourceforge.net
Subject: sendmail "cannot fsync directory" after 2.4 -> 2.6
Date: Thu, 09 Sep 2004 08:15:07 +0200 [thread overview]
Message-ID: <413FF4EB.2070607@bio.ifi.lmu.de> (raw)
Hi,
we've been running SuSE 9.0 with kernel 2.4.21 for some months. Two weeks
ago we switched to 2.6.8.1 from kernel.org.
Our diskless clients get (due to lack of a local hd) everything via nfs,
including /var/spool/mqueue. The /var directories for the clients (one
seperate for each client) are exported with "sync" and mounted with
"tcp,hard,intr,lock,sync", and this has not changed when switching from
2.4 to 2.6. But after we switched to 2.6.8.1, we get messages
Sep 9 08:03:13 galois sendmail[21596]: sync_dir: cannot fsync directory .: Invalid argument
Sep 9 08:04:02 galois sendmail[21649]: i89641NZ021648: SYSERR(root): sync_dir: cannot fsync directory .: Invalid argument
every time we send a mail with "mail -s test root" or similar. Note that
sendmail is running as daemon on every client, but only listening on
localhost. The sendmail package has REQUIRES_DIR_FSYNC enabled.
I tried mounting the nfs dir with "dirsync" additionally, but it doesn't
help. Also, it doesn't make a difference if the exported fs on the server
is ext3 or reiserfs. Since it works on local disks and worked also over
NFS with kernel 2.4.21, I guess it is a bug in 2.6? Or should it not work
with nfs and 2.4 just didn't notice?
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-09-09 6:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 6:15 Frank Steiner [this message]
2004-09-09 10:39 ` sendmail "cannot fsync directory" after 2.4 -> 2.6 Frank Steiner
2004-09-09 14:58 ` Trond Myklebust
2004-09-09 17:54 ` Ara.T.Howard
2004-09-09 18:25 ` Trond Myklebust
2004-09-10 7:33 ` Frank Steiner
-- strict thread matches above, loose matches on Subject: below --
2004-09-09 18:54 Lever, Charles
2004-09-09 20:36 ` Ara.T.Howard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=413FF4EB.2070607@bio.ifi.lmu.de \
--to=fsteiner-mail@bio.ifi.lmu.de \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.