From: "Marcin Zajączkowski" <mszpak@wp.pl>
To: linux-xfs@oss.sgi.com
Subject: xfs_ncheck (actually xfs_db) eats a lot of memory and is killed
Date: Sat, 16 Dec 2006 18:58:00 +0100 [thread overview]
Message-ID: <em1c1v$ig8$1@sea.gmane.org> (raw)
Hi,
A few weeks ago I described problem with my file system (caused by a bug
in kernel 2.6.17) - http://oss.sgi.com/archives/xfs/2006-11/msg00271.html
Recently I've got rescue CD with xfs_progs in version 2.8.11 and tried
to repair it. xfs_repair gave me about 150 files with names like inode
numbers in /lost+found and 1500 "normal" named files in its subdirectory.
I've tried to use "xfs_ncheck -i inode /dev/hdX" to got names
corresponding with specified inode(s), but program had been runing
several minutes, xfs_db had eaten all available memory (768MB) and was
killed by system (whole system hung too). The second time I killed it
(kill -15) when it ate whole available memory.
My file system has about 6GB and is filled with 95%.
Am I doing something wrong with xfs_db?
Is there any easier way to restore my files?
Btw, xfs_check shows two lines:
link count mismatch for inode 1572882 (name ?), nlink 16, counted 15
link count mismatch for inode 2102297 (name ?), nlink 2, counted 3
Can it be reason for strange xfs_db behavior?
Thanks for help
Marcin
next reply other threads:[~2006-12-16 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 17:58 Marcin Zajączkowski [this message]
2006-12-18 1:24 ` xfs_ncheck (actually xfs_db) eats a lot of memory and is killed Barry Naujok
2006-12-18 8:15 ` Marcin Zajączkowski
2006-12-18 23:54 ` Barry Naujok
2006-12-19 7:38 ` Marcin Zajączkowski
2006-12-20 1:05 ` Barry Naujok
2006-12-21 7:42 ` Marcin Zajączkowski
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='em1c1v$ig8$1@sea.gmane.org' \
--to=mszpak@wp.pl \
--cc=linux-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.