Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

cpio:lstat failed AND cpio: mkdir failed

Posted on 2002-03-25
16
Medium Priority
?
1,629 Views
Last Modified: 2013-12-27
i use ximian desktop on my red hat linux 7.2 machine. ximian corporation released an new version of their software downloader, red-carpet. when i started red-carpet, he says that i must upgrade my (old) red-carpet with the new one. he keeps saying this and not did not let me do anything else. the problem is that upgrading (rpm -Uvh) crashes with the error "unpacking of archive failed: cpio: lstat failed - input/output error". i thought that maybe rpm was too old for that package. i have tried to upgrade rpm-4.0.3 to rpm-4.0.4. : "error: unpacking of archive failed: cpio: mkdir failed - input/output error". this is happening while i'm logged in as root. what's wrong?
guzu
0
Comment
Question by:guzu
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 10
  • 6
16 Comments
 

Author Comment

by:guzu
ID: 6895701
in the meantime, upgrading kernel and others was ok. rpm -K was ok.
0
 
LVL 40

Expert Comment

by:jlevie
ID: 6897062
The 7.2 version of rpm isn't the problem here. It works fine with Ximian. Do you have enough free space on the system for the unpacking of the rpm? Do a 'df' and see what your filesystems look like.
0
 

Author Comment

by:guzu
ID: 6898416
hello jlevie, i was waiting for you. df -h says i have 297 megs free. also i have 1gig of free swap memory. unpacking other packages was ok.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:guzu
ID: 6898420
red-carpet was downloaded several times and the error was the same: "cpio: lstata failed"....
0
 
LVL 40

Expert Comment

by:jlevie
ID: 6898481
Hmm, I've not encounted that error with Ximian. Are you using Ximian's tool to do the upgrade of RedCarpet? Normally it notices that it's version is old and asks to be allowed to do the update. I don't know what would happen if you tried to manually do the upgrade via an rpm.
0
 

Author Comment

by:guzu
ID: 6898527
well, that's how the all thing's started. i've tried to upgrade with ximian's tool. indeed, it asks to do the update. as you know, there's no other posibility so i pressed the update button. he says that everything is ok and it will restart i have to agree with that then he started over again and again. the i tried to do it manually, and i've found that errors. i've checked for the installed version of red-carpet and it was the old one... . i thought that it was rpm's fault (old rpm utility with new rpm package..) and the rest you know. could it be the hdd?
0
 

Author Comment

by:guzu
ID: 6898550
well, that's how the all thing's started. i've tried to upgrade with ximian's tool. indeed, it asks to do the update. as you know, there's no other posibility so i pressed the update button. he says that everything is ok and it will restart i have to agree with that then he started over again and again. the i tried to do it manually, and i've found that errors. i've checked for the installed version of red-carpet and it was the old one... . i thought that it was rpm's fault (old rpm utility with new rpm package..) and the rest you know. could it be the hdd?
0
 

Author Comment

by:guzu
ID: 6898552
sorry, i've reposted data during refresh...
0
 
LVL 40

Expert Comment

by:jlevie
ID: 6899244
Besides Ximian, what other updates have been applied to the system and have all that are applied come from RedHat?
0
 

Author Comment

by:guzu
ID: 6901996
all updates (maybe except libstdc3, i can't recall now) are from ximian or redhat
0
 

Author Comment

by:guzu
ID: 6904584
bad news jlevie, i've done e2fsck -nf on my root partition and there are A LOT of errors... . do you think that e2fsck-ing from slackware would fix the errors? or i will loose information? (i have some bad memories about running e2fsck on my ext3 filesystem...
0
 
LVL 40

Accepted Solution

by:
jlevie earned 600 total points
ID: 6905151
There shouldn't be any problem with using e2fsck on an ext3 file system. In reality an ext3 file system is an ext2 with journaling. I believe you should be able to force an fsck of all filesystems by 'touch /forcefsck' and rebooting. When prompted during the boot, interrupt the and ask for an extensive check.
0
 

Author Comment

by:guzu
ID: 6905197
well, last time i've tried this, i've lost everything so, i'll try to boot a slack and fsck without having the partition mounted.... thanks. i'll keep you up to date.
0
 
LVL 40

Expert Comment

by:jlevie
ID: 6905242
As far as I know it's safe to force the fsck at boot on a 7.x system. What you can't safely do is to manually fsck the root file system with it mounted and in use. The OS knows how to fsck the root at boot time, which is why the forcefsck technique exists.

Now, if you've got a flaky disk or controller all bets are off. The only times I've seen corruption of a file system involved bad disks/controllers or wierd software that ran with root privs. Under normal operation (oderly startup/shutdown of the OS) it's very unlikely for RH 7.2 to scramble anything on the system.
0
 

Author Comment

by:guzu
ID: 6905287
you are the expert onceagain. since i have strong reason to believe my hdd/mb don't match (for whatever reason), i've done the check from another partition/distribution. since i still can write you this, it seems to me that it works. also , the packages could now be installed on my system. probably, first step will be to replace the hdd. ok. now the points will be yours. thanks again.
0
 
LVL 40

Expert Comment

by:jlevie
ID: 6905308
I'm glad we go to the bottom of this. I'll admit to being a bit mystified as to the rpm failures until you mentioned the disk problem. At that point the cause of the failure became quite clear. I still don't know why the corruption occured, but a disk/mb mismatch could be the root cause.
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Hello fellow BSD lovers, I've created a patch process for patching openjdk6 for BSD (FreeBSD specifically), although I tried to keep all BSD versions in mind when creating my patch. Welcome to OpenJDK6 on BSD First let me start with a little …
I promised to write further about my project, and here I am.  First, I needed to setup the Primary Server.  You can read how in this article: Setup FreeBSD Server with full HDD encryption (http://www.experts-exchange.com/OS/Unix/BSD/FreeBSD/A_3660-S…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
In a previous video, we went over how to export a DynamoDB table into Amazon S3.  In this video, we show how to load the export from S3 into a DynamoDB table.
Suggested Courses

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question