Problem with fsck : continued

 
  Hi,
   
  Thanks for the support so far. FreeBSD is working
beautifully, both on the server as well as client
workstations. Except for fsck. I am writing from India,
where the electrical power scenario makes up for any
possible lack of frustration.
   
  My server faces unscheduled power cuts and consequent
improper shutdown 2-3 times every day. This is what I have
placed in my server's rc.conf :
   
  fsck_y_enable="YES"
  background_fsck="NO"
   
  Most of the time when the system comes up on its own
without first being subjected to single-user mode
operations, half the services (including squid, webmin,
vsftpd, svscan and - most significantly - getty for the
local console) fail to start up, although fsck does run
automatically in the foreground - with the y[es] argument
enabled - on all partitions listed in fstab on system
restart (i.e. restoration of electricity). The only solution
I know is to first go into single-user mode and run fsck on
the commandline for all partitions, after which the server
comes up quite nicely.
   
  This would be okay if I could leave a console attached to
the server, in which case I could run fsck interactively in
single-user mode and get the system up again. For daily
operations however, my organisation would much prefer to
have the server working without a console attached.
   
  So now the question is if I can get FreeBSD 6.0 to run
fsck automatically on restart in such a manner that all
services come up consistently. I am even willing to have
fsck run in the foreground upon EACH restart, irrespective
of whether the previous shutdown was proper or improper. How
do I do this ?
   
  Thanks for any help. Attached at the bottom is the
previous communication.
   
  Manish Jain
  goodredhatyahoo.com
   
   
   
   
   
  On Thursday 26 January 2006 19:39, manish jain wrote:
> I recently persuaded my organisation to shift our main
> server from Linux to FreeBSD 6.0. We are now facing a
> problem with fsck. After improper shutdown, we need
> fsck to run automatically and non-interactively in the
> foreground upon restart. Enabling background fsck lets
> the system come up but fails to properly start a few
> network services. 
  When you say you enabled it, do you simply mean you did
nothing at all, or did you add an extra fsck -B somewhere.
  Background fsck is enabled by default, and it runs 60
seconds after all other initialization. Partitions can only
be deferred for background checking if they support it, and
are in a mountable state.  These partitions are simply
skipped in the pre-mount fsck check. 
  All it does is recover lost space. It shouldn't have any
impact other than a general slowdown.
   

		
---------------------------------
 
 What are the most popular cars? Find out at Yahoo! Autos 
_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On Jan 31, 2006, at 12:25 PM, manish jain wrote:
>   So now the question is if I can get FreeBSD 6.0 to
run fsck  
> automatically on restart in such a manner that all
services come up  
> consistently. I am even willing to have fsck run in the
foreground  
> upon EACH restart, irrespective of whether the previous
shutdown  
> was proper or improper. How do I do this ?

To start with, you could set:

   background_fsck="NO"

...in /etc/rc.conf to force filesystem checking to happen
first.

However, you are not going to have a very happy computing
experience  
with any flavor of Unix if you keep shutting the system down
 
uncleanly several times a day because of power failures. 
Try to  
obtain a UPS with a serial or USB connection and use a port
like  
apcupsd to shut down cleanly...

-- 
-Chuck



_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

You are going around the wrong way to solve your problem.
Problem is not with FreeBSD or fsck, it's your electrical
power
supply.
Every body else in the world puts a UPS unit between their
pc and
the wall socket.
The UPS unit can give you 30 min run time from its battery
and then
signal its time to shutdown your system.
There is FreeBSD port system software that works with
different UPS
systems to do this. After system shutdown when your power
comes back
on your system will start up normally with no problems and
no risk
to the hardware. A complete hands off solution. Having the
power
stopped on a running pc will damage the hardware and destroy
your
system. You are just plan lucky that has not occured yet.

-----Original Message-----
From: owner-freebsd-questionsfreebsd.org
[mailto:owner-freebsd-questionsfreebsd.org]On Behalf Of
manish jain
Sent: Tuesday, January 31, 2006 12:26 PM
To: freebsd-questionsfreebsd.org
Subject: Problem with fsck : continued



  Hi,

  Thanks for the support so far. FreeBSD is working
beautifully,
both on the server as well as client workstations. Except
for fsck.
I am writing from India, where the electrical power scenario
makes
up for any possible lack of frustration.

  My server faces unscheduled power cuts and consequent
improper
shutdown 2-3 times every day. This is what I have placed in
my
server's rc.conf :

  fsck_y_enable="YES"
  background_fsck="NO"

  Most of the time when the system comes up on its own
without first
being subjected to single-user mode operations, half the
services
(including squid, webmin, vsftpd, svscan and - most
significantly -
getty for the local console) fail to start up, although fsck
does
run automatically in the foreground - with the y[es]
argument
enabled - on all partitions listed in fstab on system
restart (i.e.
restoration of electricity). The only solution I know is to
first go
into single-user mode and run fsck on the commandline for
all
partitions, after which the server comes up quite nicely.

  This would be okay if I could leave a console attached to
the
server, in which case I could run fsck interactively in
single-user
mode and get the system up again. For daily operations
however, my
organisation would much prefer to have the server working
without a
console attached.

  So now the question is if I can get FreeBSD 6.0 to run
fsck
automatically on restart in such a manner that all services
come up
consistently. I am even willing to have fsck run in the
foreground
upon EACH restart, irrespective of whether the previous
shutdown was
proper or improper. How do I do this ?

  Thanks for any help. Attached at the bottom is the
previous
communication.

  Manish Jain
  goodredhatyahoo.com





  On Thursday 26 January 2006 19:39, manish jain wrote:
> I recently persuaded my organisation to shift our main
> server from Linux to FreeBSD 6.0. We are now facing a
> problem with fsck. After improper shutdown, we need
> fsck to run automatically and non-interactively in the
> foreground upon restart. Enabling background fsck lets
> the system come up but fails to properly start a few
> network services.
  When you say you enabled it, do you simply mean you did
nothing at
all, or did you add an extra fsck -B somewhere.
  Background fsck is enabled by default, and it runs 60
seconds
after all other initialization. Partitions can only be
deferred for
background checking if they support it, and are in a
mountable
state.  These partitions are simply skipped in the pre-mount
fsck
check.
  All it does is recover lost space. It shouldn't have any
impact
other than a general slowdown.



---------------------------------

 What are the most popular cars? Find out at Yahoo! Autos
_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"