Does this fsck look OK?

Posted by: SE_Sport_Driver

Does this fsck look OK? - 09/05/2002 16:44

empeg:/empeg/bin#
empeg:/empeg/bin# ro
empeg:/empeg/bin# rom
empeg:/empeg/bin# umount /dev/hda4
empeg:/empeg/bin# umount /dev/hdc4
empeg:/empeg/bin# swapon /swapfile
Adding Swap: 16596k swap-space (priority -1)
empeg:/empeg/bin# fsck -fay /
Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda5 is mounted.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hda5: 1510/4096 files (0.5% non-contiguous), 9427/16384 blocks
empeg:/empeg/bin# fsck -fay /dev/hda4
Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda4 is mounted.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'database' in /var (257) has deleted/unused inode 16577. Clear? yes

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: +418615 +3170745 +4719248 +4915378 +6587028 +10112072
+11683471 +11729919 -15213190 +15213192 +15213193 +15213194 +15213195 +15213196
+15213197 +15213198 +15213199 +15213200 +15213201 +15213202 +15213203 +15213204
+15213461 -15460923 -15460924 -15460925 -15460926 -15460927 -15460928 -15460929
-15460930 -15460931 -15460932 -15460933 -15460934 -15460935 -15460936 -15460937
-15460938 -15460939 -15460940 -15460941 -15460942 -15460943 -15460944 -15460945
-15460946 -15460947 -15460948 -15460949 -15460950 -15460951 -15460952 -15460953
-15460954 -15460955 -15460956 -15460957 -15460958 -15460959 -15460960 -15460961
-15460962 -15460963 -15460964 -15460965 -15460966 -15460967 -15460968 -15460969
-15460970 -15460971 -15460972 -15460973 -15460974 -15460975 -15460976 -15460977
-15460978 -15460979 -15460980 -15460981 -15460982 -15460983 -15460984 -15460985
-15460986 -15460987 -15460988 -15460989 -15460990 -15460991 -15460992 -15460993
-15460994 -15460995 -15460996 -15460997 -15460998 -15460999 -15461000 -15461001
-15461002 -15461003 -15461004 -15461005 -15461006 -15461007 -15461008 -15461009
-15461010 -15461011 -15461012 -15461013 -15461014 -15461015 -15461016 -15461017
-15461018 -15461019 -15461020 -15461021 -15461022 -15461023 -15461024 -15461025
-15461026 -15461027 -15461028 -15461029 -15461030 -15461031 -15461032 -15461033
-15461034 -15461035 -15461036 -15461037 -15461038 -15461039 -15461040 -15461041
-15461042 -15461043 -15461044 -15461045 -15461046 -15461047 -15461048 -15461049
-15461050 -15461051 -15461052 -15461053 -15461054 -15461055 -15461056 -15461057
-15461058 -15461059 -15461060 -15461061 -15461062 -15461063 -15461064 -15461065
-15461066 -15461067 -15461068 -15461069 -15461070 -15461071 +17735195 +17877001
+18425030 +19591427 +20630505 +22899627 +25514588
Fix? yes

Free blocks count wrong for group #51 (1, counted=0).
Fix? yes

Free blocks count wrong for group #387 (1, counted=0).
Fix? yes

Free blocks count wrong for group #576 (1, counted=0).
Fix? yes

Free blocks count wrong for group #600 (1, counted=0).
Fix? yes

Free blocks count wrong for group #804 (1, counted=0).
Fix? yes

Free blocks count wrong for group #1234 (1, counted=0).
Fix? yes

Free blocks count wrong for group #1426 (1, counted=0).
Fix? yes

Free blocks count wrong for group #1431 (1, counted=0).
Fix? yes

Free blocks count wrong for group #1857 (14, counted=1).
Fix? yes

Free blocks count wrong for group #1887 (0, counted=149).
Fix? yes

Free blocks count wrong for group #2164 (1, counted=0).
Fix? yes

Free blocks count wrong for group #2182 (1, counted=0).
Fix? yes

Free blocks count wrong for group #2249 (1, counted=0).
Fix? yes

Free blocks count wrong for group #2391 (1, counted=0).
Fix? yes

Free blocks count wrong for group #2518 (1, counted=0).
Fix? yes

Free blocks count wrong for group #2795 (1, counted=0).
Fix? yes

Free blocks count wrong for group #3114 (1, counted=0).
Fix? yes

Free blocks count wrong (116472, counted=116593).
Fix? yes


/dev/hda4: ***** FILE SYSTEM WAS MODIFIED *****
/dev/hda4: 11010/228288 files (26.9% non-contiguous), 29102807/29219400 blocks
empeg:/empeg/bin#
Posted by: SE_Sport_Driver

Re: Does this fsck look OK? - 09/05/2002 16:56

I guess this is similar to CurlyKicker's problem... I'm just wondering where the heck it came from? I've been unable to sync all day. Everytime I tried, it would force a media check. At 60GB, that took all day to do 8 times or so. But it would also crash right after most times. Since it hung during a sync, I figured I'd check to see if I needed a fsck... I'm going back to HiJack 254 and see if that helps? Weird. (fsck is finishing right now)
Posted by: pgrzelak

Re: Does this fsck look OK? - 10/05/2002 04:16

Greetings!

If you hung during a sync, you would need to fsck, and that is where you would get that kind of error set. I would strongly recommend upgrading to the latest hijack. There is a fix around release 263 that enables frame pointers. This fixes sync problems with large databases. Load 263, sync (it might do an fsck), but after that, you should be fine.
Posted by: SE_Sport_Driver

Re: Does this fsck look OK? - 10/05/2002 07:38

Thanks Paul. I loaded 266 and that's when I started having problems, but I'm thinking it was coincidence. (can't spell today, we need a spell check button!)

I'll give 263 or later a try.
Posted by: SE_Sport_Driver

Re: Does this fsck look OK? - 10/05/2002 12:47

Paul or anyone.. can anyone think of how one of these later HiJacks could cause problems? Everything was working fine with v254. Now I installed 263, and it started timing out 1/2 way through the uploading of the tracks. Now it needs another fsck... Could there be something corrupt in my empeg's filesystem that is only noticed when running a later HiJack?