public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Sean Elble <elbles@sessys.com>, xfs@oss.sgi.com
Subject: Re: Using xfsdump On Linux With IRIX Version 1 FS?
Date: Sat, 25 Jul 2009 12:22:58 +0200	[thread overview]
Message-ID: <20090725102258.GA1121@citd.de> (raw)
In-Reply-To: <alpine.DEB.2.01.0907250241170.6426@bogon.housecafe.de>

On 25.07.2009 02:46, Christian Kujau wrote:
> On Sat, 25 Jul 2009 at 09:26, Matthias Schniedermeyer wrote:
> > >   # losetup -r /dev/loop0 /path/to/IRIXbackup
> > >   # hexedit /dev/loop0 ...or whatever tool you'll be using.
> > 
> > Which has what advantage over directly changing the image?
> 
> Sean mentioned the "thrashing of the old disk" and I figured I'd be 
> worried not only by that but that the old disk might die anytime soon. So 
> I wanted to present an alternative to do the search - I don't know too 
> much about his setup, so it's up to him to follow this advice or not.

I meant: What is the advantage of using the a loop-device (of the image) 
instead of directly using the image?

> > Even with just 10MB/s it's less than 4 Minutes for 2GB.
> > In comparison it takes over 3 hours to copy a modern 1TB HDD @ 80MB/s.
> 
> ?? (what kind of comparison is that?)

That you can read/write whole "ancient" discs without having to wait for 
hours?





Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-07-25 10:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 23:57 Using xfsdump On Linux With IRIX Version 1 FS? Sean Elble
2009-07-24  2:23 ` Eric Sandeen
2009-07-24  3:02   ` Sean Elble
2009-07-24  3:32   ` Sean Elble
2009-07-24  7:30     ` Matthias Schniedermeyer
2009-07-24 15:36       ` Sean Elble
2009-07-24 17:11         ` Matthias Schniedermeyer
2009-07-24 19:13           ` Sean Elble
2009-07-25  3:53             ` Christian Kujau
2009-07-25  7:26               ` Matthias Schniedermeyer
2009-07-25  9:46                 ` Christian Kujau
2009-07-25 10:22                   ` Matthias Schniedermeyer [this message]
2009-07-25 10:36                     ` Christian Kujau
2009-07-25 16:25                   ` Sean Elble
2009-07-26  0:24                   ` Sean Elble
2009-07-24  8:23     ` Andi Kleen

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=20090725102258.GA1121@citd.de \
    --to=ms@citd.de \
    --cc=elbles@sessys.com \
    --cc=lists@nerdbynature.de \
    --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