| To: | "Avuton Olrich" <avuton@xxxxxxxxx> |
|---|---|
| Subject: | Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable |
| From: | Duncan Sands <duncan.sands@xxxxxxxxxxxxxx> |
| Date: | Sun, 25 Jun 2006 12:09:23 +0200 |
| Cc: | "Nathan Scott" <nathans@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <3aa654a40606200120v5baf0304ka205f1ad8f136ad9@mail.gmail.com> |
| References: | <3aa654a40606190044q43dca571qdc06ee13d82d979@mail.gmail.com> <20060620165209.C1080488@wobbly.melbourne.sgi.com> <3aa654a40606200120v5baf0304ka205f1ad8f136ad9@mail.gmail.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | KMail/1.9.1 |
I just got a new XFS crash running 2.6.17, again with problems at block 16777216 - I'll try to make a copy of the corrupted filesystem available. Interestingly enough, I'm also seeing ext3 corruption. The usual manifestation is that a program fails to run, with a message about it not being in executable format (if it happens again I will take a note of the exact message). I've had no problems at all with 2.6.17. It seems to be happening randomly, which makes me suspect a race condition (uniprocessor machine, but preemptable kernel), or memory corruption. I will rebuild the kernel with all kernel debugging options turned on, once I recover the filesystem. Ciao, D. |
| Previous by Date: | Re: xfs crash with linux 2.6.15.7 and disabled write caches (long), Martin Steigerwald |
|---|---|
| Next by Date: | Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable, Duncan Sands |
| Previous by Thread: | Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable, Nathan Scott |
| Next by Thread: | Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable, Duncan Sands |
| Indexes: | [Date] [Thread] [Top] [All Lists] |