Problem with file system

Ameet Nanda ameet.nanda at wipro.com
Thu Oct 25 09:18:20 UTC 2007


Hi,
I tried to untar using the command tar -xvzmf.

The error I got after tar runs for sometime was :
---------------------------------------
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers

gzip: stdin: invalid compressed data--crc error
tar: Child returned status 1
tar: Error exit delayed from previous errors
----------------------------------------

on doing a fsck.ext3 i get the result as:
--------------------------------------------------------------

/dev/sda2: ********** WARNING: Filesystem still has errors **********


   15162 inodes used (0.50%)
      84 non-contiguous inodes (0.6%)
         # of inodes with ind/dind/tind blocks: 1370/52/0
  605645 blocks used (10.05%)
       0 bad blocks
       2 large files

   11832 regular files
     886 directories
       0 character device files
       0 block device files
       0 fifos
4294967294 links
    2436 symbolic links (2414 fast symbolic links)
       0 sockets
--------
   15150 files
---------------------------------------------------------------------------

-
Ameet

On Thu, 2007-10-25 at 10:07 +0200, Christian Kujau wrote:

> On Wed, October 24, 2007 11:55, Naxor wrote:
> > While I untar a large archive on  xfs , ext3 (ver 1.3 and ver 1.4) file
> > systems , on ppc processor and kernel ver 2.6.21 , I get an error. Also
> > sometimes, on ext3 (1.3 and 1.4) the file system goes read-only while
> > untarring.
> 
> can you please post the errors from your syslog, when this happens? Also,
> did you fsck.ext3 your filesystem lately?
> 
> Christian.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20071025/edf595d3/attachment.htm>


More information about the Ext3-users mailing list