public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Fixing xfs filesystem?
Date: Sat, 09 Jul 2005 21:20:02 +0200	[thread overview]
Message-ID: <42D02362.7060105@mid.alexander.skwar.name> (raw)

Hi!

A short time ago, there was a quick power outage, because of which
some of my xfs filesystems broke :(

When I call xfs_check, I get output like this:

[21:11:09 alexander@server:~] $ sudo /bin/xfs_check /dev/mapper/Crypt-daten
xfs_check: unexpected XFS SB magic number 0x00000000
xfs_check: read failed: Invalid argument
xfs_check: data size check failed
xfs_check: cannot read root inode (22)
xfs_check: cannot read realtime bitmap inode (22)
/bin/xfs_check: line 56: 14148 Speicherzugriffsfehler  xfs_db$DBOPTS -i -p xfs_check -c "check$OPTS" $1

"xfs_repair" also isn't successful :(

[20:55:48 alexander@server:~] $ sudo xfs_repair /dev/mapper/Crypt-daten
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...
..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
...................................................................................Sorry,
could not find valid secondary superblock
Exiting now.

Is there any other way to regain the data or are they gone for
good?

PS: No, I do not have a backup. Thus the data wasn't "important"...
Still, I'd like to get a hold of the data, if possible...

Alexander Skwar
-- 
Kill Ugly Processor Architectures
- Karl Lehenbauer
-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2005-07-09 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-09 19:20 Alexander Skwar [this message]
2005-07-10 12:55 ` [gentoo-user] Fixing xfs filesystem? Bob Sanders
2005-07-10 17:15   ` Alexander Skwar
2005-07-12  2:40     ` Bob Sanders
2005-07-16  6:34       ` Alexander Skwar

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=42D02362.7060105@mid.alexander.skwar.name \
    --to=listen@alexander.skwar.name \
    --cc=gentoo-user@lists.gentoo.org \
    /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