chkfsys and rc.sysinit?

A recent post mentioned that chkfsys aborts the execution of rc.sysinit (I know this is
true when it requires keyboard input, I haven’t tested other conditions). This must be why it
is commented out by default. Has anyone come up
with an easy workaround for this? I want my machines to check disks automatically
when they boot. I’m having a few things
turn up consistently during a chkfsys (lpd lock files, and some helpviewer-related files),
though I dont know why.

Also, it seems that the ‘clean’ flag is not being set on the filesystem when there is a clean
shutdown. Is this true?

Thanks.


Art Hays
National Institutes of Health
avhays@nih.gov

“Art Hays” <avhays@nih.gov> wrote in message
news:a7bo11$qh3$1@inn.qnx.com

A recent post mentioned that chkfsys aborts the execution of rc.sysinit (I
know this is
true when it requires keyboard input, I haven’t tested other conditions).
This must be why it
is commented out by default. Has anyone come up
with an easy workaround for this? I want my machines to check disks
automatically
when they boot. I’m having a few things
turn up consistently during a chkfsys (lpd lock files, and some
helpviewer-related files),
though I dont know why.

Add chkfsys -pQr / (check option, it’s from memory) to /etc/rc.d/rc.local

Also, it seems that the ‘clean’ flag is not being set on the filesystem
when there is a clean
shutdown. Is this true?

If some program that are not responding to SIGPWR, to close all open file,
that’s true.

Thanks.


Art Hays
National Institutes of Health
avhays@nih.gov

I have found out that it is generally a bad idea to run chkfsys from any of
the start up scripts. I think the reason is that you operating on a file
system which you also are reparing/changing.

The only solid solution is to create a custom boot image which runs chkfsys
before any start up scripts are executed. It would be really nice if QSSL
would add a chkfsys option to diskboot, so that you don’t need to manully
mount the file system that you want to check.

BTW: I hear rumors that there is going to be an option in 6.2 which will
give to the ability specify the behvior of the file system when a file
wasn’t close properly. Right not it very critical with files there weren’t
closed and will give a file error if you try to open such a file.


Jens


“Mario Charest” <goto@nothingness.com> wrote in message
news:a7cil4$fh7$1@inn.qnx.com

“Art Hays” <> avhays@nih.gov> > wrote in message
news:a7bo11$qh3$> 1@inn.qnx.com> …
A recent post mentioned that chkfsys aborts the execution of rc.sysinit
(I
know this is
true when it requires keyboard input, I haven’t tested other
conditions).
This must be why it
is commented out by default. Has anyone come up
with an easy workaround for this? I want my machines to check disks
automatically
when they boot. I’m having a few things
turn up consistently during a chkfsys (lpd lock files, and some
helpviewer-related files),
though I dont know why.


Add chkfsys -pQr / (check option, it’s from memory) to /etc/rc.d/rc.local

Also, it seems that the ‘clean’ flag is not being set on the filesystem
when there is a clean
shutdown. Is this true?

If some program that are not responding to SIGPWR, to close all open file,
that’s true.


Thanks.


Art Hays
National Institutes of Health
avhays@nih.gov
\

Jens H Jorgensen <jhj@remove-nospam-videk.com> wrote:

I have found out that it is generally a bad idea to run chkfsys from any of
the start up scripts. I think the reason is that you operating on a file
system which you also are reparing/changing.

The only solid solution is to create a custom boot image which runs chkfsys
before any start up scripts are executed. It would be really nice if QSSL
would add a chkfsys option to diskboot, so that you don’t need to manully
mount the file system that you want to check.

BTW: I hear rumors that there is going to be an option in 6.2 which will
give to the ability specify the behvior of the file system when a file
wasn’t close properly. Right not it very critical with files there weren’t
closed and will give a file error if you try to open such a file.

I generally avoid the problem by running chkfsys with output redirected to
a second filesystem (granted, you need two filesystems in order to do this :slight_smile:)
The second phase of chkfsys checks the second filesystem, and then the log
files are gathered and emailed to root.

Cheers,
-RK


Jens



“Mario Charest” <> goto@nothingness.com> > wrote in message
news:a7cil4$fh7$> 1@inn.qnx.com> …

“Art Hays” <> avhays@nih.gov> > wrote in message
news:a7bo11$qh3$> 1@inn.qnx.com> …
A recent post mentioned that chkfsys aborts the execution of rc.sysinit
(I
know this is
true when it requires keyboard input, I haven’t tested other
conditions).
This must be why it
is commented out by default. Has anyone come up
with an easy workaround for this? I want my machines to check disks
automatically
when they boot. I’m having a few things
turn up consistently during a chkfsys (lpd lock files, and some
helpviewer-related files),
though I dont know why.


Add chkfsys -pQr / (check option, it’s from memory) to /etc/rc.d/rc.local

Also, it seems that the ‘clean’ flag is not being set on the filesystem
when there is a clean
shutdown. Is this true?

If some program that are not responding to SIGPWR, to close all open file,
that’s true.


Thanks.


Art Hays
National Institutes of Health
avhays@nih.gov

\


Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at www.parse.com.
Email my initials at parse dot com.