public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Jaap Struyk <japie@deserver.nl>
Cc: xfs@oss.sgi.com
Subject: Re: ways to restore data from crashed disk
Date: Thu, 07 Jun 2007 14:28:31 -0500	[thread overview]
Message-ID: <46685C5F.5090804@sandeen.net> (raw)
In-Reply-To: <46684A9B.90908@deserver.nl>

Jaap Struyk wrote:
> Eric Sandeen schreef:
> 
>> For starters, is the file really that big?  (9397895168 bytes?)
> 
> dd_rhelp /dev/hdd4 hdd4.img
> xfs_repair hdd4.img
> Phase 1 - find and verify superblock...
> superblock read failed, offset 103376846848, size 2048, ag 11, rval 0
> fatal error -- Gelukt (gelukt is dutch for sucses or done)
> 
> The image is 92G. big but my original filesystem was about 120G. but the
> 92G is about the size of the data that was on the disc.

when you are talking about sizes, do you mean space used (du) or max
offset (ls -l?)  max offset should be the same for your image file as
for your original device... 120G.

-Eric

> dd_rhelp /dev/hdd4 hdd4.img info:
> - Jump pos : 96365061.0 - max file size : 156019623.0
> - Biggest hole size :  119309126 k - total holes : 0k
> - xferd(succ/err) : 36710498.0k(36710496.0k/2.0k)
> - EOF is not found, but between 36710498.0k and 156019623.0k.
> ALL your data has been dd_rescued !!

  parent reply	other threads:[~2007-06-07 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 10:50 ways to restore data from crashed disk Jaap Struyk
2007-05-31 13:37 ` Eric Sandeen
2007-06-07 18:12   ` Jaap Struyk
2007-06-07 18:56     ` Jaap Struyk
2011-05-26 12:39       ` Robert
2007-06-07 19:28     ` Eric Sandeen [this message]
2007-06-08  4:03       ` Jaap Struyk
2007-06-08 15:58         ` Eric Sandeen
2007-06-09  7:50           ` Jaap Struyk

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=46685C5F.5090804@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=japie@deserver.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