[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47BAF3FF.3070300@wpkg.org>
Date: Tue, 19 Feb 2008 16:21:35 +0100
From: Tomasz Chmielewski <mangoo@...g.org>
To: Chris Mason <chris.mason@...cle.com>
Cc: Theodore Tso <tytso@....edu>, Andi Kleen <andi@...stfloor.org>,
LKML <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: very poor ext3 write performance on big filesystems?
Chris Mason schrieb:
> On Tuesday 19 February 2008, Tomasz Chmielewski wrote:
>> Theodore Tso schrieb:
>>
>> (...)
>>
>>> The following ld_preload can help in some cases. Mutt has this hack
>>> encoded in for maildir directories, which helps.
>> It doesn't work very reliable for me.
>>
>> For some reason, it hangs for me sometimes (doesn't remove any files, rm
>> -rf just stalls), or segfaults.
>
> You can go the low-tech route (assuming your file names don't have spaces in
> them)
>
> find . -printf "%i %p\n" | sort -n | awk '{print $2}' | xargs rm
Why should it make a difference?
Does "find" find filenames/paths faster than "rm -r"?
Or is "find once/remove once" faster than "find files/rm files/find
files/rm files/...", which I suppose "rm -r" does?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists