On Fri, Jan 25, 2013 at 03:37:17PM -0500, Josef Bacik wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=903794 > > This one is just a allocator warning because the relocator doesn't do the > right > accounting for relocation. It's just complainig, we need to fix it but it > won't > keep it from working.
I won't worry about this one, then. > > https://bugzilla.redhat.com/show_bug.cgi?id=904143 > > This I'm almost certain (I have to check) was just a result of me making fsync > faster and forgetting to remove this warn on. It's fixed upstream. Again, > nothing to worry about, but annoying. Sounds good. > > This one was triggered when I tried to remove a possibly faulty disk: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=904197 > > > > Ok this is a bug, I can fix this. Basically we tried to read from the faulty > disk, it failed, we read from the other copy, and then tried to write the good > copy back to the failed disk and when we saw that the IO wasn't actually going > to go to the bad disk we panic'ed. Silly but easy enough to understand/fix. I was a little surprised that this happened after I had already done a "btrfs dev delete"--is there a way to tell btrfs that a disk really is gone? > > With a freshly created filesystem, I got a kernel bug, associated with a > > hang in most filesystem operations. This occurred in the middle of > > ordinary operation and without any sort of hardware-related errors in > > the kernel logs. > > > > https://bugzilla.redhat.com/show_bug.cgi?id=904223 > > > > So this is from the fsync stuff, and I'm sure I fixed this somewhere but I > can't > account for where I did it. Would this also be the cause of the hangs that I'm seeing? In the end, a hang with the load rising to 260.10 is the most serious problem. It's happened a few times, and it gets temporarily fixed by a reboot, but then tends to recur fairly soon. > Can you give btrfs-next a try and see if you can > still reproduce. Thanks, Is there a pre-built RPM for btrfs-next, or what's the best way to try it out in Fedora without breaking other things? Thanks for your quick response, and sorry for not responding sooner (I've been interrupted by a few phone calls). -- Andrew McNabb http://www.mcnabbs.org/andrew/ PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868 -- 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
