Hello,
last fsck says my /tmp and my /home files system has errors, here is the
log from fsck using the read-only option:
How to recover from this savely?
How to avoid this in future?
i am using kernel 2.4.18 with the acl-patches from acl.bestbits.at and the
patches for the fileutils and e2fsprogs.
If you need more informations please mail.
-----------------------------------------------------------------------------
kernel says:
Jul 24 11:34:13 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode:
error 28
-----------------------------------------------------------------------------
fsck says:
e2fsck 1.25 (20-Sep-2001)
Warning! /dev/sda8 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 13 was part of the orphaned inode list. IGNORED.
Inode 14 was part of the orphaned inode list. IGNORED.
Inode 32807 was part of the orphaned inode list. IGNORED.
Inode 49250 was part of the orphaned inode list. IGNORED.
Inode 180226 was part of the orphaned inode list. IGNORED.
Inode 180228 was part of the orphaned inode list. IGNORED.
Inode 180239 was part of the orphaned inode list. IGNORED.
Inode 180243 was part of the orphaned inode list. IGNORED.
Inode 180256 was part of the orphaned inode list. IGNORED.
Inode 180264 was part of the orphaned inode list. IGNORED.
Inode 180275 was part of the orphaned inode list. IGNORED.
Deleted inode 180300 has zero dtime. Fix? no
Inode 196612 was part of the orphaned inode list. IGNORED.
Inode 196630 was part of the orphaned inode list. IGNORED.
Inode 196688 was part of the orphaned inode list. IGNORED.
Inode 196708 was part of the orphaned inode list. IGNORED.
Inode 213055 was part of the orphaned inode list. IGNORED.
Inode 245765 was part of the orphaned inode list. IGNORED.
Inode 245886 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -360965 -360969 -393735 -398122 -492224 -493366
-493367 -493368 -493369 -493370 -493371 -493372 -493373 -493374 -493375 -493376
-493377 -493378 -493379 -493380 -493381 -493382 -493383 -493384 -493385 -493386
-493387 -493388 -493389 -493390 -493391 -493392 -493393 -493394 -493395 -493396
-493397 -493398 -493399 -493400 -493401 -493402 -493403 -493404 -493405 -493406
-493407 -493408 -493409 -493410 -493411 -493412 -493413 -493414 -493415 -493416
-493417 -493418 -493420 -493421 -493422 -493423 -493424 -493425 -493426 -493427
-493428 -493429 -493430 -493431 -493432 -493433 -493434 -493435 -493436 -493437
-493438 -493439 -493440 -493441 -493442 -497145 -497146 -497147 -497148 -497149
-497150 -497151 -497152 -497153 -497154 -497155 -497156 -497157 -497158 -497159
-497160 -497161 -497162 -497163 -497164 -497165 -497166 -497167 -497168 -497169
-497170 -497172 -497184 -497185 -497186 -497187 -497188 -497189 -497190 -497191
-497192 -497193 -497194 -497195 -4!
97196 -497197 -497198 -497199 -497200 -497201 -497202
Fix? no
Inode bitmap differences: -13 -14 -32807 -49250 -180226 -180228 -180239 -180243
-180256 -180264 -180275 -180300 -196612 -196630 -196688 -196708 -213055 -245765
-245886
Fix? no
Directories count wrong for group #11 (17, counted=15).
Fix? no
Directories count wrong for group #12 (12, counted=10).
Fix? no
Directories count wrong for group #15 (11, counted=10).
Fix? no
/tmp: ********** WARNING: Filesystem still has errors **********
1506 inodes used (0%)
234 non-contiguous inodes (15.5%)
# of inodes with ind/dind/tind blocks: 139/17/0
119586 blocks used (22%)
0 bad blocks
0 large files
1119 regular files
316 directories
0 character device files
0 block device files
0 fifos
0 links
4 symbolic links (4 fast symbolic links)
39 sockets
--------
1478 files
--
Jens-Uwe Katolla katolla@otris.de
otris software AG http://www.otris.de
Landgrafenstr. 153 Fon +49 (0)231 95 80 69 -0
D-44139 Dortmund Fax +49 (0)231 95 80 69 -44
On Jul 24, 2002 11:37 +0200, Jens-Uwe Katolla wrote:> last fsck says my /tmp and my /home files system has errors, here is the > log from fsck using the read-only option: > > How to recover from this savely?A normal fsck will clean this up easily, as will simply mounting the filesystem.> How to avoid this in future?You cannot - orphan files are files that are opened by a program but deleted. Many programs (e.g. pcmcia cardctl, X11, gnome, etc) use such temporary files.> kernel says: > > Jul 24 11:34:13 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28This is a bug which has been fixed. It was marking the filesystem in error when it was full. Cheers, Andreas -- Andreas Dilger http://www-mddsp.enel.ucalgary.ca/People/adilger/ http://sourceforge.net/projects/ext2resize/
On Wed, Jul 24, 2002 at 11:37:03AM +0200, Jens-Uwe Katolla wrote:> Hello, > > last fsck says my /tmp and my /home files system has errors, here is the > log from fsck using the read-only option: > > How to recover from this savely? > How to avoid this in future?1. Upgrade to the latest e2fsprogs. There's been a number of improvements in e2fsprogs especially with respect to journal handling since 1.25. 2. Errors when running e2fsck on a mounted filesystem don't necessarily mean anything; neither do errors if you havne't run the journal yet. So don't try to run it on a mounted filesystem, and don't try to do a read-only check if filesystem wasn't mounted uncleanly. - Ted