On 05/25/2011 01:41 PM, matthieu Barthélemy wrote: > Finally I successfully remounted my partition. Here is how I've done > to recover, in case it can help someone else : > I had to clone btrfs-progs-unstable tree. > Then checkout branch "tmp" (because I use compression, default > btrfs-progs are "too old" > Then I compiled btrfs-zero-log with "make btrfs-zero-log" > And finally ran "./btrfs-zero-log /dev/sda2" > > Now I'm copying everything to a new partition, because I don't know if > can safely use the damaged one. > > But wouldn't it be possible to avoid the "Null pointer" kernel crash > by checking what we do inside replay_one_buffer, and then > automatically clear log, or provide a "clear_log" mount option? > Any idea about what could have caused my problem? > Can you do a gdb btrfs.ko and then do list *(add_inode_ref+0x1e7) so I can see where it is. It doesn't seem like either of those read_extent_buffer's should screw up, either we do the proper checks or it should have gone sideways before you got there. Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
