All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
To: linux-xfs@oss.sgi.com
Subject: Re: System partially unusable after power loss...
Date: Tue, 21 Sep 2010 23:30:05 +0200	[thread overview]
Message-ID: <i7b8ao$erp$1@dough.gmane.org> (raw)
In-Reply-To: <4C928424.1020409@sandeen.net>

Eric Sandeen wrote:
>> 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.

I didn't save this...

> Was there a system software update just prior to the power loss?

The affected files have been updated some days/weeks before.

> Did your storage support IO barriers (i.e. was it lvm or md)?

No lvm, no md. A simple IDE drive.

> 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).

I fixed this system. The reason was this silly "kbuildsycoca" or better 
a config file, accessible by the user, using this PC. Seems like this 
"non system file" got corrupted in some way. A run of "kbuildsycoca 
--noincremental" fixed the config and the system was up and running again.

But why did xfs_repair restore files... For me it seems like xfs_repair 
restored an *old* version of openssl, which has been replaced by the 
system update process. This would mean: xfs_repair made a deleted file 
visible. Is this possible?

Yours

Manuel

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-09-21 21:32 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
2010-09-21 21:30   ` Manuel Reimer [this message]
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='i7b8ao$erp$1@dough.gmane.org' \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.