Description of problem:
Few buckets were created with objects from s3 apis on rgw. Later when we instantiate ganesha and mounted using nfs mount . Now observe the timestamp for these directories (rgw buckets) it will be too old.
for ex :
[root@magna110 mnt]# ll
drwxrwxrwx. 3 root root 0 Jan 1 1970 another-missed-hellonew-another-newad-bucket-creation
drwxrwxrwx. 3 root root 0 Jan 1 1970 hellonew-another-newad-bucket-creation
drwxrwxrwx. 3 root root 0 Jan 1 1970 missed-hellonew-another-newad-bucket-creation
drwxrwxrwx. 3 4294967294 4294967294 0 Jul 23 13:11 nfsbucket
observe timestamp for first three directories its "Jan 1 1970" . but buckets created later has proper time stamp.
mount command used
mount -t nfs -o nfsvers=4.1,sync,noauto,soft,proto=tcp magna116.ceph.redhat.com:/ /mntr
Version-Release number of selected component (if applicable):
Agree, the timestamp for these buckets -should- be an RGW timestamp, not 0. Not sure if this can be changed before 2.1.
Matt, what ticket in tracker.ceph.com corresponds to this issue?
(In reply to Ken Dreyer (Red Hat) from comment #5)
> Matt, what ticket in tracker.ceph.com corresponds to this issue?
I've just created http://tracker.ceph.com/issues/17367 for it.
Proposed fix in
Resolved upstream in v10.2.5
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.