On Mar 3, 2014, at 11:42 PM, Hendrik Friedel <hend...@friedels.name> wrote:
> Hi Chris, > > >> It might be worth finding large files to defragment. See the ENOSPC errors >> during raid1 rebalance thread. It sounds like it might be possible for some >> fragmented files to be stuck across multiple chunks, preventing conversion. > > I moved 400Gb from my other (but full) disc to the btrfs disc. This freed up > 400Gb on the full disc, so that I could move the other 400Gb to the non-btrfs > disc. Essentially, I think this also defragmented all files, as they were > freshly written (and as "single", so that in fact a balance probably was not > neccessarry anymore). > > After this balance and device-delete worked, also the device-delete! > > Nevertheless: I find it concerning, that this problem occured (remember, it > was a raid with no SMART errors) and could not be fixed. My understanding > was, that this should not happen to btrfs even in its current state. I think that's the goal, but I don't think we're there yet. The are going to be unexpected bugs. I think it would be useful if you can recreate the problem with a discrete set of steps. If it's reproducible then hopefully it's a preventable situation, not just a matter for the fsck to fix. Chris Murphy-- 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
