From: Benedikt Schmidt <benedikt.schmidt@tum.de>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair force_geometry
Date: Tue, 14 May 2013 07:11:14 +0200 [thread overview]
Message-ID: <5191C772.4020607@tum.de> (raw)
In-Reply-To: <519165F2.80902@sandeen.net>
[-- Attachment #1.1: Type: text/plain, Size: 1875 bytes --]
First of all: Thanks for your very fast and helpful response.
I copied actually only the partition, not the whole disk: /dd_rescue
--force -r1 /dev/sdd1 /dev/sdc1/
The cause for this is that I don't have enough space left on another
device to store a whole copy of the faulty disk. I thought it would be
possible, like in some examples I found with google, that you can rescue
a partition directly.
/file -s /dev/sdc1/ says:
//dev/sdc1: data/
The disks look like this (/fdisk -l/):
/Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors//
//Units = Sektoren of 1 * 512 = 512 bytes//
//Sector size (logical/physical): 512 bytes / 4096 bytes//
//I/O size (minimum/optimal): 4096 bytes / 4096 bytes//
//Disk identifier: 0xcba506ee//
//
// Gerät boot. Anfang Ende Blöcke Id System//
///dev/sdc1 256 732566645 366283195 83 Linux//
//
//Disk /dev/sdd: 2000.4 GB, 2000397852160 bytes, 3907027055 sectors//
//Units = Sektoren of 1 * 512 = 512 bytes//
//Sector size (logical/physical): 512 bytes / 512 bytes//
//I/O size (minimum/optimal): 512 bytes / 512 bytes//
//Disk identifier: 0x3c34826b//
//
// Gerät boot. Anfang Ende Blöcke Id System//
///dev/sdd1 63 3907024064 1953512001 83 Linux/
If it is not possible to rescue the partition this way I will have to
extend my to RAID5 so that I can put the copy of the faulty disk on this
one, like Michael explained in his answer. I just hoped that I can avoid
this, because it would save me more than 100EUR.
As last information: The content of this copy is not totally lost,
actually only the last few files I have added. All the other stuff is
already stored on the RAID5, only the latest stuff is not contained in
this backup. So I don't loose everything if something goes wrong (at
least one thing :-) ).
Kind regards,
Benedikt
[-- Attachment #1.2: Type: text/html, Size: 3122 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-14 5:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 12:24 xfs_repair force_geometry Benedikt Schmidt
2013-05-13 16:58 ` Michael L. Semon
2013-05-13 17:56 ` Stan Hoeppner
2013-05-13 22:15 ` Eric Sandeen
2013-05-14 5:11 ` Benedikt Schmidt [this message]
2013-05-14 7:50 ` Michael L. Semon
2013-05-14 8:56 ` Benedikt Schmidt
2013-05-14 12:35 ` Stan Hoeppner
2013-05-14 17:54 ` Michael L. Semon
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=5191C772.4020607@tum.de \
--to=benedikt.schmidt@tum.de \
--cc=benediktibk@aon.at \
--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