From: Dave Chinner <david@fromorbit.com>
To: Johan Stenehall <stenehall@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Partition seems to have been zero:ed. For no reason.
Date: Wed, 22 Oct 2008 08:21:58 +1100 [thread overview]
Message-ID: <20081021212158.GN25906@disturbed> (raw)
In-Reply-To: <934a72850810211111g20accf8ey74f0bfb8ecf38532@mail.gmail.com>
On Tue, Oct 21, 2008 at 08:11:50PM +0200, Johan Stenehall wrote:
> After a kernal upgrade My UUIDs in /etc/fstab stoped working so I changed
> them to /dev/sd* When rebooting again /dev/sdb2 didn't want to mount. I
> tried to manualy mount it without success and tried to run a xfs_repair on
> it. Got the following: http://pastebin.com/m44d3aa47
Are you using LVM or MD? i.e. did a volume get re-assembled
incorrectly and hence the XFS tools saw random fragments of a
filesystem?
> After that the partition still didn't want to mount. Had to overwrite the
> inprogress flag "xfs_db> write inprogress 0", That aloud me to mount the
> partition but it looked entirly empty.
>
> A very nice person, <sandeen_> (thank you), on xfs@freenode tried to help
> me. However it seems like the entire disk, or part of it, have been zero:ed.
>
> Does anyone know if it's possible to recover from this? And if so how?
Recovery is possible - it's called restoring from backups. You do have a
backup, don't you?
> Running Linux Ubuntu, 8.04 32-bit
> uname -r
> 2.6.24-21-generic
> xfs_repair -V
> xfs_repair version 2.9.4
Hmmmmm - haven't we have these symptoms reported by a couple of
Ubuntu users now? There's been a few ppl reporting such problems
of late....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-10-21 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 18:11 Partition seems to have been zero:ed. For no reason Johan Stenehall
2008-10-21 21:21 ` Dave Chinner [this message]
2008-10-22 6:22 ` Johan Stenehall
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=20081021212158.GN25906@disturbed \
--to=david@fromorbit.com \
--cc=stenehall@gmail.com \
--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.