> Exactly, which is why I thought that just bypassing all those
> interventions with -y was 'brushing under the carpet'. No?
Ah I see. Yes. Given that all bets are off, it's hoping for the best ;)
> I realise it would normally be excessively cautious to go for
> synchronous mounting, but what abo
Peter Schuller wrote:
My understanding from the reading I have done is that in a situation like
this where power outages are a danger (and presuably having the UPS signal
the server to shut down gracefully is not practical), you need to make the
file system as robust as possible in the first plac
> My understanding from the reading I have done is that in a situation like
> this where power outages are a danger (and presuably having the UPS signal
> the server to shut down gracefully is not practical), you need to make the
> file system as robust as possible in the first place, rather than r
> If you are running without write caching turned on (which is the default),
That should be, "if you are running WITH write caching turned on".
--
/ Peter Schuller
PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>'
Key retrieval: Send an E-Mail to [EMAIL PROTECTED]
E-Mail: [EMAIL PR
Randy Ramsdell wrote:
> We started using FreeBSD for some network monitoring, but have found
> that a hard reboot forces us to answer filesytem questions on boot. Is
> there a way to mount each filesystem without this? Or how can we use
> FreeBSD in a remote location without needing to intervene in
Randy Ramsdell wrote:
Vince wrote:
Randy Ramsdell wrote:
We started using FreeBSD for some network monitoring, but have found
that a hard reboot forces us to answer filesytem questions on boot. Is
there a way to mount each filesystem without this? Or how can we use
FreeBSD in a remote locatio
Randy Ramsdell wrote:
Robert Huff wrote:
Randy Ramsdell writes:
> What is the value of background_fsck in /etc/rc.conf ?
>This isn't set. Was is supposed to be? So far, I have only
installed applications we need. And everything seem fine except
the reboot issue.
I'm going t
On Thu, December 6, 2007 4:42 pm, Randy Ramsdell wrote:
> Vince wrote:
>
>> Randy Ramsdell wrote:
>>
>>
>>> We started using FreeBSD for some network monitoring, but have found
>>> that a hard reboot forces us to answer filesytem questions on boot. Is
>>> there a way to mount each filesystem witho
On Thu, 06 Dec 2007 11:42:22 -0500
Randy Ramsdell <[EMAIL PROTECTED]> wrote:
> Vince wrote:
> > What is the value of background_fsck in /etc/rc.conf ?
> >
> >
> This isn't set. Was is supposed to be?
No, it's on by default, but there's an early check to determine if the
background check can
> Well any number of things, but the most recent was a prolonged power
> outage.
It is important to differentiate between expected fsck activity and
unexpected.
If you are running without write caching turned on (which is the default), a
power outtage will constitute a crash from which a file s
Randy Ramsdell wrote:
I think I will just set the rc.conf variable to answer "Y" to fsck
questions unless there is a better way.
A side note, this system has been hard shutdown two times and each time
required intervention. We also use several Linux system ( reiserfs and
ext3 ) and raely do I
On Thu, Dec 06, 2007 at 12:50:55PM -0500, Randy Ramsdell wrote:
>
>
> PS. I am confused about why so many people are replying to the list and my
> personal e-mail. This one was sent to me only. Others were sent to me and
> the list. Actually, every other reply. Is this normal for the list as I
On Thu, Dec 06, 2007 at 11:42:22AM -0500, Randy Ramsdell wrote:
> Oh, Is there a way to not receive 2 messages for every reply to this thread?
Something like this in ~/.procmailrc
:0 Wh: msgid.lock
| $FORMAIL -D 8192 msgid.cache
or like this in ~/.mailfilter
`reformail -D 8000 duplicate.cache`
Robert Huff wrote:
Randy Ramsdell writes:
> What is the value of background_fsck in /etc/rc.conf ?
>
This isn't set. Was is supposed to be? So far, I have only
installed applications we need. And everything seem fine except
the reboot issue.
I'm going to jump in here.
Vince wrote:
Randy Ramsdell wrote:
We started using FreeBSD for some network monitoring, but have found
that a hard reboot forces us to answer filesytem questions on boot. Is
there a way to mount each filesystem without this? Or how can we use
FreeBSD in a remote location without needing to i
Randy Ramsdell wrote:
> We started using FreeBSD for some network monitoring, but have found
> that a hard reboot forces us to answer filesytem questions on boot. Is
> there a way to mount each filesystem without this? Or how can we use
> FreeBSD in a remote location without needing to intervene in
Bart Silverstrim wrote:
Randy Ramsdell wrote:
We started using FreeBSD for some network monitoring, but have found
that a hard reboot forces us to answer filesytem questions on boot.
Is there a way to mount each filesystem without this? Or how can we
use FreeBSD in a remote location without ne
Randy Ramsdell wrote:
We started using FreeBSD for some network monitoring, but have found
that a hard reboot forces us to answer filesytem questions on boot. Is
there a way to mount each filesystem without this? Or how can we use
FreeBSD in a remote location without needing to intervene in
si
We started using FreeBSD for some network monitoring, but have found
that a hard reboot forces us to answer filesytem questions on boot. Is
there a way to mount each filesystem without this? Or how can we use
FreeBSD in a remote location without needing to intervene in
situatutions like this?
19 matches
Mail list logo