* One second timestamp resolution?
@ 2019-09-11 5:50 Paul D. DeRocco
2019-09-12 9:05 ` Jussi Kukkonen
0 siblings, 1 reply; 3+ messages in thread
From: Paul D. DeRocco @ 2019-09-11 5:50 UTC (permalink / raw)
To: yocto
I just noticed that I'm getting one-second resolution on all my
timestamps. This is for both ext4 and vfat partitions, and shows up in ls
--full-time and the stat command. What could account for this? My uname -a
output is "Linux CHROMA1 4.10.17-yocto-preempt-rt #1 SMP PREEMPT Wed Oct
11 12:33:54 PDT 2017 i686 i686 i386 GNU/Linux" if that's any help. Also,
my ext4 mount options are "rw,noatime,nodiratime,data=ordered".
--
Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: One second timestamp resolution?
2019-09-11 5:50 One second timestamp resolution? Paul D. DeRocco
@ 2019-09-12 9:05 ` Jussi Kukkonen
2019-09-12 16:58 ` Paul D. DeRocco
0 siblings, 1 reply; 3+ messages in thread
From: Jussi Kukkonen @ 2019-09-12 9:05 UTC (permalink / raw)
To: Paul D. DeRocco; +Cc: Yocto discussion list
On Wed, 11 Sep 2019 at 08:53, Paul D. DeRocco <pderocco@ix.netcom.com> wrote:
>
> I just noticed that I'm getting one-second resolution on all my
> timestamps. This is for both ext4 and vfat partitions, and shows up in ls
> --full-time and the stat command. What could account for this? My uname -a
> output is "Linux CHROMA1 4.10.17-yocto-preempt-rt #1 SMP PREEMPT Wed Oct
> 11 12:33:54 PDT 2017 i686 i686 i386 GNU/Linux" if that's any help. Also,
> my ext4 mount options are "rw,noatime,nodiratime,data=ordered".
I think file timestamp resolution on ext4 is one of the things that
depend on inode size (ext4 does not enforce reasonable values because
of compatibility with earlier versions I guess). So maybe check inode
size (should be 256 bytes I think?).
Jussi
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: One second timestamp resolution?
2019-09-12 9:05 ` Jussi Kukkonen
@ 2019-09-12 16:58 ` Paul D. DeRocco
0 siblings, 0 replies; 3+ messages in thread
From: Paul D. DeRocco @ 2019-09-12 16:58 UTC (permalink / raw)
To: 'Jussi Kukkonen'; +Cc: 'Yocto discussion list'
> From: Jussi Kukkonen [mailto:jku@goto.fi]
>
> I think file timestamp resolution on ext4 is one of the things that
> depend on inode size (ext4 does not enforce reasonable values because
> of compatibility with earlier versions I guess). So maybe check inode
> size (should be 256 bytes I think?).
I don't have tune2fs on my embedded system, so I can't check, but that sounds like the probable reason. The nanoseconds that ext4 added are in the upper 128 bytes of a 256 byte inode, for compatibility reasons, so somehow I must have ext4 configured to use 128 byte inodes. Where would this be configured in a Yocto build? I'm still on Pyro.
--
Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-09-12 16:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-11 5:50 One second timestamp resolution? Paul D. DeRocco
2019-09-12 9:05 ` Jussi Kukkonen
2019-09-12 16:58 ` Paul D. DeRocco
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.