On Thu, Feb 25, 2010 at 09:04:20AM -0500, Bill Pemberton wrote: > > > > I don't suppose you have the dmesg errors from the crash? This error > > shows the header in the block is incorrect, so either something was > > written to the wrong place or not written at all. > > > > Have you memtest86 on this system? > > > > How did it crash...was a power off used to reset the machine? > > > > No dmesg. This has happened on two different machines that both have > other active btrfs filesystems, so I suspect it's not a memory issue. > In both cases it was the same data that was being copied when the > crash occurred.
Ok, is there anything special about this data? > > I didn't deal with the reboot in the first case, so I don't have much > in the way of details. In the second case the kernel seemed convinced > the array was having problems (and the load went way up), but the > array was convinced it was fine. A normal reboot hung and the server > had to be powered off. > > Since it appears that the same operation caused the problem in both > cases, I'm going to try to reproduce it. I'll let you know if I can > reproduce it. What kind of array is this? It really sounds like the IO isn't happening properly. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
