diff -Naur postgresql-7.1.3.orig/src/backend/access/transam/xlog.c postgresql-7.1.3/src/backend/access/transam/xlog.c
--- postgresql-7.1.3.orig/src/backend/access/transam/xlog.c	2001-08-16 14:36:37.000000000 -0400
+++ postgresql-7.1.3/src/backend/access/transam/xlog.c	2005-02-23 12:23:30.963333861 -0500
@@ -1242,14 +1242,42 @@
 			WriteRqst.Flush = record;
 			XLogWrite(WriteRqst);
 			S_UNLOCK(&(XLogCtl->logwrt_lck));
-			if (XLByteLT(LogwrtResult.Flush, record))
-				elog(STOP, "XLogFlush: request is not satisfied");
 			break;
 		}
 		S_LOCK_SLEEP(&(XLogCtl->logwrt_lck), spins++, XLOG_LOCK_TIMEOUT);
 	}
 
 	END_CRIT_SECTION();
+
+	/*
+	 * If we still haven't flushed to the request point then we have a
+	 * problem; most likely, the requested flush point is past end of
+	 * XLOG. This has been seen to occur when a disk page has a corrupted
+	 * LSN.
+	 *
+	 * Formerly we treated this as a PANIC condition, but that hurts the
+	 * system's robustness rather than helping it: we do not want to take
+	 * down the whole system due to corruption on one data page.  In
+	 * particular, if the bad page is encountered again during recovery
+	 * then we would be unable to restart the database at all!	(This
+	 * scenario has actually happened in the field several times with 7.1
+	 * releases. Note that we cannot get here while InRedo is true, but if
+	 * the bad page is brought in and marked dirty during recovery then
+	 * CreateCheckPoint will try to flush it at the end of recovery.)
+	 *
+	 * The current approach is to ERROR under normal conditions, but only
+	 * NOTICE during recovery, so that the system can be brought up even
+	 * if there's a corrupt LSN.  Note that for calls from xact.c, the
+	 * ERROR will be promoted to PANIC since xact.c calls this routine
+	 * inside a critical section.  However, calls from bufmgr.c are not
+	 * within critical sections and so we will not force a restart for a
+	 * bad LSN on a data page.
+	 */
+	if (XLByteLT(LogwrtResult.Flush, record))
+		elog(InRecovery ? NOTICE : ERROR,
+			 "xlog flush request %X/%X is not satisfied --- flushed only to %X/%X",
+			 record.xlogid, record.xrecoff,
+			 LogwrtResult.Flush.xlogid, LogwrtResult.Flush.xrecoff);
 }
 
 /*
