Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Here is the situation:

We have a file server that is not saving timestamps to a small portion of its files (77 files out of several million). It instead writes a default mtime of 1969-12-31 19:00 (Unix epoch).

When this does happen, it happens irregularly with no set pattern (ie. one file here, a group of files in the same directory there. etc.) The files that are timestamped this way have been uploaded to the server through NFS.

It should be noted that we are only seeing this happen in an NFS share that is on this server and it has not happened to any of the servers system files, it seems isolated to just the NFS share.

Some additional info:

  • the server is running Ubuntu Server 9.04
  • NFSv4 for file serving. Here is the exports line:
    /home/file_storage 10.0.0.1/24(rw,sync,no_root_squash,no_subtree_check)
  • We recently migrated our files to this server using rsync from our old file server
  • This server has a hardware RAID 5 array using a 3ware 9650SE controller.
  • Filesystem is ext3 with LVM and LUKS/DMCRYPT on a single root partition
  • The server is regularly syncing its time with ntpd.

Update

Updated the filesystem and partitioning info above as requested in comments.

share|improve this question
add comment

3 Answers

Are the only mount point on the raid controller /home/file_storage? In other words, are the other file systems on that server on the same raid controller or on a different controller?

If the only thing on the raid controller is the nfs share, then I'd worry that there are blocks of 0 getting written, and you see them as the date zeroed. It might be worthwhile to run a bunch of md5sums across the different files, and then run them a week later and see which ones have changed.

If, on the other hand, you have a lot of file systems on the same raid controller, and the only one messing up is the nfs shared one, then it could be that network packets are getting corrupted. We have seen in the past places where files have random 8k blocks of 0s in them. Ie, everyone thought that nfs block was written, but, in fact, it wasn't. This probably is a network problem and you should see errors on the interface then.

I'd go for the first one though.

share|improve this answer
    
"are the other file systems on that server on the same raid controller or on a different controller?" They are on the same controller. –  faultyserver Jul 31 '09 at 23:43
add comment

Are you seeing the strange times locally or only remotely? If you are worried about the filesystem intergraty I would consider running the file system checker from CERN which I will add a link to when I can find it.. ( it continually writes a file to the system and then waits and reads it ).

The 3ware cards are generally pretty good.

share|improve this answer
    
The timestamp is the same when viewed locally or remotely, it does not change. –  faultyserver Jul 31 '09 at 23:45
add comment

My understanding of file times on NFS is that they're typically set by the client, so perhaps you have a machine that thinks it's constantly time zero?

share|improve this answer
    
thank you for your answer, but I dont believe that is the case here. If that was true, then all of the files that were saved to the NFS share by this client would have a constant time of zero, but it appears that there is only a small subset that have a zero time, not a majority of the files –  faultyserver Aug 1 '09 at 4:20
    
Well, if a particular client only modified a small subset of the files... –  womble Aug 1 '09 at 6:31
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.