I ran a few tests that Jim suggested and found that btrfs works fine on 2.6.26 as long as there are only 23 or less files on the file system. Anymore and I experience the lockup. Jim and I will be working to find a solution but if anyone else has any clues that would be greatly appreciated.
Lee On Tue, Feb 24, 2009 at 11:24:06AM -0500, jim owens wrote: > Lee Trager wrote: >> The more and more I look at this problem the more I tend to think that >> the issue is because of some change in the way the VFS or something >> interacts with the file system. Does anyone know of any big changes? Why >> is the inode being marked dirty? Is there some kind of read error. I'm >> completly lost in solving this problem. > > Being a filesystem guy, I always try blaming vm or drivers :) > > Until someone with real experience gives us the answer, > I'll work with you off the mailing list to try to narrow > down why this is happening. > > jim -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
