From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 38642] New: ext4 timestamp format unable to uniquely represent times
Date: Fri, 1 Jul 2011 15:05:38 GMT [thread overview]
Message-ID: <bug-38642-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=38642
Summary: ext4 timestamp format unable to uniquely represent
times
Product: File System
Version: 2.5
Kernel Version: all
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: ersmith.nospam@totalspectrum.ca
Regression: No
The presence of the extra bits in the ext4 timestamps implies a desire to
represent file times to sub-second accuracy. Unfortunately, standard posix
timestamps are not uniformly 1 SI second long, due to the presence of leap
seconds. For example, the Posix timestamp 1230768000 corresponds to the UTC
times "2008-12-31 23:59:60" and "2009-01-01 00:00:00".
Since there are only 30 bits in the nanosecond field, ext4 cannot accurately
keep track of file times during a leap second.
One possible solution would be to add another bit to the nanosecond field,
allowing nanoseconds to range from 0 to 1999999999 and hence allowing
sufficient range to keep accurate time even during "long" posix timestamps.
Another would be to specify that the seconds fields of ext4 time stamps should
hold actual SI seconds elapsed, rather than POSIX timestamps; this would be
considerably more complicated, though.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2011-07-01 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 15:05 bugzilla-daemon [this message]
2012-08-24 15:07 ` [Bug 38642] ext4 timestamp format unable to uniquely represent times bugzilla-daemon
2012-08-25 16:01 ` [Bug 38642] New: " Theodore Ts'o
2012-08-25 17:51 ` [Bug 38642] " bugzilla-daemon
2013-12-23 14:04 ` bugzilla-daemon
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=bug-38642-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.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 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).