Hide Forgot
Description of problem: We dumped metadata from a 2 TB btrfs disk using btrfs-image after running vdbench for a while. After restoring the metadata with btrfs-image -r, a mount of the disk lead to a kernel bug: kernel BUG at fs/btrfs/volumes.c:2831! Full dmesg attached. Dumps being uploaded to: http://bekstil.net/~albert/dump.btrfs.bz2 http://bekstil.net/~albert/dump2.btrfs.bz2 Version-Release number of selected component (if applicable): kernel-2.6.35.10-74.fc14.x86_64 How reproducible: Always Steps to Reproduce: 1. bunzip2 dump.btrfs.bz2 2. btrfs-image -r btrfs-image /big/disk 3. mount /big/disk Actual results: Crash. See attached. Expected results: Should work. Disk was fine before we dumped the metadata.
Created attachment 477636 [details] dmesg output
Yeah images created by btrfs-image are not meant to be mounted, it just creates something that can be looked at by btrfsck. Tho it shouldn't panic, I will fix that, but you still won't be able to mount it.
Given that f14's btrfs is *way* behind mainline, and there have been hundreds of fixes since that aren't going to get backported (f14 is only really going to get security fixes, and obviously correct fixes at this point in its lifecycle), moving this bug to f16.
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.