On Tue, Jul 31, 2012 at 11:04:12AM -0700, Marc MERLIN wrote:

My kernel crashed for some other reason, and now I can't mount my btrfs
filesystem.
I don't care about the data, it's backed up.

I'll compile a 3.5 kernel, but is there any info you'd like off that
filesystem to see why btrfs is crashing on mount?

On the plus side, 3.5 mounted the filesystem:
[  183.069179] device label btrfs_pool1 devid 1 transid 20769 /dev/mapper/test
[  183.087805] btrfs: disk space caching is enabled
[  183.224784] btrfs: no dev_stats entry found for device /dev/mapper/test (devid 1) (OK on first mount after mkfs)
[  186.277795] Btrfs detected SSD devices, enabling SSD mode
[  188.477443] btrfs: unlinked 6 orphans
[  188.477451] btrfs: truncated 1 orphans
[  411.837015] btrfs: unlinked 13 orphans
[  414.373500] btrfs: unlinked 35 orphans

This seems to hint that I lost random files and that I don't know what they are.

I suppose I can go back to my latest hourly snapshot which is more likely to not have
truncated or missing files.

Is there anything else someone would want off that filesystem that will help 
the developers?

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/