Hi, > I don't think the signboards are big enough.
Sure; that's why I tried to make one of them larger. > Most people assume that there is some way of fixing a broken file > system, and finding out the btrfs does not have one usually is > quite surprising and just a little too late. Agreed, that's my experience from the IRC channel. > I was under the impression that with atomic writes it's > impossible to mess up a file system? Yes, we're not seeing data corruption, we're correctly reporting that the transid of the data block doesn't match the transid in the parent node's pointer, which means that some writes went missing. Then we're hitting a BUG() as a result, which hangs. I don't know what the right way of dealing with this is going to be, but answers like "pretend the lost writes never happened and sync the transids", or "do something other than BUG() on verify_parent_transid() failure" sound plausible. - Chris. -- Chris Ball <c...@laptop.org> One Laptop Per Child -- 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
