From: Yura Pakhuchiy <pakhuchi@sam-solutions.net>
To: linux-xfs@oss.sgi.com, xfs-masters@oss.sgi.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: tibor@altlinux.ru, Yura Pakhuchiy <pakhuchiy@gmail.com>
Subject: XFS corruption on move from xscale to i686
Date: Thu, 07 Jul 2005 20:15:52 +0300 [thread overview]
Message-ID: <1120756552.5298.10.camel@pc299.sam-solutions.net> (raw)
Hi,
I'm creadted XFS volume on 2.6.10 linux xscale/iq31244 box, then I
copyied files on it and moved this hard drive to i686 machine. When I
mounted it on i686, I found no files on it. I runned xfs_check, here is
output:
pc299:/home/yura# xfs_check /dev/sda5
dir 128 size is 31, should be 13
dir 128 offsets too high
root directory 128 has .. 0
dir 131 entry bad inode number 4030121216
dir 131 entry SRPMS.base\x02 bad offset 0
dir 131 bad size in entry at 68
link count mismatch for inode 0 (name ?), nlink 0, counted 3
link count mismatch for inode 6303282 (name ?), nlink 0, counted 1
link count mismatch for inode 128 (name ?), nlink 3, counted 1
link count mismatch for inode 131 (name ?), nlink 5, counted 4
link count mismatch for inode 33554560 (name ?), nlink 2, counted 1
link count mismatch for inode 67108992 (name ?), nlink 2, counted 1
link count mismatch for inode 100663424 (name ?), nlink 2, counted 1
--
Best regards,
Yura
next reply other threads:[~2005-07-07 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 17:15 Yura Pakhuchiy [this message]
2005-07-08 4:21 ` XFS corruption on move from xscale to i686 Nathan Scott
2005-07-13 15:22 ` Yura Pakhuchiy
2005-07-14 1:20 ` Nathan Scott
2005-07-14 13:50 ` Yura Pakhuchiy
[not found] ` <60868aed050714065047e3aaec@mail.gmail.com>
2005-07-14 14:38 ` Christoph Hellwig
2005-07-14 14:45 ` Yura Pakhuchiy
2005-07-14 14:49 ` Christoph Hellwig
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=1120756552.5298.10.camel@pc299.sam-solutions.net \
--to=pakhuchi@sam-solutions.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=pakhuchiy@gmail.com \
--cc=tibor@altlinux.ru \
--cc=xfs-masters@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;
as well as URLs for NNTP newsgroup(s).