Nicholas Lee posted on Thu, 22 Aug 2013 02:47:38 -0400 as excerpted: > Problem: My filesystem is screwed up, and I can't mount it at all right > now. In the logs, the problem begins around 45s.
> Adding insult to injury, this occurred right as I began the initial > backup to another system with rsync. :( > I would be seriously grateful to anyone that can figure out a way to > mount/fix this partition, and I'd be willing to send some bitcoin Not to add insult to injury, but for future reference anyway, you /are/ aware that btrfs is still marked experimental both in the kernel btrfs option description and on the btrfs wiki[1], and that as such, anything you put on it should be considered subject to loss, basically throw-away data that you don't care about losing either because you have multiple backups (on rather less developmental-stage stable filesystems), or because it really is throw-away data, and backups would be overkill. I know you were just starting that backup, but the fact that you're willing to throw some bitcoin at recovery indicates that you /already/ had valuable data on the filesystem, that should have already been restoreable from (tested) backup. Alternatively, perhaps btrfs simply isn't an appropriate choice of filesystem for you at this point, because it /is/ still considered experimental. Maybe in a year or two, sometime after that experimental label comes off, depending on how conservative you actually need to be with your data. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
