can anybody clue me in on why fsck on my server [yes, of course as root]
seem to refuse to WRITE? we had a power out locally and i caught my UPS at
the last second. i powered off my server to save the battery, etc, and
a few minutes ago when i ran
# fsck -y /var
there were unresolved inconsis
On 6/15/2011 3:50 PM, Gary Kline wrote:
>
> is there any way of scripting fsck *every* time i reboot this box? i just
> want to make abs certain that the filesystems are clean. ---didn't fscking
> used to be easier?
Just override the defaults in /etc/rc.conf
fsck_y_enable="YES"
and if you are
On Jun 15, 2011, at 12:50 PM, Gary Kline wrote:
> can anybody clue me in on why fsck on my server [yes, of course as root]
> seem to refuse to WRITE?
Bad sectors on the hard drive are a somewhat common cause of this.
> we had a power out locally and i caught my UPS at
> the last second. i power
From: Chuck Swiger
To: Gary Kline
Cc: FreeBSD Mailing List
Sent: Wed, June 15, 2011 4:04:23 PM
Subject: Re: how do i fsck my server?
On Jun 15, 2011, at 12:50 PM, Gary Kline wrote:
> can anybody clue me in on why fsck on my server [yes, of course as r
_
> From: Chuck Swiger
> To: Gary Kline
> Cc: FreeBSD Mailing List
> Sent: Wed, June 15, 2011 4:04:23 PM
> Subject: Re: how do i fsck my server?
> You can set fsck_y_enable="YES" in /etc/rc.conf, but it shouldn't be
> necessary.
Facts:
8.2-RELEASE man fsck
-B ...
background fsck is limited to checking for only the most commonly
occurring file system abnormalities. Under certain circumstances,
some errors can escape background fsck. It is recommended that you
perform foreground fsck o
On Wed, Jun 15, 2011 at 01:04:23PM -0700, Chuck Swiger wrote:
> Date: Wed, 15 Jun 2011 13:04:23 -0700
> From: Chuck Swiger
> Subject: Re: how do i fsck my server?
> To: Gary Kline
> Cc: FreeBSD Mailing List
> X-Mailer: Apple Mail (2.1084)
>
> On Jun 15, 2011, at 12
On Fri, 17 Jun 2011 22:31:00 -0700, Gary Kline wrote:
> right. i booted into single-user and fsck still gave me the NO
> WRITE response; then i did a
>
> # shutdown now to get a # prompt in single-user and got the same
> NO WRITE. Only it did fix the errors. dunno... str
