Little research how rm -rf and tar kill server

[Artem Kuchin]

31.03.2015 19:42, Konstantin Belousov пишет:
> On Tue, Mar 31, 2015 at 04:24:28AM +0300, Artem Kuchin wrote:
>> 30.03.2015 19:09, Mark Felder пишет:
>>
> Syncer and sync(2) perform different kind of syncs.
This is strange. Did you see what
man 2 sync
said?
It specifically refers to syncer, implying that syncer does the same sync as
man 2 sync

Is man page outdated or incorrect?
> Take the snapshot of
> sysctl debug.softdep before and after the situation occur to have some
> hints what is going on.


Will do tonight. Before, during and after the untaring.

>
> Also, it makes sense to test the HEAD kernel after the r280763. Even if
> I end up with any fix, it probably would require r280760 as prerequisite.

This is a working loaded server, i am afraid to test HEAD on it. That 
make not be compatible
with the rest of the system. And actually, i don't know how to fetch 
only kernel from HEAD :)


>
>> By the way: is there way to make sure  that SU+J is really working?
>> Maybe it is disabled for some reason
>> and i don't know it. tunefs just shows stored setting, but, for example,
>> with dirty fs, journaling is not
>> working in reality. Any way to get current status of SU journaling?
> Your statement about 'dirty fs' makes no sense.
Maybe i misunderstood something
Here is the situation:
I have dirty shutdown, so fs is dirty
fsck started at boot but said something about unexpected inconsistency
and journal is not used
i stopped fsck
and made
mount -f -a
sh /etc/rc
to boot the server and make it work anyway
(later i shutdown it again and did fsck normally)

As i understand journaling was disabled when i did mount -f -a
correct?


>
> Journaling state is displayed by mount -v.
Thank you!