From: Eric Sandeen <sandeen@sandeen.net>
To: metaverse <metaverse@artikel-140.nl>, xfs@oss.sgi.com
Subject: Re: Create superblock
Date: Fri, 20 Jun 2014 09:27:00 -0500 [thread overview]
Message-ID: <53A444B4.2010803@sandeen.net> (raw)
In-Reply-To: <1403246832932-35023.post@n7.nabble.com>
On 6/20/14, 1:47 AM, metaverse wrote:
> Last week a harddrive in a NAS crashed in our office. Long story short: We
> have been trying everything. In the end we where able to pull an image of
> the hard drive. Also we found out there's no superblock or secondary blocks.
> Since I have recovered successfully the data I was wondering if it was
> possible to create a new superblock and secondary block. If not I'll create
> a new partition and place all the data back.
Not really enough info to go on here. How did you recover the data if
you have no valid superblock?
If you've got your data back, just mkfs a fresh filesystem and repopulate it.
Or by "recovered the data" do you just mean you have a dd image of the broken
drive?
> Scary that only a power outage can do this...
It shouldn't, unless the storage was configured in an unreliable way.
> TL;DR: Is it possible to create a new superblock from scratch?
Not in general, but rather than jumping to the proposed solution, perhaps
it would be better to describe the problem in detail:
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
At an absolute bare minimum, what happened when you ran xfs_repair?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-06-20 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 6:47 Create superblock metaverse
2014-06-20 14:27 ` Eric Sandeen [this message]
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=53A444B4.2010803@sandeen.net \
--to=sandeen@sandeen.net \
--cc=metaverse@artikel-140.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox