From: Eric Sandeen <sandeen@sandeen.net>
To: hank peng <pengxihan@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: can xfs_repair guarantee a complete clean filesystem?
Date: Tue, 01 Dec 2009 09:44:06 -0600 [thread overview]
Message-ID: <4B1539C6.90000@sandeen.net> (raw)
In-Reply-To: <389deec70912010732o72edd3c4q196088a1c01b801e@mail.gmail.com>
hank peng wrote:
> 2009/12/1 Eric Sandeen <sandeen@sandeen.net>:
>> hank peng wrote:
>>
>>> Today, I encountered a problem:
>>> I use "xfs_repair -L “ on a damaged filesystem and a lot of messages
>> why did you use -L, did it fail to mount & replay the log properly?
>>
> umount, mount, umount and then xfs_repair failed, so I have to use -L.
Failed how? that's a bug. (or, -L did nothing anyway because the log
wasn't dirty after the clean unmount)
>>> output which include "moving disconnected inodes to lost+found ...".
>>> Then I can remount the filesystem successfully and decided to remove
>>> those files in lost+found directory, but it printed the following
>>> message:
>>> root@1234dahua:/mnt/Pool_md1/ss1/lost+found# rm -rf *
>>> rm: cannot stat '710': Structure needs cleaning
>>> rm: cannot stat '728': Structure needs cleaning
>>> rm: cannot stat '729': Structure needs cleaning
>>> rm: cannot stat '730': Structure needs cleaning
>>> rm: cannot stat '731': Structure needs cleaning
>>> rm: cannot stat '732': Structure needs cleaning
>>> rm: cannot stat '733': Structure needs cleaning
>>> rm: cannot stat '734': Structure needs cleaning
>>> rm: cannot stat '735': Structure needs cleaning
>> Look at dmesg to see what's gone wrong....
>>
>
>>> Other directories and files seems normal to access, is it not allowed
>>> to delete files in lost+found directory after repair, then what should
>>> I do?
>> This is indicative of a bug or IO error that caused xfs to shut down.
>>
>> You haven't mentioned which kernel version, architecture, or
>> version of xfsprogs you're using yet ... that may offer some clues.
>>
>
>> I'm guessing an older kernel and userspace on arm? :)
>>
> kernel version is 2.6.23, xfsprogs is 2.9.7, CPU is MPC8548, powerpc arch.
> I am at home now, Maybe I can provide some detailed information tomorrow.
If there's any possibility to test newer kernel & userspace, that'd
be great. Many bugs have been fixed since those versions.
-Eric
>> -Eric
>>
>
>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-12-01 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 2:05 can xfs_repair guarantee a complete clean filesystem? hank peng
2009-12-01 3:54 ` Eric Sandeen
2009-12-01 4:37 ` hank peng
2009-12-01 5:58 ` Eric Sandeen
2009-12-01 6:34 ` hank peng
2009-12-01 14:43 ` Eric Sandeen
2009-12-01 15:32 ` hank peng
2009-12-01 15:44 ` Eric Sandeen [this message]
2009-12-02 0:46 ` hank peng
2009-12-02 1:08 ` Eric Sandeen
2009-12-02 1:36 ` hank peng
2009-12-02 2:39 ` hank peng
2009-12-02 3:52 ` Eric Sandeen
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=4B1539C6.90000@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@oss.sgi.com \
--cc=pengxihan@gmail.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