public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Scott, Edmund J @ SSG - Link" <edmund.scott@l-3com.com>
Cc: Ben Myers <bpm@sgi.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: SGI Version 1 XFS on Linux
Date: Thu, 7 May 2015 07:58:16 +1000	[thread overview]
Message-ID: <20150506215816.GE4327@dastard> (raw)
In-Reply-To: <2994A55DE0FBBE41B8FE47F9885D74221BC056F3@ARLEXCHMBX02.lst.link.l-3com.com>

On Wed, May 06, 2015 at 07:47:51PM +0000, Scott, Edmund J @ SSG -
Link wrote:
> Hi,
> 
> We are in a thunderstorm right now so we had to shut down, be a
> while until we get things back up. We're in Utah with a rolling
> t-storm coming through. 
> 
> We did find documentation that XFS version 1 was pulled out of the
> linux kernel around or after kernel 2.4. and the messages kind of
> support that. I'm looking into digging up an old Red Hat OS to see
> if it is old enough to have the version 1 XFS in it.

You'd be talking about the directory version, then, not the version
of the filesystem? Irix 6.2 introduced Version 4 filesystems, but
version 2 directories didn't come along until a couple of years
later. See Slides 6-7 here:

http://events.linuxfoundation.org/sites/events/files/slides/dchinner-xfs-there-and-back.pdf

As it is, the dirv1 removal commit says "Never functioned on Linux,
just pure bloat".

http://oss.sgi.com/cgi-bin/gitweb.cgi?p=archive/xfs-import.git;a=commitdiff;h=b84149405b9c2ecbc445d2684053e4acc03342ee

So I suspect that the only way you are going to be able to read
those filesystems is with an Irix machine....

> While it was up, we've done the blkid command and it recognizes at
> least 1 partition on the SGI drive to be xfs, others were efs. We
> also used the hardware browser and got the same readings.

Yeah, that's old ;)

> We've also tried to make a disk image. If I try to mount the image
> on the linux computer, it will essentially give me the same error
> about version 1 xfs. Not that this was unexpected, it should error
> out just like the drive did. I also happen to have an O2 up and
> running, so I copied the image over to the O2 expecting to try and
> mount the image so it would/should automatically handle the xfs
> issue, but it looks like the O2 mount command does not have the
> loop or knows how to handle mounting an image like the Linux does.

http://www.nekochan.net/wiki/Loopback_Filesystems

Nekochan is the place to go for information about old SGI boxes.
It might be worth posting there to see if there is anyone local to
you with working hardware that would enable you to pull the
information off the disks....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  parent reply	other threads:[~2015-05-06 21:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 15:12 SGI Version 1 XFS on Linux Scott, Edmund J @ SSG - Link
2015-05-06 17:12 ` Ben Myers
2015-05-06 19:47   ` Scott, Edmund J @ SSG - Link
2015-05-06 21:48     ` Ben Myers
2015-05-06 21:58     ` Dave Chinner [this message]
2015-05-06 22:38       ` Scott, Edmund J @ SSG - Link
2015-05-07  3:05       ` Eric Sandeen
2015-05-07 10:24 ` Emmanuel Florac

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=20150506215816.GE4327@dastard \
    --to=david@fromorbit.com \
    --cc=bpm@sgi.com \
    --cc=edmund.scott@l-3com.com \
    --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