Filesystem-Probleme

[Johannes Vieweg]

Hallo Liste,

nach langer Abstinenz habe ich mal wieder ein kleines technisches  
Problem.
Ich versuche gerade ein XEN-Image zu retten, bei einem Server-Absturz  
wurden auch die im XEN-Image enthaltenen Filesyteme beschädigt.
Mit kpartx konnte ich die FS in der dom-0 einbinden und die erste  
Partition reparieren. Die zweite macht aber Ärger:

wdf01:~ # e2fsck  /dev/mapper/loop0p2
e2fsck 1.38 (30-Jun-2005)
/dev/mapper/loop0p2: recovering journal
e2fsck: unable to set superblock flags on /dev/mapper/loop0p2

Okay, alternative Superblöcke suchen & auswählen:

wdf01:~ # mkfs.ext3 -n /dev/mapper/loop0p2
mke2fs 1.38 (30-Jun-2005)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
971520 inodes, 1939848 blocks
96992 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1988100096
60 block groups
32768 blocks per group, 32768 fragments per group
16192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

wdf01:~ # e2fsck -b 32768 -B 4096 /dev/mapper/loop0p2
e2fsck 1.38 (30-Jun-2005)
ext3 recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
/dev/mapper/loop0p2: recovering journal
ext3 recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
e2fsck: unable to set superblock flags on /dev/mapper/loop0p2

Das habe ich mit allen alternativen Superblöcken ausprobiert. Selbes  
Bild.
Wie gehe ich da am Besten weiter vor? Denn e2fsck -n sagt:

wdf01:~ # e2fsck -n /dev/mapper/loop0p2
e2fsck 1.38 (30-Jun-2005)
Warning: skipping journal recovery because doing a read-only  
filesystem check.
/dev/mapper/loop0p2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix? no

Inode 65240 was part of the orphaned inode list.  IGNORED.
Inode 68593 was part of the orphaned inode list.  IGNORED.
Deleted inode 633078 has zero dtime.  Fix? no

Inode 633119, i_size is 99314273, should be 99319808.  Fix? no

Inode 633119, i_blocks is 194176, should be 194184.  Fix? no

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(1308709--1308710) -(1308715--1308718)  
-1308727 -(1311318--1311321) -(1311324--1311333) -(1311335--1311349)  
-1315644 -1315660 -1316408 -(1316424--1316438)
Fix? no

Free blocks count wrong (990306, counted=941153).
Fix? no

Inode bitmap differences:  -65240 -68593 -633078
Fix? no

Free inodes count wrong (838668, counted=838542).
Fix? no


/dev/mapper/loop0p2: ********** WARNING: Filesystem still has errors  
**********

/dev/mapper/loop0p2: 132852/971520 files (1.3% non-contiguous),  
949542/1939848 blocks

Danke schonmal im Vorraus.

Johannes