> On Fri, Jul 06, 2001 at 12:38:51PM -0500,
> Steve Lord wrote:
> > > With ext2, the fsck would attempt to fix metadata problems
> > > on bootup; on the other hand, with xfs, if write caching
> > > resulted in a corrupted log, would the simple log replay
> > > that xfs does on mount perhaps fail to catch possible
> > > metadata problems?
> > Yes, and the same will be true for all write behind journalled
> > filesystems, if the log does not make it to disk when the
> > driver says it has then in theory a subsequent metadata write
> > could make it out to the media. A crash at this point would
> > mean that part of a transaction had made it to disk, but the
> > rest which only existed in the disks internal cache would not.
> I assume that a manual xfs_repair would be needed at that
> point... (?)
Yes, a full consistency check is the only way out of this situation,
pretty much the same think fsck is doing on ext2.
> Andrew Klaassen