* courier-imap/maildrop now doing proper fsync'ing
@ 2002-11-13 0:44 Dax Kelson
2002-11-13 0:55 ` Is this proper fsync'ing ? Dax Kelson
0 siblings, 1 reply; 2+ messages in thread
From: Dax Kelson @ 2002-11-13 0:44 UTC (permalink / raw)
To: linux-kernel@vger.kernel.org
The newest versions of courier-imap, a maildir POP3/POP3S/IMAP/IMAPS
server, and maildrop, a MDA, now have a compile time configure option:
--with-dirsync
Should it now be safe to run ext3 filesystems (that contain the
maildirs) with data=writeback?
BTW, procmail isn't doing proper fsyncing when writing to a maildir.
Dax
^ permalink raw reply [flat|nested] 2+ messages in thread
* Is this proper fsync'ing ?
2002-11-13 0:44 courier-imap/maildrop now doing proper fsync'ing Dax Kelson
@ 2002-11-13 0:55 ` Dax Kelson
0 siblings, 0 replies; 2+ messages in thread
From: Dax Kelson @ 2002-11-13 0:55 UTC (permalink / raw)
To: linux-kernel@vger.kernel.org
Here is some strace output from email delivery via maildrop compiled
with --with-dirsync:
open("./Maildir/tmp/1037107256.1332_0.mail,S=673", O_WRONLY|O_NONBLOCK|O_CREAT|O_EXCL, 0666) = 3
write(3, "message contents goes here"..., 673) = 673
fsync(3) = 0
close(3) = 0
link("./Maildir/tmp/1037107256.1332_0.mail,S=673", "./Maildir/new/1037107256.1332_0.mail,S=673") = 0
open("./Maildir/new", O_RDONLY) = 3
fsync(3) = 0
close(3) = 0
unlink("./Maildir/tmp/1037107256.1332_0.mail,S=673") = 0
[snip some non-relevant stuff]
exit(0)
Does this look correct/safe? Filesystem is ext3 data=writeback.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-11-13 0:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-11-13 0:44 courier-imap/maildrop now doing proper fsync'ing Dax Kelson
2002-11-13 0:55 ` Is this proper fsync'ing ? Dax Kelson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox