From: Eric Sandeen <sandeen@sandeen.net>
To: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
Cc: linux-xfs@oss.sgi.com
Subject: Re: System partially unusable after power loss...
Date: Thu, 16 Sep 2010 15:55:00 -0500 [thread overview]
Message-ID: <4C928424.1020409@sandeen.net> (raw)
In-Reply-To: <i6ttq6$41d$1@dough.gmane.org>
Manuel Reimer wrote:
> Hello,
>
> Kernel is 2.6.27.7.
>
> My Problem started as I got called, that login from KDM is not longer
> possible. In fact, the KDE login is possible, but soon after entering
> the password, a "kbuildsycoca" hangs and takes 100% CPU. Shortly before
> this happened, power was abruptly lost.
>
> I rebooted to a live CD. As, for some reason, xfs_check was broken on
> that live CD (something with "db" in it was missing), I directly ran
xfs_check is a shell script that invokes xfs_db
> xfs_repair on the broken hard drive and it found some zero byte files
better to run xfs_repair -n rather than xfs_check anyway ...
> and two files with ELF header, which may be (a part of) library files, I
> don't know, as the name wasn't restored.
Having the xfs_repair output would be helpful.
> Is it possible to find out what exactly happened to cause this system to
> be unusable? For me it seems like those restored ELF files are
> something, needed by KDE to start up properly. Why did library files get
> destroyed, the user, using this PC, isn't able to write to? Doesn't this
> mean, they don't get into a write cache and even a power loss can't
> destroy them?
Was there a system software update just prior to the power loss?
Did your storage support IO barriers (i.e. was it lvm or md)?
Buffered data is always lost on a power loss, but I'm not sure
why you should see problems with system files unless they had
just been written out (and not synced).
-Eric
> Yours
>
> Manuel
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-16 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 20:10 System partially unusable after power loss Manuel Reimer
2010-09-16 20:55 ` Eric Sandeen [this message]
2010-09-21 21:30 ` Manuel Reimer
2010-09-22 4:15 ` Eric Sandeen
2010-09-24 20:44 ` Manuel Reimer
2010-09-16 21:23 ` Michael Monnerie
2010-09-17 20:15 ` Peter Grandi
2010-09-20 7:37 ` Michael Monnerie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C928424.1020409@sandeen.net \
--to=sandeen@sandeen.net \
--cc=Manuel.Spam@nurfuerspam.de \
--cc=linux-xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox