All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jürgen Fischer" <jfi.pcs@t-online.de>
To: xfs@oss.sgi.com
Subject: Problem with xfs devices
Date: Tue, 11 Mar 2008 15:33:17 +0100	[thread overview]
Message-ID: <47D6982D.7030305@t-online.de> (raw)

Hi,

I have some problems with xfs devices which I can't mount and hope you 
can help me.

I have the devices md1, md5, md6, md7, md8 on a Root-Server by a german 
provider with SuSE linux 10.2. I've made yesterday evening an online 
update which updates the kernel and wants a reboot after that. Since 
that no rebbot is possible, no help available from provider.
The devices md1, md5 and md8 I can mount without problems. But if i try 
to mount md6 or md7 I got the following messages on the screen:

rescue:~# mount /dev/md6 /mnt
Killed
rescue:~#
Message from syslogd@rescue at Tue Mar 11 00:48:37 2008 ...
rescue kernel: Oops: 0000 [2] SMP

Message from syslogd@rescue at Tue Mar 11 00:48:37 2008 ...
rescue kernel: CR2: 0000000000000008

No xfs_check or xfs_repair is possible. I got this messages:

rescue:~# xfs_check -v /dev/md6
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_check.  If you are unable to mount the filesystem, then use
the xfs_repair -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
rescue:~#

I can start after that the xfs_repair -L command but nothing is happend. 
I wait 30 minutes or so an tra to kill the process - impossible. I must 
restart my rescue system.

I would be great if you can help me.

Regards

Juergen

             reply	other threads:[~2008-03-11 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 14:33 Jürgen Fischer [this message]
2008-03-11 16:24 ` Problem with xfs devices Eric Sandeen

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=47D6982D.7030305@t-online.de \
    --to=jfi.pcs@t-online.de \
    --cc=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.