From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] curious mtime of cwfs
Date: Mon, 25 Feb 2013 10:04:01 +0900 [thread overview]
Message-ID: <69702CC5-3D26-4B77-B098-6C2F81EBEF76@ar.aichi-u.ac.jp> (raw)
Hello,
cwfs64x shows curious mtime in dump.
my experiment is only on cwfs64x. I don't know other cwfs.
fossil is OK.
standing on general rule of unix and plan9,
mtime of directory should be the time that the contents are modified.
#
# fossil
#
ar% ls -ld /n/dump
d-r-xr-xr-x M 538590 adm adm 0 Dec 31 2003 /n/dump/2003
d-r-xr-xr-x M 538590 adm adm 0 Dec 31 2004 /n/dump/2004
d-r-xr-xr-x M 538590 adm adm 0 Dec 31 2005 /n/dump/2005
d-r-xr-xr-x M 538590 adm adm 0 Dec 31 2006 /n/dump/2006
d-r-xr-xr-x M 538590 adm adm 0 Dec 31 2007 /n/dump/2007
d-r-xr-xr-x M 538590 adm adm 0 Dec 31 2008 /n/dump/2008
d-r-xr-xr-x M 538590 adm adm 0 Dec 31 2009 /n/dump/2009
d-r-xr-xr-x M 538590 adm adm 0 Dec 30 2010 /n/dump/2010
d-r-xr-xr-x M 538590 adm adm 0 Dec 31 2011 /n/dump/2011
d-r-xr-xr-x M 538590 adm adm 0 Dec 31 13:00 /n/dump/2012
d-r-xr-xr-x M 538590 adm adm 0 Feb 24 13:00 /n/dump/2013
ar% ls -ld /n/dump
d-r-xr-xr-x M 538590 adm adm 0 Jan 1 13:00 /n/dump
ar% ls -l /n/dump/2013
...
d-r-xr-xr-x M 538590 adm adm 0 Feb 20 13:00 /n/dump/2013/0220
d-r-xr-xr-x M 538590 adm adm 0 Feb 21 13:00 /n/dump/2013/0221
d-r-xr-xr-x M 538590 adm adm 0 Feb 22 13:00 /n/dump/2013/0222
d-r-xr-xr-x M 538590 adm adm 0 Feb 23 13:00 /n/dump/2013/0223
d-r-xr-xr-x M 538590 adm adm 0 Feb 24 13:00 /n/dump/2013/0224
ar% ls -ld /n/dump/2013
d-r-xr-xr-x M 538590 adm adm 0 Feb 24 13:00 /n/dump/2013
# this is OK because the last change is at the time 0224 is added.
ar%
#
# cwfs64x
#
maia# ls -l /n/dump
d-r-xr-xr-x M 160 adm adm 0 Aug 1 2012 /n/dump/2012
d-r-xr-xr-x M 160 adm adm 0 Jan 21 05:07 /n/dump/2013
maia# ls -ld /n/dump
d-r-xr-xr-x M 160 adm adm 0 Jul 31 2012 /n/dump
maia# ls -l /n/dump/2013
....
d-r-xr-xr-x M 160 adm adm 0 Feb 21 05:00 /n/dump/2013/0221
d-r-xr-xr-x M 160 adm adm 0 Feb 22 05:00 /n/dump/2013/0222
d-r-xr-xr-x M 160 adm adm 0 Feb 23 00:23 /n/dump/2013/0223
d-r-xr-xr-x M 160 adm adm 0 Feb 24 05:00 /n/dump/2013/0224
d-r-xr-xr-x M 160 adm adm 0 Feb 24 17:09 /n/dump/2013/02241
d-r-xr-xr-x M 160 adm adm 0 Feb 25 05:00 /n/dump/2013/0225
maia# ls -ld /n/dump/2013
d-r-xr-xr-x M 160 adm adm 0 Jan 21 05:07 /n/dump/2013
# this is NG because the last change is at the time 0225 is added.
maia#
Kenji Arisawa
next reply other threads:[~2013-02-25 1:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 1:04 arisawa [this message]
2013-02-25 1:17 ` arisawa
2013-02-25 5:55 ` cinap_lenrek
2013-02-25 7:24 ` arisawa
2013-02-25 8:23 ` cinap_lenrek
2013-02-25 10:17 ` arisawa
2013-02-25 10:34 ` Anthony Martin
2013-02-25 11:27 ` cinap_lenrek
2013-02-25 11:39 ` arisawa
2013-03-02 21:08 ` erik quanstrom
2013-03-03 3:30 ` arisawa
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=69702CC5-3D26-4B77-B098-6C2F81EBEF76@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@9fans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).