>> After panic data *is* getting corrupted anyway - MySQL tables that were
>> open are broken, soft-updates are unsync'ed etc etc.
> If it's an option for you, you may want to look into disabling soft
> updates as well so that you don't have to just hope that everything gets
> synced before the end
On Fri, 18 Dec 2009, ïÌÅÇ ðÅÔÒÁÞ£× wrote:
Konrad, Erik, thank you for the good advice. Several foreground fsck
in a row really helped.
Konrad, which hardware are you using with FreeBSD on heavily loaded
and i/o-bound systems?
One of these systems is a Dell PowerEdge 2650 with Qlogic ISP 2312
On Tue, Dec 08, 2009 at 01:41:04PM +0300, cronfy wrote:
>
> After panic data *is* getting corrupted anyway - MySQL tables that were
> open are broken, soft-updates are unsync'ed etc etc.
By the way, you might want to look into using a DBMS that (unlike MySQL)
doesn't hose up open tables because
Konrad, Erik, thank you for the good advice. Several foreground fsck
in a row really helped.
Konrad, which hardware are you using with FreeBSD on heavily loaded
and i/o-bound systems?
>> If you have other instances of filesystem corruption (which includes
>> everything which can trigger a kernel
On Tue, 8 Dec 2009, Erik Trulsson wrote:
On Tue, Dec 08, 2009 at 02:09:03PM +0300, cronfy wrote:
panics like 'freeing free block' or 'ffs_valloc: dup alloc'
Is there a way to say "Dear kernel, don't panic, I'am holding your
hand, keep working please-please-please?" If so, can it lead to
c
On Tue, 8 Dec 2009, cronfy wrote:
Please forgive me for probably a very stupid question. But why is FreeBSD
so sensitive to filesystem errors that it ends up with panics like
'freeing free block' or 'ffs_valloc: dup alloc'? I just can't get it.
Failed to allocate vnode? Go allocate another
On Tue, Dec 08, 2009 at 02:09:03PM +0300, cronfy wrote:
>
> panics like 'freeing free block' or 'ffs_valloc: dup alloc'
> >>
> >> Is there a way to say "Dear kernel, don't panic, I'am holding your
> >> hand, keep working please-please-please?" If so, can it lead to
> >> complete filesystem
cronfy wrote:
>
>>> ...
>>> Is there a way to say "Dear kernel, don't panic, I'am holding your hand,
>>> keep working please-please-please?" If so, can it lead to complete
>>> filesystem corruption indeed or it is not so serious?
>>>
>>
>> Drop to DDB, fix it, and 'continue'?
>>
>
> If I
panics like 'freeing free block' or 'ffs_valloc: dup alloc'
Is there a way to say "Dear kernel, don't panic, I'am holding your
hand, keep working please-please-please?" If so, can it lead to
complete filesystem corruption indeed or it is not so serious?
Afaik you can't do this. And you sh
...
Is there a way to say "Dear kernel, don't panic, I'am holding your hand,
keep working please-please-please?" If so, can it lead to complete
filesystem corruption indeed or it is not so serious?
Drop to DDB, fix it, and 'continue'?
If I type 'continue' kernel says 'Dumping... rebo
cronfy wrote:
> ...
> Is there a way to say "Dear kernel, don't panic, I'am holding your hand,
> keep working please-please-please?" If so, can it lead to complete
> filesystem corruption indeed or it is not so serious?
Drop to DDB, fix it, and 'continue'?
--
Fuzzy love,
-CyberLeo
Technical Admi
.. but the hell why is it required to panic and kill everything
that would be working happily even if something very disasterous
happen to /backup partition, in example?
All those errors indicate file system corruption. To protect other data
from getting corrupted (e.g. by invalid pointe
Please forgive me for probably a very stupid question. But why is
FreeBSD so sensitive to filesystem errors that it ends up with panics
like 'freeing free block' or 'ffs_valloc: dup alloc'? I just can't
get it. Failed to allocate vnode? Go allocate another one! Freeing
free block? Leave it fr
Ivan Voras wrote:
> cronfy wrote:
>> ... but the hell why is it required to panic and kill everything
>> that would be working happily even if something very disasterous
>> happen to /backup partition, in example?
>
> All those errors indicate file system corruption. To protect other data
> from g
cronfy wrote:
Hello.
Please forgive me for probably a very stupid question. But why is
FreeBSD so sensitive to filesystem errors that it ends up with panics
like 'freeing free block' or 'ffs_valloc: dup alloc'? I just can't get
it. Failed to allocate vnode? Go allocate another one! Freeing fr
Hello.
Please forgive me for probably a very stupid question. But why is
FreeBSD so sensitive to filesystem errors that it ends up with panics
like 'freeing free block' or 'ffs_valloc: dup alloc'? I just can't get
it. Failed to allocate vnode? Go allocate another one! Freeing free
block? Leav
16 matches
Mail list logo
