From: Eric Sandeen <sandeen@sandeen.net>
To: Honza Fikar <j.fikar@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: recover xfs with v1 dirs on linux?
Date: Mon, 16 Oct 2006 08:53:13 -0500 [thread overview]
Message-ID: <45338EC9.9010501@sandeen.net> (raw)
In-Reply-To: <2117b660610160232p1ffb28e0necfeeb377b5d4ead@mail.gmail.com>
Honza Fikar wrote:
> Hi everybody,
>
> I want to recover old SGI Irix xfs disks, but I don't have any more the old
> hardware. I was able to copy the xfs partition in a file with dd and I could
> run xfs_recover, xfs_check and xfs_ncheck, which gives me the filenames. But
> I was not able to mount this file. Kernel 2.6.17 gives "Function not
> implemented", while 2.6.5 mounts, but the disk looks empty.
>
> I think the reason is "v1 dirs":
>
> file img4.xfs
> img4.xfs: SGI XFS filesystem data (blksz 4096, inosz 256, v1 dirs)
>
> Is there a way to get the files? I have the innode numbers and filenames as
> an output of xfs_ncheck:
> ....
> 947364 abc/MIXDUM/MD110/20K/step9/dynrt.out.gz
> 184821 aa/Monteal/fmd3kev-45K/cluster.I.076.gz
> 1286273 abc/MIXDUM/MD111/250K/step10/dyn5.f1.gz
> ...
v1dir support was removed a short while ago, they never really worked on Linux.
http://oss.sgi.com/projects/xfs/faq.html#useirixxfs
Older kernels had rudimentary v1 support, and you may find some degree of
functionality, or, as it seems in your case, no functionality at all.
If this is terribly important data, then some finite amount of work (involving a
patched glibc, IIRC) might be able to get you going.
-Eric
next prev parent reply other threads:[~2006-10-16 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 9:32 recover xfs with v1 dirs on linux? Honza Fikar
2006-10-16 13:53 ` Eric Sandeen [this message]
2006-10-17 6:34 ` Mike Gigante
2006-10-17 9:31 ` Honza Fikar
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=45338EC9.9010501@sandeen.net \
--to=sandeen@sandeen.net \
--cc=j.fikar@gmail.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