On Thu, 2002-10-10 at 09:55, Hardy I.D. wrote:
> Hi,
>
> Yesterday I rebooted a server with a recent XFS CVS (downloaded/compiled
> Tuesday of this week; the kernel reports at boot time - 'SGI XFS
> CVS-10/08/02:05 with quota, no debug enabled'. Since then the kernel has
> shut down the one XFS filesystem on this server:
>
> Oct 10 14:22:10 blue01 kernel: xfs_force_shutdown(md(9,0),0x8) called
> from line 1041 of file xfs_trans.c. Return address = 0xc01d9138
> Oct 10 14:22:10 blue01 kernel: Corruption of in-memory data detected.
> Shutting down filesystem: md(9,0)
> Oct 10 14:22:10 blue01 kernel: Please umount the filesystem, and rectify
> the problem(s)
>
> I've rebooted, ran xfs_check (and xfs_repair, which was necessary on the
> first occasion, the 2nd time - above the 'xfs_check' was clean) and
> remounted the filesystem OK.
Ian, did you run xfs_check and repair before mounting the fs or
after? You should mount again after reboot, then run check.
The in memory corruption error means it failed an internal check
on a memory buffer, not that it had found bad data on the disk.
If you have the check/repair output, please send it, but there is
no real way to tell if the issues in it were from running the
commands with a dirty log or not.
We really need to improve that particular trace message, there
are 80 some places it could have originated. Lets see if we
can do something about that.
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx
|