xfs
[Top] [All Lists]

Re: XFS corruption on vanilla kernel.

To: Linux XFS List <linux-xfs@xxxxxxxxxxx>
Subject: Re: XFS corruption on vanilla kernel.
From: Johannes Brügmann <johannes@xxxxxxxxxxx>
Date: Thu, 26 Aug 2004 10:41:04 +0200
In-reply-to: <208fc95204082512352ea7b9b9@mail.gmail.com>
References: <208fc95204082512352ea7b9b9@mail.gmail.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6i
Hello XFS-list,

Wenzel Jakob wrote:
> Hello,
> I am experiencing XFS file system corruption on a vanilla kernel.org
> kernel 2.6.7 (the only additional module is the nvidia driver which
> really shouldn't be the cause of the problems).

I used the nvidia card with the Xorg driver.

> The problem is that, all of a sudden, files have the content of an
> entirely different file. For example one second I am editing a .cpp
> file, the next moment I open it up again, it is a jpeg file from a
> directory containing my digital camera pictures. The original .cpp
> file was lost, so the files were not exchanged.

I experienced exactly the same problem -- the main reason why I use
?fs now. I didn't have the heart to write this problem to this list
(though I'm reading this list for more than half a year now) because I
thought that very likely I did something wrong.

First time I encountered this problem was -- I guess -- due to broken
memory. Weeks later came the kernel freezes. So from this point on I
knew it was the memory.

I removed the broken memory -- but the problem went back. Usually
after an 'emerge sync' there were missing files in the /usr/portage
(my distribution sync tree) directory and syncing failed due to
freshly created but lost files.

This time I was experimenting with CFLAGS so I thought maybe I was too
aggressive in optimizing and probably the compiler doesn't work. The
confusing thing was, that the whole system and all applications worked
very well and were build with the same CFLAGS. *Only* syncing failed
and some files were gone. Due to the fact that syncing failed I bought
a new disk, took ?fs and builded a partially new system on the new
disk (the old one exists still with the old system).

> This has happened to me before with previous kernels from 2.6 - what I
> usually did is run knoppix and fsck the filesystem which seemed to
> stop it for a while.

Same with me: I used the gentoo livecd xfs_check, xfs_repair. Tons of
inode messages and the lost+found directory was filled with about
swap-size (with the broken memory). With a good memory it was not that
much but still some files.

I had kernel versions 2.6.1 - 2.6.7 and various rcs.

Don't know if this is useful.

Regards,
Johannes
--
      Herr,  all  mein  Verlangen liegt offen vor dir, und mein Seufzen
      ist dir nicht verborgen.

      Psalm 38,10


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