Are you running chkfsys in the start or the end of rc.local?
If you do at the last thing then try to move it to the beginning.
What I think is happing is that the shell is executing the script by reading
line by line from the script with a file pointer point to a certain area of
the file system. If then chkfsys moves that section of the file system the
file pointer is going to point to the wrong place on the file system and
your script execution is going to try to execute what ever the file pointer
is pointing at.
The problem I was seeing in my rc.local was that the script execution would
abort/error out right after chkfsys was executed. So for instance:
#stuff before chkfsys
#stuff after chkfsys
rc.local would never make it to “stuff after chkfsys”
“Thomas Emberson” <email@example.com> wrote in message
Jens H Jorgensen <> firstname.lastname@example.org> > wrote:
I glad to hear that it is currently working for you, but I used
do the same thing and I would often end up with problems script
I think the difference between running chkfsys from the shell
which is on the file system that you are cleaning up, and
running chkfsys from a script - is that the system during
script execution has a open file to the script, and if that
section of the file system where the script is located gets
moved around - I think your script execution fails. At least
that is my theory on why you sometimes end up with problems
when executing chkfsys in a script - perhaps someone from QSSL
can correct me if I am wrong.
Honestly, I can’t see where having a file open for read only
should cause a problem with the chkfsys.
Just tried it on my 6.1a box, had a file open for write and
chkfsys did not complain. And none of my open files had any
problems, at least 2 elvis processes running with no effect. I
am sure if I increased the size then I would get a bitmap error.
chkfsys, will just scan the raw partition for errors.