xfs
[Top] [All Lists]

[Bug 355] unreplayable log after crash

To: xfs-master@xxxxxxxxxxx
Subject: [Bug 355] unreplayable log after crash
From: bugzilla-daemon@xxxxxxxxxxx
Date: Sun, 15 Aug 2004 17:59:08 -0700
Sender: linux-xfs-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=355





------- Additional Comments From nathans@xxxxxxx  2004-15-08 17:59 PDT -------
hi Peter,

> but the subsequent mount fails when the log would be replayed.  xfs_check 
> tells
> me that the filesystem is funky:

Most likely because the log not replayed, so this isn't useful information
unless it persists after a mount/umount (more recent xfsprogs will warn),
or repair in this case.

> Kernel is 2.4.20-31.7.2.cernsmp which is basically RedHat plus some local
> patches to the SCSI tape layer.

Where did the XFS code come from (which version?  cvs?)

> sure to gather as much information about the fs as possible:

Thanks!  (fyi - one other useful piece - the -C option to xfs_logprint
can capture the log off to a file for later post-processing).

> Could we at least theorize what causes this, because the probability of
> hardware error is diminishing rather fast as more cases are developed?

Lots of variables here - if we can eliminate some, we could come up
with a theory.  Things to exclude if possible - software RAID, large
inodes vs default, v2 log vs defaults, stripe alignment vs none, etc.
Any additional info will help.  Any mount options in use?

thanks.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


<Prev in Thread] Current Thread [Next in Thread>