Platte hinueber?
Hallo zusammen,
wir haben einen DS9000 bei Hetzner mit RAID1 stehen.
Eine Platte im Raid wurde degraded, und ich habe jetzt mal einen fsck
drueber laufen lassen.
Bevor ich nun den Hetzner-Support mobilisiere zum Plattentausch, meine
Frage, ob man anhand der Ausgabe von fsck erkennen kann, ob die Platte
gehimmelt ist oder es "bloss" ein Fehler im File-System ist, welches
durch fsck behoben werden kann?
Hier mal die Ausgabe des fsck:
============ [ snip ] ================
root@rescue /mnt # fsck /dev/sda2
fsck 1.40-WIP (14-Nov-2006)
e2fsck 1.40-WIP (14-Nov-2006)
/dev/sda2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 26836996 has zero dtime. Fix<y>? no
Inodes that were part of a corrupted orphan linked list found. Fix<y>? no
Inode 26836997 was part of the orphaned inode list. IGNORED.
Inode 26836998 was part of the orphaned inode list. IGNORED.
Inode 26836999 was part of the orphaned inode list. IGNORED.
Inode 26837000 was part of the orphaned inode list. IGNORED.
Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 30670906: 61639348 61639348
61640116 61640116 61640228 61640228
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
(There are 1 inodes containing multiply-claimed blocks.)
File /home/CompassHotline/webdemo/webdemo_uk_pos.dump (inode
#30670906, mod time Wed May 14 16:30:04 2008)
has 6 multiply-claimed block(s), shared with 0 file(s):
Clone multiply-claimed blocks<y>? no
Delete file<y>? 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: +(61454337--61454343) +(61461483--61462512)
+(61639174--61639315) -61639316 +(61639317--61640083) -61640084
-61640196 +(61640198--61641650) +(61648905--61650943)
+(61851260--61852161) +(61862536--61865983) +(61867520--61868031)
+(61871503--61872122) +(61877562--61888511) +(61888520--61890559)
+(61890568--61894655) +(61899720--61899770) +(61915163--61917183)
+(61917192--61925416)
Fix<y>?
Free blocks count wrong for group #1875 (21849, counted=22886).
Fix<y>? no
Free blocks count wrong for group #1881 (25690, counted=30091).
Fix<y>? no
Free blocks count wrong for group #1887 (27904, counted=32254).
Fix<y>? no
Free blocks count wrong for group #1888 (14022, counted=32232).
Fix<y>? no
Free blocks count wrong for group #1889 (15838, counted=26135).
Fix<y>? no
Free blocks count wrong (75521658, counted=75559953).
Fix<y>? no
Inode bitmap differences: -(26836996--26837000)
Fix<y>? no
/dev/sda2: ********** WARNING: Filesystem still has errors **********
/dev/sda2: 50758/38813696 files (1.2% non-contiguous), 2096389/77618047 blocks
Message from syslogd@localhost at Thu May 15 16:26:00 2008 ...
localhost kernel: Oops: 0000 [1] SMP
Warning... fsck.ext3 for device /dev/sda2 exited with signal 9.
Message from syslogd@localhost at Thu May 15 16:26:00 2008 ...
localhost kernel: CR2: 0000000000000020
============ [ snap ] ================
Vielen Dank im Voraus & Gruss
Gregor
--
what's puzzlin' you, is the nature of my game
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @ http://pgpkeys.pca.dfn.de:11371
Reply to: