From: David Zafman <dzafman@redhat.com>
Date: Fri, 6 Feb 2015 02:40:25 +0000 (-0800)
Subject: osd: FileJournal::read_entry() can't use a zero seq to check for corruption
X-Git-Tag: v9.0.2~168^2~39
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=a7cda53d20eb6d35203fce6ec9f7ea1df432bf53;p=ceph.git

osd: FileJournal::read_entry() can't use a zero seq to check for corruption

Seen when using dump() on a journal which has all entries committed

Signed-off-by: David Zafman <dzafman@redhat.com>
---

diff --git a/src/os/FileJournal.cc b/src/os/FileJournal.cc
index 80fa1a9477a6..3130ac9c7c8e 100644
--- a/src/os/FileJournal.cc
+++ b/src/os/FileJournal.cc
@@ -1778,7 +1778,7 @@ bool FileJournal::read_entry(
   }
 
   stringstream errss;
-  if (seq < header.committed_up_to) {
+  if (seq && seq < header.committed_up_to) {
     derr << "Unable to read past sequence " << seq
 	 << " but header indicates the journal has committed up through "
 	 << header.committed_up_to << ", journal is corrupt" << dendl;