On 19:19 Sat 10 May , Douglas A. Tutty wrote:
> On Fri, May 09, 2008 at 06:58:02PM -0400, Mitchell Laks wrote:
> > On 07:24 Fri 09 May , NN_il_Confusionario wrote:
> > > > * From: "Douglas A. Tutty" <firstname.lastname@example.org>
> > > >Does anyone know how much memory fsck needs to check a large filesystem?
> > In my case, the fsck took about 24 hours - amd64 machine with 1 terabyte ram
> > running kernel 2.4.18.
> I'm assuming that you mean 1 TB disk.
I had only 1G ram, but the raid was a 1T hardware raid.
> I don't suppose you know how much memory it used? If your / fs isn't 1
> TB, and you have 24 hrs to spend, you could check just that 1 TB
> filesysem with top (or something) running and see.
I did peak once via ssh while I was running fsck.ext3 (at that
time which was close to hour 20 ). As I recall I thought I would see
large numbers in the %cpu and %mem columns. I dont remember
exactly what I saw, but it was something like 10% cpu and 10% mem
but I can't swear. It certainly was not hogging more. I perhaps should
have done something with nice to make it more agressive...
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org