On Mon, 16 Oct 2006, Jason White wrote:
> This is my desktop system, running kernel 220.127.116.11. Kernel 2.6.17 was
> previously installed, but I upgraded several weeks ago after I found out about
> the corruption bug in 2.6.17, which may or may not be related to the
> The file system was shut down during a Debian package upgrade while trying to
> access apt-related files. I booted into an old 2.4 kernel on a separate
> partition and ran an old version of xfs_repair. The output is attached.
> Xfs_repair terminated abnormally (see the end of the output).
> I can copy a newer version of xfs_repair to the backup partition if that would
> help, though I'm not sure which libraries to copy along with it.
> Also, if there is any indication of what might have caused this I would be
> interested, as this hasn't happened before and I'de especially like to find
> out whether it is a hardware problem, or related to the current kernel, or
> indeed a manifestation of the 2.6.17 bug. I've successfully mounted the
> corrupted file system and a lot of it is still relatively intact - plenty of
> files in lost+found, especially from the /usr/share/man3 directory for obvious
> It's a straightforward desktop machine with an IDE drive. I haven't updated
> Debian packages on here for a while, so it isn't clear when the corruption
Most likely if you booted and mounted the partition r/w with 2.6.17(.1-.6)
then it is most likely a result of that.
Either follow the instructions on the XFS FAQ on how to fix the problem or
re-install and bypass 2.6.17-18.104.22.168.
Backup your data first if possible before you do anything!