Hello J. R. ,
> do dd if=/dev/zero of=$f bs=$((($RANDOM % 8) + 16))
I corrected $f to $i. I guess this was a typo...
Ok, I tried the procedure you described running the check in the
foreground and the stress test in the background.
The result is a bit puzzling. I try my best to describe it right:
The general behaviour is:
When I start the stresstest script ( I positioned it in a directory
on /mnt/ro_root/test/ ) I can see a few processes with "ps" that all
use the process name of the script. I guess these are the different
functions.
At the mentioned directory I can see that RANDOM files and directories
are randomly created,removed,... according to the script. This happens
ALSO when the check script is running the check ( -> not in sleep
time ). This distracts me a bit.
After I kill all the stress script processes, random files are still at
the mentioned directory and the following fs-checks are all SANE.
However,
At the time the stress scripts are running the fsck script runs into
errors. I guess this is just because it cannot mount it readonly - see
the first line, and so runs into a lot of inconsistency :
(Some BONEHEAD checking a live filesystem :D )
- - - - - - - -
mount: /mnt/ro_root is busy
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
Warning! /dev/sda1 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem
check. Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Invalid inode number for '.' in directory inode 160989.
Fix? no
Entry '.' in ??? (160989) has deleted/unused inode 161033. Clear? no
Entry '..' in ??? (160989) has deleted/unused inode 161032. Clear? no
Invalid inode number for '.' in directory inode 161006.
Fix? no
Entry '.' in /test/16/15 (161006) has deleted/unused inode 160968.
Clear? no
Entry '.' in /test/16/15 (161006) has an incorrect filetype (was 2,
should be 1). Fix? no
Invalid inode number for '.' in directory inode 161007.
Fix? no
Entry '.' in /test/9/15/23/4 (161007) has deleted/unused inode 160969.
Clear? no
Entry '.' in /test/9/15/23/4 (161007) has an incorrect filetype (was 2,
should be 7). Fix? no
Entry '..' in /test/9/15/23/4 (161007) has deleted/unused inode
160968. Clear? no
Entry '..' in /test/9/15/23/4 (161007) has an incorrect filetype (was
2, should be 1). Fix? no
Invalid inode number for '.' in directory inode 160998.
Fix? no
Invalid inode number for '.' in directory inode 160986.
Fix? no
...
WARNING: PROGRAMMING BUG IN E2FSCK!
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[160986] is 2, inode.i_links_count is 3. They should be
the same! Inode 160986 ref count is 3, should be 3. Fix? no
Unattached inode 160989
Connect to /lost+found? no
Unattached inode 160990
Connect to /lost+found? no
Inode 160992 ref count is 5, should be 2. Fix? no
WARNING: PROGRAMMING BUG IN E2FSCK!
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[160993] is 2, inode.i_links_count is 3. They should be
the same! Inode 160993 ref count is 3, should be 1. Fix? no
WARNING: PROGRAMMING BUG IN E2FSCK!
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[160996] is 2, inode.i_links_count is 1. They should be
the same! Inode 160996 ref count is 1, should be 1. Fix? no
Unattached inode 160998
Connect to /lost+found? no
Unattached inode 161001
Connect to /lost+found? no
WARNING: PROGRAMMING BUG IN E2FSCK!
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[161005] is 1, inode.i_links_count is 2. They should be
the same! Inode 161005 ref count is 2, should be 2. Fix? no
WARNING: PROGRAMMING BUG IN E2FSCK!
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[161006] is 6, inode.i_links_count is 2. They should be
the same! Inode 161006 ref count is 2, should be 1. Fix? no
Unattached inode 161007
Connect to /lost+found? no
Unattached inode 161008
Connect to /lost+found? no
Unattached inode 161011
Connect to /lost+found? no
Unattached inode 161013
Connect to /lost+found? no
Unattached inode 161014
Connect to /lost+found? no
Unattached inode 161016
Connect to /lost+found? no
Inode 161018 ref count is 2, should be 1. Fix? no
Unattached inode 161022
Connect to /lost+found? no
Unattached inode 161024
Connect to /lost+found? no
WARNING: PROGRAMMING BUG IN E2FSCK!
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[161063] is 3, inode.i_links_count is 0. They should be
the same! Inode 161063 ref count is 0, should be 1. Fix? no
Pass 5: Checking group summary information
Block bitmap differences: +(655865--655867) -655884 +(657412--657413)
-(657414--657417) -659461 +661507 -(661516--661518) -(661525--661526)
-(661533--661540) -(663555--663556) +665600 -(665607--665608) -665610
-(667650--667652) +667671 +(669697--669698) -(669703--669707) +669708
-(669712--669714) -(671752--671753) +673793 -673796 +(673798--673799)
+673802 +673810 +675843 -(675850--675853) +(679936--679937) -679945
-(679952--679953) -681997 -(682008--682010) +684033 +684040
+(686080--686081) -686083 -(686085--686091) Fix? no
Free blocks count wrong for group #20 (32227, counted=32202).
Fix? no
Free blocks count wrong (976669, counted=976610).
Fix? no
Inode bitmap differences: -(160968--160969) -160971 +160975 -160976
-160978 -160982 -160985 -(160987--160988) -(160994--160995)
-(160999--161000) -(161003--161004) -(161009--161010) -161012 -161015
-(161020--161021) -161023 -(161025--161026) -(161030--161033) -161035
-161037 -161040 +161063 Fix? no
Free inodes count wrong for group #20 (8005, counted=7978).
Fix? no
Directories count wrong for group #20 (21, counted=18).
Fix? no
Free inodes count wrong (242765, counted=242697).
Fix? no
nibbler: ********** WARNING: Filesystem still has errors **********
- - - - - - - -
But as I already stated, besides this dumb error, the check completes
without errors, after the stress-test has ended. And there has
definitely been a lot of traffic in the test directory during the
procedure.
So the test was successful - can you extract something from it?
Have a nice day,
Marcus
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
