![]() | ||||||||||
Messages in this thread |
On Fri, 3 November 2006 02:19:05 +0100, Mikulas Patocka wrote: > >On Thu, 2 November 2006 22:52:47 +0100, Mikulas Patocka wrote: > >> > >>new method to keep data consistent in case of crashes (instead of > >>journaling), > > > >Your 32-bit transaction counter will overflow in the real world. It > >will take a setup with millions of transactions per second and even > >then not trigger for a few years, but when it hits your filesystem, > >the administrator of such a beast won't be happy at all. :) > > If it overflows, it increases crash count instead. So really you have 2^47 > transactions or 65536 crashes and 2^31 transactions between each crash. I am fully aware the counters are effectively 48-bit. If they were just 32-bit, you would likely have hit the problem yourself already. Jörn -- Data expands to fill the space available for storage. -- Parkinson's Law - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2006-11-03 09:21 [W:0.764 / U:0.030 seconds] ©2003-2008 Jasper Spaans | ||||||||||