We changed the way we do memory allocation to avoid needing large contiguous chunks of memory a bit over a year ago; that solved the main OOM problem we were getting reported with highly fragmented f
We changed the way we do memory allocation to avoid needing large contiguous chunks of memory a bit over a year ago; that solved the main OOM problem we were getting reported with highly fragmented f
We changed the way we do memory allocation to avoid needing large contiguous chunks of memory a bit over a year ago; that solved the main OOM problem we were getting reported with highly fragmented f
..... Oh, that problem. The issue is that allocation beyond EOF (the normal way we prevent fragmentation in this case) gets truncated off on file close. Even NFS request is processed by doing: open w
David Chinner wrote: On Tue, Jun 05, 2007 at 03:23:50PM -0700, Michael Nishimoto wrote: David Chinner wrote: On Wed, May 30, 2007 at 09:49:38AM -0700, Michael Nishimoto wrote: Hello, Has anyone done
Vlad Apostolov wrote: No, Dave is right. The example worked because the extent hint was the same size as the filesystem block. Regards, Vlad Note - i don't think extent size hints alone will help as
..... Oh, that problem. The issue is that allocation beyond EOF (the normal way we prevent fragmentation in this case) gets truncated off on file close. Even NFS request is processed by doing: open w
..... So has the community - there may even be patches floating around... That's not a problem for slowly growing log files - they will eventually use the space. I'm not saying that the truncate shou
If you've got 10TB of free space, the allocator should be doing a better job than that ;) Yes, that is a fair observation. The first case is really only a concern when the maximum extent size (8GB on
Yes, that's fragmented - it has 4 orders of magnitude more extents than optimal - and the extents are too small to allow reads or writes to acheive full bandwidth on high end raid configs.... Fair e
Hi Mike, This seems a flawed way to look at this to me - in practice, almost noone would have files that large. While filesystem sizes increase and can be expected to continue to increase, I'd expect
We changed the way we do memory allocation to avoid needing large contiguous chunks of memory a bit over a year ago; that solved the main OOM problem we were getting reported with highly fragmented f
We changed the way we do memory allocation to avoid needing large contiguous chunks of memory a bit over a year ago; that solved the main OOM problem we were getting reported with highly fragmented f
We changed the way we do memory allocation to avoid needing large contiguous chunks of memory a bit over a year ago; that solved the main OOM problem we were getting reported with highly fragmented f
..... Oh, that problem. The issue is that allocation beyond EOF (the normal way we prevent fragmentation in this case) gets truncated off on file close. Even NFS request is processed by doing: open w
David Chinner wrote: On Tue, Jun 05, 2007 at 03:23:50PM -0700, Michael Nishimoto wrote: David Chinner wrote: On Wed, May 30, 2007 at 09:49:38AM -0700, Michael Nishimoto wrote: Hello, Has anyone done
Vlad Apostolov wrote: No, Dave is right. The example worked because the extent hint was the same size as the filesystem block. Regards, Vlad Note - i don't think extent size hints alone will help as
..... Oh, that problem. The issue is that allocation beyond EOF (the normal way we prevent fragmentation in this case) gets truncated off on file close. Even NFS request is processed by doing: open w
..... So has the community - there may even be patches floating around... That's not a problem for slowly growing log files - they will eventually use the space. I'm not saying that the truncate shou
If you've got 10TB of free space, the allocator should be doing a better job than that ;) Yes, that is a fair observation. The first case is really only a concern when the maximum extent size (8GB on