From: Luis Henriques <lhenriques@suse.com>
To: Marc Roos <M.Roos@f1-outsourcing.eu>, Jeff Layton <jlayton@kernel.org>
Cc: ceph-users <ceph-users@ceph.io>, ceph-devel@vger.kernel.org
Subject: Re: [ceph-users] cephfs snap mkdir strange timestamp
Date: Tue, 10 Mar 2020 13:46:13 +0000 [thread overview]
Message-ID: <20200310134613.GA74810@suse.com> (raw)
In-Reply-To: <"H000007100164304.1583836879.sx.f1-outsourcing.eu*"@MHS>
[ CC'ing Jeff and ceph-devel@ ]
On Tue, Mar 10, 2020 at 11:41:19AM +0100, Marc Roos wrote:
>
>
> If I make a directory in linux the directory has the date of now, why is
> this not with creating a snap dir? Is this not a bug? One expects this
> to be the same as in linux not????
I've noticed that long time ago, but I never checked the fuse client
behaviour, which turns out to be different. The fuse client seems to set
ctime and atime to the same value as the parent directory (see
Client::open_snapdir()).
The patch below mimics that behaviour, by simply copying those timestamps
from the parent inode.
Cheers,
--
Luis
From 2c8e06e66e5453ddf8b634cf1689a812dc05a0c6 Mon Sep 17 00:00:00 2001
From: Luis Henriques <lhenriques@suse.com>
Date: Tue, 10 Mar 2020 13:35:11 +0000
Subject: [PATCH] ceph: fix snapshot dir ctime and mtime
The .snap directory timestamps are kept at 0 (1970-01-01 00:00), which
isn't consistent with what the fuse client does. This patch makes the
behaviour consistent, by setting these timestamps to those of the parent
directory.
Signed-off-by: Luis Henriques <lhenriques@suse.com>
---
fs/ceph/inode.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/ceph/inode.c b/fs/ceph/inode.c
index d01710a16a4a..f4e78ade0871 100644
--- a/fs/ceph/inode.c
+++ b/fs/ceph/inode.c
@@ -82,6 +82,8 @@ struct inode *ceph_get_snapdir(struct inode *parent)
inode->i_mode = parent->i_mode;
inode->i_uid = parent->i_uid;
inode->i_gid = parent->i_gid;
+ inode->i_mtime = parent->i_mtime;
+ inode->i_ctime = parent->i_ctime;
inode->i_op = &ceph_snapdir_iops;
inode->i_fop = &ceph_snapdir_fops;
ci->i_snap_caps = CEPH_CAP_PIN; /* so we can open */
next parent reply other threads:[~2020-03-10 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <"H000007100163fdf.1583792359.sx.f1-outsourcing.eu*"@MHS>
[not found] ` <"H000007100164304.1583836879.sx.f1-outsourcing.eu*"@MHS>
2020-03-10 13:46 ` Luis Henriques [this message]
2020-03-10 17:39 ` [ceph-users] cephfs snap mkdir strange timestamp Jeff Layton
2020-03-11 10:31 ` Luis Henriques
2020-03-11 10:36 ` Marc Roos
[not found] ` <"H00000710016454f.1583923016.sx.f1-outsourcing.eu*"@MHS>
2020-03-11 11:04 ` Luis Henriques
2020-03-11 11:25 ` Luis Henriques
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=20200310134613.GA74810@suse.com \
--to=lhenriques@suse.com \
--cc=M.Roos@f1-outsourcing.eu \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@ceph.io \
--cc=jlayton@kernel.org \
/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.