[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Ext2fs problem not cured by e2fsck



Oliver Elphick wrote:
> 
> I had a power failure yesterday and I have a corrupted filesystem as
> a result.  When fsck tried to repair it, it produced some strange
> messages, and seems to be unable to repair the problem.
> 
> I am also getting a 'no space on device' message, but 'df -k' still
> shows 273Mb available.
> 
> This is what I get:
>   Script started on Fri Aug 29 06:23:01 1997
>   linda# fsck -y /dev/sda1
>   Parallelizing fsck version 1.10 (24-Apr-97)
>   e2fsck 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
>   /dev/sda1 contains a file system with errors, check forced.
>   Pass 1: Checking inodes, blocks, and sizes
>   Error reading block 2103793 (Success) while reading indirect blocks of inode 477625.  Ignore error? yes
> 
>   Error reading block 2102843 (Success) while reading indirect blocks of inode 477624.  Ignore error? yes
> 
>   ... and so on ...
> 
>   Pass 2: Checking directory structure
>   Error reading block 2129105 (Success).  Ignore error? yes
> 
>   Directory inode 477567, block 2, offset 0: directory corrupted
>   Salvage? yes
> 
>   Error writing block 2129105 (Success).  Ignore error? yes
> 
>   Pass 3: Checking directory connectivity
>   Pass 4: Checking reference counts
>   Pass 5: Checking group summary information
>   Error reading block 2097163 (Success) while reading inode and block bitmaps.  Ignore error? yes
> 
>   Error reading block 2097164 (Success) while reading inode and block bitmaps.  Ignore error? yes
>   ... and so on ...
> 
>   Fix summary information? yes
> 
>   Block bitmap differences: +2097153 +2097154 +2097155 +2097156 ... and lots more ...
>   Padding at end of block bitmap is not set. Fix? yes
> 
> 
>   /dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
>   /dev/sda1: 149930/536576 files (6.7% non-contiguous), 1770388/2144646 blocks
>   Error writing block 2097163 (Success) while writing block bitmaps.  Ignore error? yes
> 
>   Error writing block 2105355 (Success) while writing block bitmaps.  Ignore error? yes
> 
>   Error writing block 2113547 (Success) while writing block bitmaps.  Ignore error? yes
> 
>   Error writing block 2121739 (Success) while writing block bitmaps.  Ignore error? yes
> 
>   Error writing block 2129931 (Success) while writing block bitmaps.  Ignore error? yes
> 
>   Error writing block 2138123 (Success) while writing block bitmaps.  Ignore error? yes
> 
>   Error writing block 2097153 (Success).  Ignore error? yes
> 
>   Error writing block 2097154 (Success).  Ignore error? yes
> 
>   ... and so on ...
> 
> This is the third or fourth time I've run fsck, and the errors keep on occurring.
> 
> I think I will have to destroy and rebuild the partition, but I'd like to
> understand what is going on here.

Maybe the heads made scratches when the power failed and the medium is
corrupt.
You could try to make a backup and do a pattern test on the partition
(should be an option for mke2fs) like it's done during installation.

May the source be with you.
			Mrvn


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .


Reply to: