Hi Corey,

thank you. I try to update the kernel to a newer one if i get a downtime. 
Maybe on Sunday. :-)

Is that an official bug? I don't find something on the relase notes.

regards Jens



From:
Corey Kovacs <[email protected]>
To:
"Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list" 
<[email protected]>
Date:
04.03.2010 09:51
Subject:
Re: [rhelv5-list] NFS Client Timestamp problem
Sent by:
[email protected]



The files I had problems with , then "dot" file had the wrong timestamps 
and were of size 0.

Obviously you'll need to check your files. The underlying filesystem was 
fine mind you. It was just some files that were destroyed.

Good luck

Corey

On Thu, Mar 4, 2010 at 8:28 AM, Jens Voigt <[email protected]> 
wrote:
Hi Corey, 

thanks for your quick response. Is it only a display issue or may i assume 
that my data can be corrupt? 

Jens 


From: 
Corey Kovacs <[email protected]> 
To: 
"Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list" <
[email protected]> 
Date: 
04.03.2010 08:45 
Subject: 
Re: [rhelv5-list] NFS Client Timestamp problem 
Sent by: 
[email protected]





Also, the kernel only need be upgraded on the server, not the client.

-C

On Thu, Mar 4, 2010 at 7:34 AM, Corey Kovacs <[email protected]> 
wrote: 
Jens,

That looks like a problem we had as well. You might also see that "dot" 
files are really messed up. The problem exists in that particular kernel 
release I believe (I don't have it in front of me atm) and an upgrade is 
necessary. It's a problem specific to NFS I believe.

-Corey

On Thu, Mar 4, 2010 at 7:02 AM, Jens Voigt <[email protected]> 
wrote: 
Hi Folks, 

we are running RHEL5.4 2.6.18-164.el5PAE on 2 Servers. One is mounting an 
FC-Storage(MPIO) and export this via NFS to the Network(NIS, automounter) 
also via Samba. 

I created a new file on the samba share on server1 and do a 'ls -altr' on 
the server1. So the new file is on the bottom. Everythings fine. 
#ls -altr 
Aug  8  2008 oldfile 
Mar  3 11:01 newfile 

Now my Problem one user reported and also happens on my workstation 2 
times: 
Server2 mounts the same folder via nfsv3 
The same 'ls -altr' on server2 shows me also the same file at the bottom 
and a second old file in this folder with the same new timestamp. 
At the same time on server1 'ls -altr' shows me the correct timestamps. 
The second old file dated in year 2008. 
A second 'ls -altr' on server2 shows me also the correct timestamps now. 

Server1 
#ls -altr 
Aug  8  2008 oldfile 
Mar  3 11:01 newfile 
at the same time on Server2 
#ls -altr 
Mar  3 11:01 oldfile 
Mar  3 11:01 newfile 

one second later on Server2 
#ls -altr 
Aug  8  2008 oldfile 
Mar  3 11:01 newfile 

I don't know which component is causing this problem. For my understanding 
it must be nfs. 

regards Jens 

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list


_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list



_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list


_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to