| View previous topic :: View next topic |
| Author |
Message |
dgaffuri
Advocate
Joined: 05 Jun 2005
Posts: 2078
Location: Italy
|
 Posted: Fri Oct 21, 2005 9:17 pm Post subject: ext3_orphan_cleanup errors, damaged files |
 |
|
During a periodic check of root fs in one of the last boots I've got those in /var/log/messages
| Code: | Oct 20 00:50:30 sotomayor EXT3-fs: INFO: recovery required on readonly filesystem.
Oct 20 00:50:30 sotomayor EXT3-fs: write access will be enabled during recovery.Oct 20 00:50:30 sotomayor EXT3-fs: hda5: orphan cleanup on readonly fs
Oct 20 00:50:30 sotomayor ext3_orphan_cleanup: deleting unreferenced inode 688421
Oct 20 00:50:30 sotomayor kjournald starting. Commit interval 5 seconds
Oct 20 00:50:30 sotomayor ext3_orphan_cleanup: deleting unreferenced inode 1663
.....
Oct 20 00:50:30 sotomayor ext3_orphan_cleanup: deleting unreferenced inode 164633
Oct 20 00:50:30 sotomayor ext3_orphan_cleanup: truncating inode 688450 to 2948 bytes
Oct 20 00:50:30 sotomayor EXT3-fs: hda5: 106 orphan inodes deleted
Oct 20 00:50:30 sotomayor EXT3-fs: hda5: 1 truncate cleaned up
Oct 20 00:50:30 sotomayor EXT3-fs: recovery complete.
Oct 20 00:50:30 sotomayor EXT3-fs: mounted filesystem with ordered data mode.
Oct 20 00:50:30 sotomayor VFS: Mounted root (ext3 filesystem) readonly. |
After that I discovered bad files in /usr/lib. So I renamed it to libold, run
| Code: | | cp -a /usr/libold /usr/lib |
and I've got errors on three files. I emerged again the involved packages. Now, after removing all other files from libold, I get
| Code: | # ls -l /usr/libold/
total 69
?rwsr-S--T 2270 1410926814 148783080 1600 Jan 1 1970 dbus-1.0
?--Sr-xr-- 2273 1608517857 148985908 375 Jan 1 1970 libaspell.so.15
prwsrws-wT 2267 567347419 148578731 1072521256 Jan 1 1970 libpspell.so |
and I get errors when I try to removee these files too
| Code: | # rm -rf /usr/libold/
rm: cannot remove `/usr/libold//libaspell.so.15': Operation not permitted
rm: cannot remove `/usr/libold//libpspell.so': Operation not permitted
rm: cannot remove `/usr/libold//dbus-1.0' |
Trying to update qt I've found other damaged files
| Code: | OSError: [Errno 17] File exists: '/usr/qt/3/tools/designer/templates'
sotomayor ~ # ls -l /usr/qt/3/tools/designer/templates
ls: /usr/qt/3/tools/designer/templates: Input/output error |
This is the second time in two months I've damaged files after a boot check, last time I had to re-install because emerge itself was damaged.
Anyone saw something similar?
_________________
Adopt an unanswered post
If you feel that your problem has been solved please edit the top post and add [solved] to the subject |
|
| Back to top |
|
 |
soulwarrior
Guru
Joined: 21 Oct 2002
Posts: 331
|
| Posted: Sun Jan 22, 2006 6:09 pm Post subject: |
|
|
Happened to me too: two times in two weeks 
And I thought that ext3 would be a very stable filesystem. Maybe I should be going back to reiserfs?, never had any similar problem on this filesystem.
Have not yet found a solution how to correct the filesystem, as e2fsck did not help with all the problems. |
|
| Back to top |
|
|
dgaffuri
Advocate
Joined: 05 Jun 2005
Posts: 2078
Location: Italy
|
| Posted: Sun Jan 22, 2006 6:37 pm Post subject: |
|
|
I've read that ipw2200 1.0.8 caused slab corruption when firmware errrors occurred (a bug in collecting error dump, see here). In effect I was running 1.0.8 when I had these problems and I had firmware errors (removed by disabling the hwcrypto option). I think it's fixed in portage version (for sure it is fixed in 2.6.15).
Even if it's not ipw2200 it could be some other module that you've added recently to your kernel. I reaaly don't think it's an ext3 problem, it is for sure the stablest file system on linux.
_________________
Adopt an unanswered post
If you feel that your problem has been solved please edit the top post and add [solved] to the subject |
|
| Back to top |
|
|
soulwarrior
Guru
Joined: 21 Oct 2002
Posts: 331
|
| Posted: Sun Jan 22, 2006 7:22 pm Post subject: |
|
|
Have now found a solution how to remove this sort of files. You have to use "debugfs". For example:
| Code: |
debugfs-w /dev/hda7
cd /directory
rm file
close
quit
|
@dgaffuri: For myself the rt2570 module poses a problem, does often hardlock. Will wait till the module does become more stable, as I only used this USB wireless device for kismet. |
|
| Back to top |
|
|
|
Kernel & Hardware
