I've been hunting an insidious problem whereby during heavy
incremental indexing operations in production on redhat el3 machine I
notice that the java process has a lot of open files which appear to
be deleted.
Now, before anyone jumps in, yes I know the # open file limit needs
to be in
On Sunday 12 February 2006 22:48, John Haxby wrote:
> Otis Gospodnetic wrote:
>
> >I'm somewhat familiar with ext3 vs. ReiserFS stuff, but that's not really
what I'm after (finding a better/faster FS). What I'm wondering is about
different block sizes on a single (ext3) FS.
> >If I understand b
I just through in the reiserfs suggestion since it's
usually nott a 1k vs 4k blocksize issue as much as it
is how many contiguous files consume those blocksizes.
If they're small and random reiserfs will smoke ext3,
if they're large ext3 will be lighter weight and if
they're really large and somewh
Otis Gospodnetic wrote:
I'm somewhat familiar with ext3 vs. ReiserFS stuff, but that's not really what
I'm after (finding a better/faster FS). What I'm wondering is about different
block sizes on a single (ext3) FS.
If I understand block sizes correctly, they represent a chunk of data that th
On 2/12/06, Otis Gospodnetic <[EMAIL PROTECTED]> wrote:
> If I understand block sizes correctly, they represent a chunk of data that
> the FS will read in a single read.
The filesystem block size is just the logical size of allocation units
for the FS, and does not put any cap on the amount of da
Hi,
I'm somewhat familiar with ext3 vs. ReiserFS stuff, but that's not really what
I'm after (finding a better/faster FS). What I'm wondering is about different
block sizes on a single (ext3) FS.
If I understand block sizes correctly, they represent a chunk of data that the
FS will read in a s
