On Friday 18 January 2008, Chris mason wrote: > On Thursday 17 January 2008, Christian Hesse wrote: > > On Thursday 17 January 2008, Chris mason wrote: > > > So, I've put v0.11 out there. > > > > Ok, back to the suspend problem I mentioned: > > [ oopsen ] > > > I get this after a suspend/resume cycle with mounted btrfs. > > Looks like metadata corruption. How are you suspending?
No, that's not metadata corruption. After reset I can use the image without problems. After resume the first access to the fs oopses. I use kernel 2.6.24-rc8 with tuxonice 3.0-rc3 and btrfs 0.11. Back in early december I reported the problem for btrfs 0.9. Seems like the lockfs call still is not implemented. Any hints what I need when I try to code it myself? -- Regards, Chris - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
