On Wed, Mar 13, 2013 at 08:03:53AM -0600, Russell Coker wrote: > On Thu, 14 Mar 2013, Eric Sandeen <sand...@redhat.com> wrote: > > > It seems the SSD has bad blocks now, BTRFS seems to abuse SSD disks, I > > > burnt 1 SSD disk and 2 USB flash drive since I'm using BTRFS, in about > > > 2 months for each. ddrescue'ing the SSD would probably give better > > > chances of recovery and give BTRFS/btrfsck a chance to write correctly > > > to the newly copied image. > > > > On what do you base that theory? I suppose it could be, but nothing > > in the logs necessarily suggests that. The "IO failure" is because > > the fs shut down, went readonly, and subsequent IOs got -EIO, > > I think. > > I've just used nc to transfer the filesystem to another system, there were no > read errors so I don't think that a SSD hardware failure is the problem here. > > I'm now getting similar problems running a 3.8 kernel with the filesystem on > a > loopback device. I'll provide more information soon.
Bad key ordering is pretty rare, and it usually means memory corruptions. Are you reproducing this on the same machine or a different one? -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
