Re: Using xfsdump On Linux With IRIX Version 1 FS?

Sean Elble
2009-07-25T16:24:50Z

[-- Attachment #1.1: Type: text/plain, Size: 1530 bytes --]

On 7/25/09 5:46 AM, "Christian Kujau" <lists@nerdbynature.de> 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 think (and hope, considering its age) that the disk is OK. My concern was
more with the speed that hexedit could traverse the drive searching for a
string, as opposed to dd'ing the drive to disk, editing the image, and then
dd'ing the image back to disk.

Using the loopback driver is definitely a thought, but I don't know if the
kernel on my spare box supports it or not. I'll definitely take it into
consideration, depending on how it goes, so thanks for the info.

>> 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?)
>
> C.

--
+-------------------------------------------------
| Sean Elble
| Virginia Tech, Class of 2009
| E-Mail: elbles@sessys.com
| Web: http://www.sessys.com/~elbles/
| Cell: 860.946.9477
+-------------------------------------------------

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2139 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]