Prev: httpd rewrite or redirect to subdomain
Next: Recovering edited files after crashes
From: Grant on 19 Jul 2010 21:56
On Mon, 19 Jul 2010 17:36:39 -0600, Danno <WhoaBaby(a)MySecretPlace.org> wrote:

>On Mon, 19 Jul 2010 07:45:45 +1000
>Grant <omg(a)grrr.id.au> wrote:
>
>> On Sun, 18 Jul 2010 14:23:59 -0600, Danno <WhoaBaby(a)MySecretPlace.org> wrote:
>>
>> > I've endured a couple of fairly hard crashes recently (power outage, failed UPS), am trying to recover, but am wondering if things are beyond recovery this time.
>> > I'm able to boot up, and my commonly used apps seem to run, but I notice the output of "top" and "ps" no longer show CPU percentage for specific tasks (everything is 0.0), "top" seems to be showing proper memory accounting, though. I'm also getting an occasional crash of an application for no obvious reason. I suspect the two are related, perhaps the CPU/core management has been affected, but it is a little beyond my experience to know for sure. Would a hard crash affect /proc after a reboot? My understanding is that the kernel needs /proc to manage processes.
>> > I'm running Slack.12.2, stock SMP 2.6.27.7 kernel except for the nVidia module, have considered simply re-installing the kernel from the installation disc, but am not sure if that will restore the /proc interface?
>> > Any direction or insight would be helpful.
>>
>> I've not encountered post-crash problems that you report. If you think
>> reinstalling the kernel will fix it, try that and tell us what happens?
>> Wont do any harm ;)
>>
>> Which filesystem, what post-crash actions did you take to repair or
>> check filesystem?
>>
>> Grant.
>
> Had been running XFS on two partitions, ran xfs_repair, which caught some inconsistencies, but the random crashes and issues with /proc ultimately convinced me to do a fresh install of 13.1 (and get a new friggin UPS). The KDE was pooched enough that I couldn't start it, all my Wine apps started misbehaving, my bittorrent servent was unreliable... it seemed the effort spent recovering the 12.2 install will be better spent bringing 13.1 up to snuff. FWIW, migrating Sylpheed from 12.2 to 13.1 was a breeze. I hope the rest goes so smoothly...

XFS is known for not tolerating unexpected power fail, I guess you've
confirmed that :(

Grant.
From: Danno on 19 Jul 2010 22:39
On Tue, 20 Jul 2010 11:56:39 +1000
Grant <omg(a)grrr.id.au> wrote:
<snip>
>
> XFS is known for not tolerating unexpected power fail, I guess you've
> confirmed that :(
>
> Grant.

I actually endured a few power failures over a short period of time, and XFS seemed pretty resilient. I guess one can only push their luck so far LOL.
FWIW, my first blush with 13.1 and XFCE is very good. Configuring CUPS was trivial, the nVidia module worked brainlessly, NFS was flawless, Thunar feels like a viable replacement for Konqueror. I should have installed 13.1 when it was released.

--
Slackware 13.1, 2.6.33.4-smp, Core i7 920
RLU #272755
From: jim dorey on 23 Jul 2010 07:41
Danno wrote:
> I've endured a couple of fairly hard crashes recently (power outage,
> failed UPS), am trying to recover, but am wondering if things are
> beyond recovery this time.

same, but it messed up my net(inter) access, get a lot of timeouts, but
once there's a connection it's as fast as always. been trying to figure
it out for a while...
First  |  Prev  | 
Pages: 1 2
Prev: httpd rewrite or redirect to subdomain
Next: Recovering edited files after crashes