David Brown wrote:
On Sun, Dec 04, 2005 at 11:41:42PM +0000, Peter Grandi wrote:
jijo> First, that I had to mount the filesystem (the root
jijo> partition) from a rescue CD for the log replay to "fix"
jijo> things properly.
IIRC Debian Sarge mounts the root filesystem in a way that for
example does not necessarily trigger the mount count/time based
check. At least it did not happen on my mostly-Sarge PC.
The distributions mount count/time checks would only invoke fsck.xfs, which
never does anything. It shouldn't be possible to mount the root filesystem
without replaying logs, so this is likely to be a real bug.
Dave
XFS always does a scan of the log on mount, it always replays the log if it
is not terminated with an unmount record. The fact that the filesystem is
mounted readonly during startup should have no affect on this. XFS will run
recovery on a read only mount.
On inode unlink, XFS adds inodes to an unlinked inode list until the space in
the inode is freed when the last reference count is released. Removing these
inodes is part of the recovery process. It sounds like there may be an issue
with this part of recovery.
Steve
|