[Lustre-discuss] OST went back in time to 0 (bug 9646)

[Mikhail Pershin]

On Thu, 30 Jul 2009 10:29:17 +0400, Jakob Goldbach <jakob at goldbach.dk>  
wrote:

> Hi,
>
> I have a question on bug 9646 - Server went back in time.
>
> I had an OSS crash and had to pull the power. After mounting lustre
> again I see the following on one of my clients:
>
> (import.c:909:ptlrpc_connect_interpret()) b-OST0010_UUID went back in
> time (transno 12901362807 was previously committed, server now claims
> 0)!  See https://bugzilla.lustre.org/show_bug.cgi?id=9646
>
> This bug description suggest that there are commits lost in hardware
> cache - but how can it loose all commits (transno is zero)? (btw, cache
> is battery backup up)
>
> On the client that I saw this I had previosly deactivated the import
> bacause of the crash. Is this the reason I'm seeing this transno as
> zero ? (full dmesg below)
>

Please see the bug 19579, it is not critical error and harmless but it is  
confusing to see such error message indeed. This is wrong alert and will  
be fixed

-- 
Mikhail Pershin
Staff Engineer
Lustre Group
Sun Microsystems, Inc.