Going through my old email - I think I just fixed this - there was a bug in the delayed allocation handling in XFS which caused a memory leak due to a buffer_head reference count leak. The latest cvs
We upgraded our 8CPU/8GB Dell to 2.4.16 w/XFS last week and it works *much* better than previous 2.4 w/XFS kernels. No, hangs, crashes or VM weirdness, even under heavy loads. Thanks, Jason Allen Fer
You might want to sync up with the latest kernel when you get a chance, a couple of nasty bugs in the I/O path got squashed this week. I will ask Eric to update the 2.4.16 patches so that cvs is not
Hi Steve are this bugs present in the 1.0.2 Release too ? im using 2.4.9-13SGI_XFS_1.0.2 and im wondering if i need to upgrade it thank you -- Mihai RUSU "... and what if this is as good as it gets ?
The memory leak is not there, there is a deadlock triggered by an ext3 test program, but you need to mmap a chunk of a file, and then do a write into the file using that mmapped chunk as the write bu
Steve Lord wrote: On Tue, 2001-11-13 at 09:54, Jim Eshleman wrote: FWIW me too, on an 8-way 8.5GB (64GB HIGHMEM enabled) IBM Netfinity x370 (8500R) which functions as a production mail server. I curr
Jim Eshleman wrote: Steve Lord wrote: On Tue, 2001-11-13 at 09:54, Jim Eshleman wrote: FWIW me too, on an 8-way 8.5GB (64GB HIGHMEM enabled) IBM Netfinity x370 (8500R) which functions as a production
FWIW me too, on an 8-way 8.5GB (64GB HIGHMEM enabled) IBM Netfinity x370 (8500R) which functions as a production mail server. I currently run 2.4.9 with XFS and it stays up for about a week under he