xfs
[Top] [All Lists]

[Bug 345] Memory allocation failure

To: xfs-master@xxxxxxxxxxx
Subject: [Bug 345] Memory allocation failure
From: bugzilla-daemon@xxxxxxxxxxx
Date: Mon, 12 Jul 2004 12:22:28 -0700
Sender: linux-xfs-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=345





------- Additional Comments From xfs@xxxxxxxxxxxxxxxx  2004-12-07 12:22 PDT 
-------
Yes, that partition is exlusively used for downloading and p2p-programs. It's 
almost constantly full, 
and on top of that almost continually in use by at least one p2p-program.

I use mldonkey(ed2k) and azureus(bittorrent), and both of these are set to 
start with sparse files, 
even further fragmenting the filesystem. On top of that, I often use azureus 
over nfs.. 

So, yes, it's probably very, VERY fragmented..

I'll run xfs_fsr for a night or so, and get back on if I still get memory 
allocation error.

Compiling and testing patches (unless destructive) is no problem for me.

Apparently cw was able to reproduce the bug by running multiple cd-burns after 
eachother, but I'm 
not burning any cd's on that computer.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


<Prev in Thread] Current Thread [Next in Thread>