Hi,

I have RedHat Enterprise Linux AS release 3 installed on an intel
server with kernel 2.4.21-27.0.2.EL. Commands like tar, unzip run
extremely slow. To untar a 4 MB it takes over 30min.

Has anyone run into these issues before and knows of any solution ?

Thanks,
Kevin.

kejoseph@hotmail.com wrote:
> Hi,
>
> I have RedHat Enterprise Linux AS release 3 installed on an intel server
> with kernel 2.4.21-27.0.2.EL. Commands like tar, unzip run extremely
> slow. To untar a 4 MB it takes over 30min.
>
> Has anyone run into these issues before and knows of any solution ?
>
I have RHEL ES 3, same kernel (SMP version). I do not have this problem.


--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 22:10:00 up 9 days, 15:26, 4 users, load average: 3.04, 3.11, 3.09

kejoseph@hotmail.com wrote:
> Hi,
>
> I have RedHat Enterprise Linux AS release 3 installed on an intel
> server with kernel 2.4.21-27.0.2.EL. Commands like tar, unzip run
> extremely slow. To untar a 4 MB it takes over 30min.
>
> Has anyone run into these issues before and knows of any solution ?
>
> Thanks,
> Kevin.
>
Don't have Red Hat FC3 I use Slackware but asks, System RAM, processor
speed? I am running an AMD K6-2 500 with 256MB ram and a 36MB file , eg
the new Linux 2.6.11.7 kernel takes about 6 to 7 minutes total time to
decompress

kejoseph@hotmail.com wrote:
> Hi,
>
> I have RedHat Enterprise Linux AS release 3 installed on an intel
> server with kernel 2.4.21-27.0.2.EL. Commands like tar, unzip run
> extremely slow. To untar a 4 MB it takes over 30min.

If it's so slow then it has to be a problem with the harddrive.
Probably your motherboard is not properly detected by RHEL AS.
The best you can do is call Red Hat and use the support you've
paid for.

> Thanks,
> Kevin.

Regards.

--

Jose Maria Lopez Hernandez
Director Tecnico de bgSEC
jkerouac@bgsec.com
bgSEC Seguridad y Consultoria de Sistemas Informaticos
http://www.bgsec.com
ESPAÑA

The only people for me are the mad ones -- the ones who are mad to live,
mad to talk, mad to be saved, desirous of everything at the same time,
the ones who never yawn or say a commonplace thing, but burn, burn, burn
like fabulous yellow Roman candles.
-- Jack Kerouac, "On the Road"

"Jose Maria Lopez Hernandez" <jkerouac@bgsec.com> wrote in message
news:42675809_2@x-privat.org...
> kejoseph@hotmail.com wrote:
>> Hi,
>>
>> I have RedHat Enterprise Linux AS release 3 installed on an intel
>> server with kernel 2.4.21-27.0.2.EL. Commands like tar, unzip run
>> extremely slow. To untar a 4 MB it takes over 30min.
>
> If it's so slow then it has to be a problem with the harddrive.
> Probably your motherboard is not properly detected by RHEL AS.
> The best you can do is call Red Hat and use the support you've
> paid for.

Or he's swapping to death for other reasons. But backing up the system and
running an fsck at reboot time is probably a really, really good idea.

Jean-David Beyer wrote:
> kejoseph@hotmail.com wrote:
>
>>Hi,
>>
>>I have RedHat Enterprise Linux AS release 3 installed on an intel server
>>with kernel 2.4.21-27.0.2.EL. Commands like tar, unzip run extremely
>>slow. To untar a 4 MB it takes over 30min.
>>
>>Has anyone run into these issues before and knows of any solution ?
>>
>
> I have RHEL ES 3, same kernel (SMP version). I do not have this problem.
>
>
I just ran a little test:

$ time tar -c *.pdf >/tmp/frammis

real 0m0.147s
user 0m0.000s
sys 0m0.140s

Wall clock time appeared to be instantaneous.

$ ls -l /tmp/frammis
-rw-r----- 1 jdbeyer jdbeyer 12646400 Apr 21 08:11 /tmp/frammis

So a 12+ megabyte file (three times your 4 Megabytes; a bunch of .pdf files,
actually) took essentially no time to run, not 30 minutes.

--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 08:10:00 up 10 days, 1:26, 5 users, load average: 3.41, 3.32, 3.28

On Wed, 20 Apr 2005 at 23:25 GMT, kejoseph@hotmail.com eloquently wrote:
> Hi,
>
> I have RedHat Enterprise Linux AS release 3 installed on an intel
> server with kernel 2.4.21-27.0.2.EL. Commands like tar, unzip run
> extremely slow. To untar a 4 MB it takes over 30min.
>
> Has anyone run into these issues before and knows of any solution ?
This happened a long time back and the problem seemed to be with nscd
and/or initscripts. See
http://alphalinux.org/archives/axp-l...1998/0086.html and
https://www.redhat.com/archives/axp-.../msg00190.html

Why it is happening in your case is anyone's guess.

N.Emile...
--
Registered Linux User # 125653 (http://counter.li.org) | Please remove
Certified: 75% bastard, 42% of which is tard. | '.invalid'
http://www.thespark.com/bastardtest | to reply.
Switch to: http://www.speakeasy.net/refer/190653

Tried various options - nothing seems to work...including upgrading to
2.4.21-27.0.2.

I see the following errors in the log files. Dont know whether they are
related.

Apr 21 11:14:09 myserver rc: Starting pcmcia: succeeded
Apr 21 11:14:09 myserver netfs: Mounting other filesystems: succeeded
Apr 21 11:14:09 myserver autofs: automount startup succeeded
Apr 21 11:14:10 myserver insmod:
/lib/modules/2.4.21-27.0.2.ELsmp/kernel/drivers/parport/parport_pc.o:
init_module: Device or resource busy
Apr 21 11:14:10 myserver insmod: Hint: insmod errors can be caused by
incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
Apr 21 11:14:10 myserver insmod:
/lib/modules/2.4.21-27.0.2.ELsmp/kernel/drivers/parport/parport_pc.o:
insmod parport_lowlevel failed
Apr 21 11:14:10 myserver kernel: lp: driver loaded but no devices found
Apr 21 11:14:10 myserver kernel: usb.c: registered new driver serial
Apr 21 11:14:10 myserver kernel: usbserial.c: USB Serial support
registered for Generic

I found the following parport errors in the log file - dont know
whether they are related.

Apr 21 11:14:09 myserver rc: Starting pcmcia: succeeded
Apr 21 11:14:09 myserver netfs: Mounting other filesystems: succeeded
Apr 21 11:14:09 myserver autofs: automount startup succeeded
Apr 21 11:14:10 myserver insmod:
/lib/modules/2.4.21-27.0.2.ELsmp/kernel/drivers/parport/parport_pc.o:
init_module: Device or resource busy
Apr 21 11:14:10 myserver insmod: Hint: insmod errors can be caused by
incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
Apr 21 11:14:10 myserver insmod:
/lib/modules/2.4.21-27.0.2.ELsmp/kernel/drivers/parport/parport_pc.o:
insmod parport_lowlevel failed
Apr 21 11:14:10 myserver kernel: lp: driver loaded but no devices found
Apr 21 11:14:10 myserver kernel: usb.c: registered new driver serial
Apr 21 11:14:10 myserver kernel: usbserial.c: USB Serial support
registered for Generic

Tried various options ...including upgrading to 2.4.21-27.0.2 - nothing
seems to help.

I see the following errors in the log files. Dont know whether they are
related.

Apr 21 11:14:09 myserver rc: Starting pcmcia: succeeded
Apr 21 11:14:09 myserver netfs: Mounting other filesystems: succeeded
Apr 21 11:14:09 myserver autofs: automount startup succeeded
Apr 21 11:14:10 myserver insmod:
/lib/modules/2.4.21-27.0.2.ELsmp/kernel/drivers/parport/parport_pc.o:
init_module: Device or resource busy
Apr 21 11:14:10 myserver insmod: Hint: insmod errors can be caused by
incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
Apr 21 11:14:10 myserver insmod:
/lib/modules/2.4.21-27.0.2.ELsmp/kernel/drivers/parport/parport_pc.o:
insmod parport_lowlevel failed
Apr 21 11:14:10 myserver kernel: lp: driver loaded but no devices found
Apr 21 11:14:10 myserver kernel: usb.c: registered new driver serial
Apr 21 11:14:10 myserver kernel: usbserial.c: USB Serial support
registered for Generic