Hello again,
I repeated my du test, causing excessive memory allocations by the
glusterfs client, with log level set to TRACE and a few additional
points of logging added within inode.c. After each forget(), for example:
[fuse-bridge.c:477:fuse_forget] glusterfs-fuse: got forget on inode
On Fri, Mar 26, 2010 at 03:40:27PM +0100, Amon Ott wrote:
Now we should check, whether fuse_forget() is called at all during the
test. I would not assume blindly that it is.
Added a counter to fuse_forget():
[2010-03-26 15:34:31] N [fuse-bridge.c:3203:fuse_thread_proc] fuse:
unmounting
Krzysztof Strasburger wrote:
On Mon, Mar 29, 2010 at 12:35:32PM +0530, Shehjar Tikoo wrote:
Krzysztof Strasburger wrote:
On Mon, Mar 29, 2010 at 11:48:44AM +0530, Shehjar Tikoo wrote:
This is a known problem. See a previous email on the devel list about it
at:
Could you please tell me, which function in glusterfs handles the
'forget()'
request?
check 'xlators/mount/fuse/src/fuse-bridge.c:612:fuse_forget()', thats the
entry point of 'forget()' calls.
Later inode_forget() calls each xlators's 'forget()' function.
To send forceful forgets to
On Friday 26 March 2010 wrote Amar Tumballi:
To send forceful forgets to glusterfs, do the following.
bash# echo 3 /proc/sys/vm/drop_caches
and see the memory usage after this.
I did it almost one year ago, as recommended by a member of the Gluster
team,
and repeated
On Friday 26 March 2010 wrote Krzysztof Strasburger:
On Fri, Mar 26, 2010 at 12:08:48PM +0100, Amon Ott wrote:
I can confirm this problem on our test system. glusterfs goes up to the
memory limit set for performance/io-cache (1.2 GB here), logs out of
memory errors and further access fails
On Fri, Mar 26, 2010 at 01:16:53PM +0100, Amon Ott wrote:
No, this should happen without any filters. What happens, if you disable
io-cache?
Disabled both io-cache and read-ahead. Now it only grew to 739 MB. Again,
drop_caches did not reduce that size, although it reduced the fuse_inode
On Friday 26 March 2010 wrote Amon Ott:
On Friday 26 March 2010 wrote Krzysztof Strasburger:
On Fri, Mar 26, 2010 at 12:08:48PM +0100, Amon Ott wrote:
I can confirm this problem on our test system. glusterfs goes up to the
memory limit set for performance/io-cache (1.2 GB here), logs out
On Friday 26 March 2010 wrote Krzysztof Strasburger:
On Fri, Mar 26, 2010 at 01:16:53PM +0100, Amon Ott wrote:
No, this should happen without any filters. What happens, if you
disable io-cache?
Disabled both io-cache and read-ahead. Now it only grew to 739 MB. Again,
drop_caches did
Hi,
Does your mount point has large number of files? Did you try droping caches
(using echo 3 /proc/sys/vm/drop_caches) after doing du? If yes, what were
the results?
regards,
On Thu, Mar 25, 2010 at 2:38 PM, Krzysztof Strasburger
stras...@chkw386.ch.pwr.wroc.pl wrote:
I upgraded today from
On Thursday 25 March 2010 06:38:00 am Krzysztof Strasburger wrote:
Dear other users of
glusterfs - are you at least able to reproduce this memory consumption
problem?
I had a problem like this with 3.0.2 and the Quickread translator. That is a
known issue. Do you have the same problem with
11 matches
Mail list logo
