On Mon, 2011-04-25 at 15:05 -0600, cwillu wrote: > On Mon, Apr 25, 2011 at 2:50 PM, Peter Stuge <pe...@stuge.se> wrote: > > Maik Zumstrull wrote: > >> >> Bug at fs/btrfs/free-space-cache.c:1246 > >> >> Bug type: invalid opcode: 0000 > >> >> Kernel not tainted, running on an ASUSTek 1005HAG > >> >> EIP is at btrfs_add_free_space+0x285/0x39a [btrfs] > >> > > >> > You will probably need to provide a more complete copy of the panic > >> > message. > >> > >> I thought as much, but other than taking a picture of the screen, I > >> don't know how. > > > > Take a picture and ideally transcribe it after reboot. > > Known issue; josef sent a patch > (http://permalink.gmane.org/gmane.comp.file-systems.btrfs/10261) that > should fix it, or you can mount with clear_cache on each boot as a > workaround.
This fix doesn't seem to be in your for-linux branch yet. Please can you ensure that this (or an alternate fix) is included in 2.6.39. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
