es ist wieder so weit:
Nach dem die Box 4 Tage lief und diverse Aufnahmen erfolgreich hinter sich gebracht hatte habe ich wegen chronischem Speicherverlust die Box neu gestartet:
~ > dmesg|grep XFS
<6>SGI XFS with no debug enabled
<5>XFS mounting filesystem ide0(3,2)
<5>Starting XFS recovery on filesystem: ide0(3,2) (dev: ide0(3,2))
<1>Filesystem "ide0(3,2)": XFS internal error xlog_recover_do_inode_trans(1) at line 2366 of file xfs_log_recover.c. Caller 0xc39c2738
<4>XFS: log mount/recovery failed: error 990
<4>XFS: log mount failed
~ > /bin/mount -t xfs /dev/discs/disc0/part2 /hdd
mount: Mounting /dev/discs/disc0/part2 on /hdd failed: Invalid argument
~ > xfs_repair /dev/discs/disc0/part2
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed. Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair. If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
So sieht der Versuch aus:
Code: Alles auswählen
~ > xfs_repair -L /dev/discs/disc0/part2
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
ALERT: The filesystem has valuable metadata changes in a log which is being
destroyed because the -L option was used.
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
bad magic number 0x8b34 on inode 128
bad version number 0x65 on inode 128
bad inode format in inode 128
bad magic number 0xbb0 on inode 129
bad version number 0xffffffe7 on inode 129
bad (negative) size -6694777401864313085 on inode 129
bad magic number 0x206e on inode 130
bad version number 0xffffffc9 on inode 130
bad inode format in inode 130
bad magic number 0x7b04 on inode 131
bad version number 0xffffff80 on inode 131
bad inode format in inode 131
bad magic number 0x74ea on inode 132
bad version number 0x0 on inode 132
bad inode format in inode 132
bad magic number 0x1f63 on inode 133
bad version number 0xffffffdc on inode 133
bad inode format in inode 133
bad magic number 0xa76b on inode 134
bad version number 0x58 on inode 134
bad inode format in inode 134
bad magic number 0x4700 on inode 135
bad version number 0x5c on inode 135
bad (negative) size -4748991457231552570 on inode 135
bad magic number 0x1b25 on inode 136
bad version number 0x49 on inode 136
bad (negative) size -6755935621999281186 on inode 136
bad magic number 0xc787 on inode 137
bad version number 0x33 on inode 137
bad (negative) size -8940518901823028121 on inode 137
bad magic number 0xaaa0 on inode 138
bad (negative) size -1082815631519877350 on inode 138
bad magic number 0x3595 on inode 139
bad version number 0x43 on inode 139
bad inode format in inode 139
bad magic number 0x6d29 on inode 140
bad version number 0x7b on inode 140
bad inode format in inode 140
bad magic number 0xf48 on inode 141
bad version number 0x67 on inode 141
bad (negative) size -4125297258653347081 on inode 141
bad magic number 0xf013 on inode 142
bad version number 0x60 on inode 142
bad inode format in inode 142
bad magic number 0x7205 on inode 143
bad version number 0x37 on inode 143
bad (negative) size -455838627872106333 on inode 143
bad magic number 0x8b34 on inode 128, resetting magic number
bad version number 0x65 on inode 128, resetting version number
bad inode format in inode 128
cleared root inode 128
bad magic number 0xbb0 on inode 129, resetting magic number
bad version number 0xffffffe7 on inode 129, resetting version number
bad (negative) size -6694777401864313085 on inode 129
cleared realtime bitmap inode 129
bad magic number 0x206e on inode 130, resetting magic number
bad version number 0xffffffc9 on inode 130, resetting version number
bad inode format in inode 130
cleared realtime summary inode 130
bad magic number 0x7b04 on inode 131, resetting magic number
bad version number 0xffffff80 on inode 131, resetting version number
bad inode format in inode 131
cleared inode 131
bad magic number 0x74ea on inode 132, resetting magic number
bad version number 0x0 on inode 132, resetting version number
bad inode format in inode 132
cleared inode 132
bad magic number 0x1f63 on inode 133, resetting magic number
bad version number 0xffffffdc on inode 133, resetting version number
bad inode format in inode 133
cleared inode 133
bad magic number 0xa76b on inode 134, resetting magic number
bad version number 0x58 on inode 134, resetting version number
bad inode format in inode 134
cleared inode 134
bad magic number 0x4700 on inode 135, resetting magic number
bad version number 0x5c on inode 135, resetting version number
bad (negative) size -4748991457231552570 on inode 135
cleared inode 135
bad magic number 0x1b25 on inode 136, resetting magic number
bad version number 0x49 on inode 136, resetting version number
bad (negative) size -6755935621999281186 on inode 136
cleared inode 136
bad magic number 0xc787 on inode 137, resetting magic number
bad version number 0x33 on inode 137, resetting version number
bad (negative) size -8940518901823028121 on inode 137
cleared inode 137
bad magic number 0xaaa0 on inode 138, resetting magic number
bad (negative) size -1082815631519877350 on inode 138
cleared inode 138
bad magic number 0x3595 on inode 139, resetting magic number
bad version number 0x43 on inode 139, resetting version number
bad inode format in inode 139
cleared inode 139
bad magic number 0x6d29 on inode 140, resetting magic number
bad version number 0x7b on inode 140, resetting version number
bad inode format in inode 140
cleared inode 140
bad magic number 0xf48 on inode 141, resetting magic number
bad version number 0x67 on inode 141, resetting version number
bad (negative) size -4125297258653347081 on inode 141
cleared inode 141
bad magic number 0xf013 on inode 142, resetting magic number
bad version number 0x60 on inode 142, resetting version number
bad inode format in inode 142
cleared inode 142
bad magic number 0x7205 on inode 143, resetting magic number
bad version number 0x37 on inode 143, resetting version number
bad (negative) size -455838627872106333 on inode 143
cleared inode 143
- agno = 1
data fork in ino 134222212 claims free block 9860865
data fork in ino 134222212 claims free block 9860866
data fork in ino 134222212 claims free block 9860867
data fork in ino 134222212 claims free block 9860868
data fork in ino 134222212 claims free block 9860869
data fork in ino 134222212 claims free block 9860870
data fork in ino 134222212 claims free block 9860871
data fork in ino 134222212 claims free block 9860872
data fork in ino 134222212 claims free block 9860873
data fork in ino 134222212 claims free block 9860874
data fork in ino 134222212 claims free block 9860875
data fork in ino 134222212 claims free block 9860876
data fork in ino 134222212 claims free block 9860877
data fork in ino 134222212 claims free block 9860878
data fork in ino 134222212 claims free block 9860879
data fork in ino 134222212 claims free block 9860880
data fork in ino 134222213 claims free block 8389391
data fork in ino 134222213 claims free block 8389392
data fork in ino 134222214 claims free block 8389348
data fork in ino 134222214 claims free block 8389349
data fork in ino 134222214 claims free block 8389350
data fork in ino 134222214 claims free block 8389351
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
root inode lost
- clear lost+found (if it exists) ...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
entry ".." at block 0 offset 32 in directory inode 134217856 references free inode 128
clearing inode number in entry at offset 32...
no .. entry for directory 134217856
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
Phase 5 - rebuild AG headers and trees...
- reset superblock...
Phase 6 - check inode connectivity...
reinitializing root directory
reinitializing realtime bitmap inode
reinitializing realtime summary inode
- resetting contents of realtime bitmap and summary inodes
- ensuring existence of lost+found directory
- traversing filesystem starting at / ...
rebuilding directory inode 134217856
- traversal finished ...
- traversing all unattached subtrees ...
- traversals finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 128, moving to lost+found
disconnected inode 144, moving to lost+found
disconnected dir inode 145, moving to lost+found
disconnected dir inode 148, moving to lost+found
disconnected inode 151, moving to lost+found
disconnected inode 152, moving to lost+found
disconnected inode 153, moving to lost+found
disconnected inode 154, moving to lost+found
disconnected dir inode 134217856, moving to lost+found
disconnected dir inode 134217857, moving to lost+found
disconnected dir inode 134222223, moving to lost+found
disconnected dir inode 134222232, moving to lost+found
disconnected dir inode 134228044, moving to lost+found
disconnected dir inode 268435584, moving to lost+found
disconnected dir inode 268435587, moving to lost+found
disconnected dir inode 402653312, moving to lost+found
Phase 7 - verify and correct link counts...
doneDas ganze scheint u.U. in Zusammenhang damit zu stehen, dass EPG Speichern nicht fertig wird oder der "sync" nicht fertig wird... ???
Jedenfalls ist das Filesystem zum Zeitpunkt des Resets nicht beruhigt.
Wie kann man das verhindern?