From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: sendmail "cannot fsync directory" after 2.4 -> 2.6
Date: Thu, 09 Sep 2004 12:39:05 +0200 [thread overview]
Message-ID: <414032C9.7090105@bio.ifi.lmu.de> (raw)
In-Reply-To: <413FF4EB.2070607@bio.ifi.lmu.de>
I wrote a little c program to test fsync on nfs directories (must be
called in the directory you want to check):
#include <fcntl.h>
int main() {
int dirfd;
dirfd = open(".",O_RDONLY, 0700);
if (fsync(dirfd) < 0)
printf("failed\n");
else
printf("succeeded\n");
}
Indeed it fails for all nfs-mounted directories when the client is running
kernel 2.6 (tried 2.6.6 and 2.6.8.1), and succeeds for clients running
kernel 2.4, with the same nfs server (regardless if the server is running
2.6 or 2.4).
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
-------------------------------------------------------
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 prev parent reply other threads:[~2004-09-09 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 6:15 sendmail "cannot fsync directory" after 2.4 -> 2.6 Frank Steiner
2004-09-09 10:39 ` Frank Steiner [this message]
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=414032C9.7090105@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.