All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Anderson <anderson@ligo.caltech.edu>
To: nfs@lists.sourceforge.net
Subject: NFSv4 uninitialized mtime
Date: Wed, 27 Jun 2007 16:31:14 -0700	[thread overview]
Message-ID: <20070627233114.GA14508@ligo.caltech.edu> (raw)

The following simple program creates files with un-initialized mtime values
on a Linux NFSv4 client mounting from a Solaris NFSv4 server--at least the
mtimes are wildly different each time the program is run. The problem is
reproducible but does not happen under any of the following circumstances:

1) Drop O_EXCL from open() call.
2) NFS mount using v3.
3) Switch NFS v4 client from Linux to Solaris.

This is on an FC4 machine with the 2.6.20.14 kernel plus Trond's recent
revalidate-the-fsid-on-the-current-dir-not-the-root-dir patch
and nfs-utils 1.0.9-16 backported from CentOS 5.

Thanks.


> cat badmtime.c 
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>


main() {
int fd;

fd = open("badtime.out", O_CREAT|O_EXCL, 0664);
close(fd);
}
> vi badmtime.c
> gcc badmtime.c -o badmtime
> ./badmtime 
> ls -l badmtime.out 
-rw-r--r--  1 anderson anderson 0 Oct  9  1979 badmtime.out
> stat badmtime.out 
  File: `badmtime.out'
  Size: 0               Blocks: 1          IO Block: 1048576 regular empty file
Device: 20h/32d Inode: 107016      Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 5026/anderson)   Gid: ( 5026/anderson)
Access: 2007-06-27 16:07:24.184162655 -0700
Modify: 1979-10-09 12:54:39.549017000 -0700
Change: 2007-06-27 16:07:24.192792428 -0700


-- 
Stuart Anderson  anderson@ligo.caltech.edu
http://www.ligo.caltech.edu/~anderson

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-06-27 23:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27 23:31 Stuart Anderson [this message]
2007-06-27 23:43 ` NFSv4 uninitialized mtime Trond Myklebust
2007-06-28  0:49   ` Stuart Anderson
2007-06-28  0:59     ` Stuart Anderson
2007-06-28  1:15       ` Jeff Layton
2007-06-28  2:53         ` Stuart Anderson
2007-06-28  3:09           ` Spencer Shepler
2007-06-28  3:23             ` Stuart Anderson
2007-06-28  3:30               ` Spencer Shepler
2007-06-28  3:44                 ` Stuart Anderson
2007-06-28  3:59                   ` Spencer Shepler
2007-06-28 13:32                     ` J. Bruce Fields
2007-06-28 10:41           ` Jeff Layton
2007-06-28 12:01             ` Jeff Layton
2007-06-28 13:19               ` Trond Myklebust
2007-06-28 13:29                 ` Jeff Layton
     [not found] <nfs-valinux.20070628064127.a769bc53.jlayton@redhat.com>
     [not found] ` <46857F06.102@ligo.caltech.edu>
     [not found]   ` <20070629181234.b70f6f7f.jlayton@redhat.com>
2007-06-29 22:31     ` Erik A. Espinoza
2007-06-30  2:35       ` Jeff Layton
2007-06-30  3:09         ` Erik A. Espinoza
2007-06-30 11:19           ` Jeff Layton

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=20070627233114.GA14508@ligo.caltech.edu \
    --to=anderson@ligo.caltech.edu \
    --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.