Filesystemfehler nach Stromausfall

meine Videopartition hat das Format "reiserfs". Nach einem stromausfall bleibt der rechner beim hochfahren mit der Fehlermeldung stehen, daß irgend was am filesystem nicht stimmt. Habe mithilfe der knoppix cd die entsprechende Partition aus der etc/fstab gelöscht und nach dem Hochfahren manuell gemountet. Der zugriff und das hochfahren klappte auf diese weiße. Aber wie repariere ich die entsprechende Partition, so das ich sie wieder in die etc/fstab eintragen kann. Hatte das problem schon mal. Damals hab ich die entsprechnde Partition formatiert dann gings wieder. Aber dieses mal möchte ich mehr über das filesystem erfahren und den FEhler reparieren.

Ich hatte auch schon ext3 am laufen, da ging zwar das hochfahren des rechners schneller (wegen kürzeren filesystemcheck) aber der zugriff auf die Filme dauerte länger, was mir nicht gefiel. Wenn ich Menü/ aufzeichnungen/ einen Film anwählte dauerte es ein paar sekunden bis der Film anlief was bei reiserfs nicht der Fall ist.

Hatte jemand ähnliche probleme nach einen Stromausfall bzw kennt sich jemand mit dem Filesystemcheck unter reiserfs aus?

Könnte mann fieleciht zum beschleunigten hochfahren des rechners auf den Filesystemcheck ganz verzichten

Mit "linux:~ # reiserfsck /dev/hdb2 --rebuild-tree" konnte ich zwar das filsystem reparieren, aber eine lösung für diesen Bug ist das ja auch nicht. Wenn das nächste mal wieder Stromausfall bei einem GEwitter ist steh ich ja erneut vor dem Problem.

Was Spräche dagegen wenn ich die Video Partitionen aus der Fstab herausnehmen würde und das mounten in die runvdr verlegen würde. Dann würde der rechner beim auftreten des Problems trotzdem hochfahren. Was bringt der Standartmäsige filesystemcheck beim hochfahren, wenn der Bootprozess bei einem Fehler gestoppt wird und nicht gleich der Fehler repariert. Oder giebt es patches oder optionen für reiser fs die zu einem sofortigen reparieren des beschädigten filesystems führen

linux:~ # umount /dev/hdb2
umount: /bigPart2: device is busy
linux:~ # umount /dev/hdb2
linux:~ # mount /dev/hdb2 /bigPart2
linux:~ # umount /dev/hdb2
You have new mail in /var/spool/mail/root
linux:~ # umount /dev/hdb2
umount: /dev/hdb2: not mounted
linux:~ # reiserfsck /dev/hdb2
reiserfsck 3.6.9 (2003 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to reiserfs-list@namesys.com, **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
*************************************************************

Will read-only check consistency of the filesystem on /dev/hdb2
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Sun Jul 18 09:44:33 2004
###########
Replaying journal..
0 transactions replayed
Checking internal tree../135 (of 135)block 2138468: The level of the node (0) is not correct, (2) expected
the problem in the internal node occured (2138468), whole subtree is skipped
finished
Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs.
Bad nodes were found, Semantic pass skipped
1 found corruptions can be fixed only when running with --rebuild-tree
###########
reiserfsck finished at Sun Jul 18 09:46:42 2004
###########
linux:~ # reiserfsck /dev/hdb2 --rebuild-tree
reiserfsck 3.6.9 (2003 www.namesys.com)

*************************************************************
** Do not run the program with --rebuild-tree unless **
** something is broken and MAKE A BACKUP before using it. **
** If you have bad sectors on a drive it is usually a bad **
** idea to continue using it. Then you probably should get **
** a working hard drive, copy the file system from the bad **
** drive to the good one -- dd_rescue is a good tool for **
** that -- and only then run this program. **
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to reiserfs-list@namesys.com, **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
*************************************************************

Will rebuild the filesystem (/dev/hdb2) tree
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
Replaying journal..
0 transactions replayed
###########
reiserfsck --rebuild-tree started at Sun Jul 18 09:50:18 2004
###########

Pass 0:
####### Pass 0 #######
Loading on-disk bitmap .. ok, 20994701 blocks marked used
Skipping 9307 blocks (super block, journal, bitmaps) 20985394 blocks will be read
0%....20%....40%block 22705005: The number of items (12) is incorrect, should be (0) - corrected
block 22705005: The free space (3075) is incorrect, should be (4072) - corrected
..block 24432705: The free space (2071) is incorrect, should be (4072) - corrected
block 24432708: The free space (2073) is incorrect, should be (4072) - corrected
.block 24602499: The number of items (16) is incorrect, should be (0) - corrected
block 24602499: The free space (31) is incorrect, should be (4072) - corrected
block 24733308: The free space (2993) is incorrect, should be (4072) - corrected
.block 25419353: The number of items (12) is incorrect, should be (0) - corrected
block 25419353: The free space (8787) is incorrect, should be (4072) - corrected
block 25484202: The free space (5928) is incorrect, should be (4072) - corrected
60%block 26512611: The number of items (12) is incorrect, should be (0) - corrected
block 26512611: The free space (3075) is incorrect, should be (4072) - corrected
block 26836795: The free space (2073) is incorrect, should be (4072) - corrected
...block 30238238: The free space (2890) is incorrect, should be (4072) - corrected
block 30249389: The number of items (14) is incorrect, should be (0) - corrected
block 30249389: The free space (41511) is incorrect, should be (4072) - corrected
block 30324360: The free space (3712) is incorrect, should be (4072) - corrected
block 30324362: The free space (3714) is incorrect, should be (4072) - corrected
block 30324366: The free space (3716) is incorrect, should be (4072) - corrected
block 30324368: The free space (3718) is incorrect, should be (4072) - corrected
.80%....100% left 0, 9143 /sec
569 directory entries were hashed with "r5" hash.
"r5" hash is selected
Flushing..finished
Read blocks (but not data blocks) 20985394
Leaves among those 20844
- leaves all contents of which could not be saved and deleted 15
Objectids found 670

Pass 1 (will try to insert 20829 leaves):
####### Pass 1 #######
Looking for allocable blocks .. finished
0%....20%....40%....60%....80%....100% left 0, 111 /sec
Flushing..finished
20829 leaves read
20829 inserted
- pointers in indirect items pointing to metadata 15 (zeroed)
non-unique pointers in indirect items (zeroed) 581
####### Pass 2 #######
Flushing..finished
Pass 3 (semantic):
####### Pass 3 #########
/Backup/07_07_04/suse.001vpf-10680: The file [137 140] has the wrong block count in the StatData (1160816) - corrected to (1160776)
/09_07_04/suse.001vpf-10680: The file [103 108] has the wrong block count in the StatData (1436168) - corrected to (1436104)
/Aufzeichnungen1/Die_Killerhandrebuild_semantic_pass: The entry [563 564] ("2004-07-17.23.02.50.99.rec") in directory [4 563] points to nowhere - is removed
vpf-10650: The directory [4 563] has the wrong size in the StatData (96) - corrected to (48)
Flushing..finished
Files found: 440
Directories found: 122
Symlinks found: 6
Names pointing to nowhere (removed): 1
Pass 3a (looking for lost dir/files):
####### Pass 3a (lost+found pass) #########
Looking for lost directories:
/2145_96561get_next_directory_item: The entry ".." of the directory [2145 96561] pointes to [80 2145], instead of [2 567] - corrected
rebuild_semantic_pass: The entry [96561 96633] ("image") in directory [2145 96561] points to nowhere - is removed
rebuild_semantic_pass: The entry [96561 96562] ("filter") in directory [2145 96561] points to nowhere - is removed
vpf-10650: The directory [2145 96561] has the wrong size in the StatData (96) - corrected to (48)
Looking for lost files:
vpf-10680: The file [2145 96424] has the wrong block count in the StatData (312) - corrected to (0)
vpf-10680: The file [2145 96553] has the wrong block count in the StatData (1208) - corrected to (0)
vpf-10680: The file [2145 96560] has the wrong block count in the StatData (1456) - corrected to (0)
vpf-10680: The file [2145 96736] has the wrong block count in the StatData (160) - corrected to (0)
vpf-10680: The file [115668 164337] has the wrong block count in the StatData (8) - corrected to (0)
vpf-10680: The file [115668 164339] has the wrong block count in the StatData (16) - corrected to (0)
vpf-10680: The file [115668 164341] has the wrong block count in the StatData (24) - corrected to (0)
vpf-10680: The file [115668 164343] has the wrong block count in the StatData (16) - corrected to (0)
vpf-10680: The file [115668 164345] has the wrong block count in the StatData (48) - corrected to (0)
vpf-10680: The file [115668 164346] has the wrong block count in the StatData (16) - corrected to (0)
vpf-10680: The file [115668 164348] has the wrong block count in the StatData (24) - corrected to (0)
vpf-10680: The file [115668 164349] has the wrong block count in the StatData (8) - corrected to (0)
vpf-10680: The file [117697 165835] has the wrong block count in the StatData (16) - corrected to (0)
vpf-10680: The file [117697 165837] has the wrong block count in the StatData (48) - corrected to (0)
vpf-10680: The file [117988 166165] has the wrong block count in the StatData (56) - corrected to (0)
vpf-10680: The file [119358 167503] has the wrong block count in the StatData (32) - corrected to (0)
vpf-10680: The file [119358 167505] has the wrong block count in the StatData (16) - corrected to (0)
vpf-10680: The file [119358 167507] has the wrong block count in the StatData (16) - corrected to (0)
vpf-10680: The file [119358 167509] has the wrong block count in the StatData (24) - corrected to (0)
vpf-10680: The file [119358 167511] has the wrong block count in the StatData (16) - corrected to (0)
vpf-10680: The file [140622 140782] has the wrong block count in the StatData (8) - corrected to (0)
vpf-10680: The file [147670 147794] has the wrong block count in the StatData (400) - corrected to (0)
vpf-10680: The file [147670 147795] has the wrong block count in the StatData (16) - corrected to (0)
vpf-10680: The file [147670 147796] has the wrong block count in the StatData (112) - corrected to (0)
vpf-10680: The file [147670 147798] has the wrong block count in the StatData (40) - corrected to (0)
vpf-10680: The file [147670 147799] has the wrong block count in the StatData (56) - corrected to (0)
vpf-10680: The file [149250 149317] has the wrong block count in the StatData (56) - corrected to (0)
vpf-10680: The file [149250 149319] has the wrong block count in the StatData (48) - corrected to (0)
vpf-10680: The file [149250 149324] has the wrong block count in the StatData (16) - corrected to (0)
vpf-10680: The file [149250 149326] has the wrong block count in the StatData (64) - corrected to (0)
vpf-10680: The file [149250 149329] has the wrong block count in the StatData (40) - corrected to (0)
Flushing..finished
Objects without names 82
Dirs linked to /lost+found: 1
Files linked to /lost+found 81
Pass 4 - finished done 7969, 28 /sec
Deleted unreachable items 8
Flushing..finished
Syncing..finished
###########
reiserfsck finished at Sun Jul 18 10:34:39 2004
###########
linux:~ # reiserfsck /dev/hdb2
reiserfsck 3.6.9 (2003 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to reiserfs-list@namesys.com, **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
*************************************************************

Will read-only check consistency of the filesystem on /dev/hdb2
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Sun Jul 18 10:51:13 2004
###########
Replaying journal..
0 transactions replayed
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
Leaves 20828
Internal nodes 133
Directories 123
Other files 527
Data block pointers 20965700 (558 of them are zero)
Safe links 0
###########
reiserfsck finished at Sun Jul 18 10:53:45 2004
###########
linux:~ #

Nach der reperatur von Reiser fs ging zwar das booten wieder aber einige filme sogar neu aufgenommene zeigten Bildfehler.

Habe jetzt alle meine Partitionen auser meine Bootpartition auf XFS umgestellt.
Vom einschalten bis zum fernsehbild daert es jetzt 55 sekunden was zuerst 100 sekunden dauerte (filesystemcheck). Auserdem habe ich jetzt einen durchsatze von 35 mb/s wenn ich von einer Festplatte auf die andere kopiere wobei es vorher im schnitt nur 15 mb/s waren

Wenn ich ins aufzeichnungsmeü gehe und einen film auswähle bin ich auch sofort im Film wobei ich bei ext3 2 bis 3 sekunden warten musste bis was vom Film zu sehen war

mal schauen bis zum nächsten stromausfall wie es mit der zuverlässigkeit aussieht