On Fri, Feb 26, 2010 at 04:57:27PM -0300, Gustavo Alves wrote: > In my case, kernel 2.6.32-0.51.rc7.git2.fc13.i686.PAE and BTRFS under LVM2. >
Did you also have power-off based reboots? Depending on the configuration LVM (anything other than a single drive) won't send barriers to the device. -chris > ---- > Gustavo Junior Alves > Specchio Soluções em TI > > > On Fri, Feb 26, 2010 at 1:15 PM, Chris Mason <chris.ma...@oracle.com> wrote: > > On Fri, Feb 26, 2010 at 11:13:32AM -0500, Chris Mason wrote: > >> On Thu, Feb 25, 2010 at 03:28:19PM -0300, Gustavo Alves wrote: > >> > I've got the same error before in a similar situation (24 partitions, > >> > only two with problems). Unfortunally I erased all data after this > >> > error. Strange that all I've done was shutdown and poweron the > >> > machine. > >> > >> Basically it looks like the tree of data checksums isn't right. Which > >> kernels were you running when you had these problems? > > > > Sorry, I mixed up this corruption with one farther down. The same > > question stands though, this error generally means that IO either didn't > > happen or happened in the wrong place. > > > > So, the more details you can give about your config the easier it will > > be to nail it down. > > > > -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 -- 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
