Just performed an installation. Ran “tune2fs -l” on the file system that mounts at root (/), which is ext3 and it reported a “First orphan inode.” The inode number changed after a few minutes with no other user-space activity.
Booted from DVD and ran “e2fsck -f -C0” on the file system, and it reported no errors.
Booted from the hard drive, and a new “First orphan inode” was reported (which also changed after a few minutes). There were no files in lost+found. Ran “e2fsck -f -C0 -n” on the file system and it reported:
e2fsck 1.41.1 (01-Sep-2008)
Warning! /dev/mapper/pdc_dbddcighd_part7 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 1847532 has zero dtime. Fix? 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: -(7381179–7381232)
Free blocks count wrong for group #223 (23960, counted=23959).
Free blocks count wrong (28945097, counted=28945096).
Inode bitmap differences: -1847532
/dev/mapper/pdc_dbddcighd_part7: ********** WARNING: Filesystem still has errors **********
/dev/mapper/pdc_dbddcighd_part7: 139304/7617024 files (0.3% non-contiguous), 1463607/30408704 blocks
Clean restarts (not shutdowns) each time. When I installed the OS (from OpenSUSE-11.1-DVD-x86_64.iso), I edited the default partitioning recommendation by deleting the /home partition (it would not let me reduce the size), enlarging the / partition to grab most of the space freed by deleting the /home partition, and recreating the /home partition using all the remaining space, but otherwise exactly the same parameters it had recommended. It wanted to make the /home partition take up approximately 85% of the hard drive, and make the / partition only around 20 GiB. Since most files I plan to add won’t be in the /home directory (/usr/local/bin/ instead), I figured I needed to do this to have the free space.
Maybe I screwed it up when I partitioned it this way, but I only mention it because I have no idea, not because I have any reason to suspect this was the cause of the errors.
What’s going on with the file system checking out okay when unmounted but not when mounted?
Is there any way to safely fix errors that appear only when the system is mounted?
Would the “First orphan inode” changing when the system is idle be attributable to background processes not successfully deleting files (I was in runlevel 5)?
Anything wrong with my logic or actions regarding the partitioning setup?