|To:||Dave Chinner <david@xxxxxxxxxxxxx>|
|Subject:||Re: xfs deadlock on buffer semaphore while reading directory|
|From:||Linda Walsh <xfs@xxxxxxxxx>|
|Date:||Sat, 09 Feb 2013 18:04:52 -0800|
|References:||<20130202192007.GS30577@xxxxxxxxxxxxxxxxxx> <510D6EDE.1080409@xxxxxxx> <510E054B.2070500@xxxxxxxxx> <20130206004442.GS2667@dastard>|
|User-agent:||Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:184.108.40.206) Gecko/20100228 Lightning/0.9 Thunderbird/220.127.116.11 Mnenhy/0.7.6.666|
Dave Chinner wrote:
I can't get the buffers to 'free' no matter what echo 3> /proc/sys/vm/drop_caches does nothing.What buffers are you talking about? The deadlock is in metadata buffer handling, which you can't directly see, and will never be able to entirely free via drop caches. if you are talking about what is reported by the "free" command, then that number can be ignored as it is mostly meaningless for XFS filesystems....
---- Actually was talking 'cache', not buffers... sorry, which I thought was mostly fs-data that was "freeable" (mostly). whereas because of the error in xfs_dump, I was concerned about it taking up all free memory (whereas normally, it doesn't matter). but I was trying to use echo 3>/proc/sys/vm/drop_caches, but that seemed to pretty much be ignored... But after boot and new kernel w/new and different problems, xfs_dump (the new version) works fine... ;) Sorry for any confusion.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||NICE MEETING YOU, ALLEN GLOBAL TRADING|
|Next by Date:||xfs_inode slab, Nikolay S.|
|Previous by Thread:||Re: xfs deadlock on buffer semaphore while reading directory, Linda Walsh|
|Next by Thread:||xfsdump showing system problems -- ? ideas?, Linda Walsh|
|Indexes:||[Date] [Thread] [Top] [All Lists]|