From 58edc686a47033349c061a55b780a14c4303b92b Mon Sep 17 00:00:00 2001 From: Mikhail Pershin Date: Thu, 4 Oct 2012 09:17:53 +0400 Subject: [PATCH] LU-1943 ofd: save server last transaction number After reading server data from the last_rcvd file we must store the last transaction number in lu_target. Otherwise we write a zero last transaction number back to last_rcvd, causing transaction numbers to roll back to 2^32 every time the server is restarted. This can lead to 'server went back in time' client console errors. Whamcloud-bug-id: ORI-670 Signed-off-by: Ned Bass Signed-off-by: Mikhail Pershin Change-Id: Iaff4af3e4bd6fce0da1d1b0886147538c3300c1e Reviewed-on: http://review.whamcloud.com/4190 Tested-by: Hudson Tested-by: Maloo Reviewed-by: Ian Colle Reviewed-by: Oleg Drokin --- lustre/ofd/ofd_fs.c | 1 + 1 file changed, 1 insertion(+) diff --git a/lustre/ofd/ofd_fs.c b/lustre/ofd/ofd_fs.c index a21586d..ee01de2 100644 --- a/lustre/ofd/ofd_fs.c +++ b/lustre/ofd/ofd_fs.c @@ -453,6 +453,7 @@ int ofd_server_data_init(const struct lu_env *env, struct ofd_device *ofd) cfs_spin_lock(&ofd->ofd_lut.lut_translock); obd->obd_last_committed = lsd->lsd_last_transno; + ofd->ofd_lut.lut_last_transno = lsd->lsd_last_transno; cfs_spin_unlock(&ofd->ofd_lut.lut_translock); /* save it, so mount count and last_transno is current */ -- 1.8.3.1