From: "Jörgen Karlsson" <jorgen.karlsson@chello.se>
To: nfs@lists.sourceforge.net
Subject: knsfd - files don't sync to disk
Date: Thu, 16 May 2002 21:43:51 +0200 [thread overview]
Message-ID: <3CE40BF7.1090605@chello.se> (raw)
Hi,
We have a serious problem with knfsd and kernel 2.4.17.
When doing a database backup in our linux cluster we have noticed that
a few files are not written to disk properly. The files have zero
file size when checked with the 'ls' command
Several thousands of files are written to the nfs server during a
short period of time. Average file size is 300-400 bytes.
We have noticed that usually 1-2 out of 3000 files will have their sizes
truncated to 0.
File system is exported with (rw,sync)
The disk filesystem is ext2.
E.g. this is what is happening:
- client writes 272 bytes to the server
- mm/file.c:generic_file_write() returns 272 bytes written
- fs/nfsd/vfs.c:nfs_write() increments nfsdstats.io_write +=272
and returns that the write was sucessful.
- knfsd returns to client that 272 bytes was written.
- when checking with 'ls' command on server the file size is zero.
Apparently the nfs server lies to the client and the files are not
properly synced/written to disk.
Setting no_wdelay makes no difference.
When running with async set (or sync removed) the problem
disappears (no files have their sizes truncated to zero).
The nfs server is a PIII-700/ 1GB RAM
Any ideas what is going on ?
/Jörgen Karlsson
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-05-16 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 19:43 Jörgen Karlsson [this message]
2002-05-17 11:58 ` knsfd - files don't sync to disk Neil Brown
2002-05-17 17:18 ` Jörgen Karlsson
2002-05-17 20:56 ` Neil Brown
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=3CE40BF7.1090605@chello.se \
--to=jorgen.karlsson@chello.se \
--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.