[HN Gopher] XFS File-System with Linux 5.10 Punts Year 2038 Prob...
       ___________________________________________________________________
        
       XFS File-System with Linux 5.10 Punts Year 2038 Problem to the Year
       2486
        
       Author : programd
       Score  : 53 points
       Date   : 2020-10-17 20:37 UTC (2 hours ago)
        
 (HTM) web link (www.phoronix.com)
 (TXT) w3m dump (www.phoronix.com)
        
       | trhway wrote:
       | one way for a generational ship to fail.
        
         | Red_Leaves_Flyy wrote:
         | While the failure mode is different. The Orville did a great
         | episode(if the stars should appear s01e04) on what could happen
         | in such an event.
         | 
         | https://m.imdb.com/title/tt6483046/
        
       | bloak wrote:
       | There's a better explanation here, though I still don't
       | understand "34-bit unsigned second counter right shifted two
       | bits" and "(((2^34-1) + (2^31-1)) & ~3)":
       | 
       | https://lwn.net/Articles/829314/
        
         | StringyBob wrote:
         | A bit mysterious, but seems as files will now have nanosecond
         | accuracy since 1901 (in the 64bit unsigned int), the quota
         | timers are still 32bit and have been downgraded from 1 second
         | to 4 second accuracy to cover the full bigtime forward time
         | range required (for 1970 unix epoch).
         | 
         | Seems to be described in this patch comment:
         | https://patchwork.kernel.org/project/xfs/patch/157784114490....
        
         | [deleted]
        
         | dschuler wrote:
         | It's not totally clear to me either, but maybe it's a 32-bit
         | value treated as a 34-bit value with a precision of 4 seconds
         | (so left-shifted two bits elsewhere), since the whole term has
         | the least significant two bits cleared with '& ~3'. No idea
         | what the (2^31-1) term is doing though.
        
       | n00ri wrote:
       | interresting
        
       | freedomben wrote:
       | It's tempting to think that 2038 is a long way off, so who cares,
       | but I still regularly encounter systems that have been in prod
       | for 20+ years. 2038 is only 18 years away! If you're building
       | systems today, it's worth thinking about how these kinds of
       | issues may affect things. You may still be around then anyhow, so
       | your future self may thank you.
        
         | chrisseaton wrote:
         | > It's tempting to think that 2038 is a long way off, so who
         | cares
         | 
         | It's not - it'll be here before you know it.
        
         | sedatk wrote:
         | It's closer than 2000.
        
         | lowbloodsugar wrote:
         | Its tempting to think 2486 is a long way off. You may still be
         | around then anyhow, so your future self may thank you.
        
         | onion2k wrote:
         | It's important to remember that 2038 problems won't start
         | happening in 2038. Any system where users can perform actions
         | to generate arbitrary dates in the future that get converted to
         | epoch timestamps in code needs to work with 2038 _now_.
        
       ___________________________________________________________________
       (page generated 2020-10-17 23:00 UTC)