On Oct 25, 2012, at 2:12 PM, Marc MERLIN <m...@merlins.org> wrote: > I also have hourly, daily, weekly > btrfs subvolume snapshots, but I can't use those currently since I can't > mount the base filesystem.
It might be worth unmounting it. Then only remounting a snapshot well before the problem started, yet still current enough to be useful: use '-o subvol=' instead of trying to mount from the top. Each subvolume is a root directory, so it might be possible to find one that will mount directly. > I'm a bit surprised that no one seems to be replying on btrfs crashes, > that's a bit worrisome. I'm willing to risk my data somewhat, but if finding > a problem doesn't help fixing the code, I'm not sure if I'm helping anymore > :-/ Lurking, I've learned this means you either didn't provide enough information for anyone to go on, or the problem is known. I suspect the former. Kernel 3.5.0 or 3.6.2 doesn't say where it came from, what distribution, or what version of btrfs is included in that distros kernel. And I'm not seeing that you're using a debug kernel, which will actually produce useful error messages. And it's over a weekend for another thing. 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
