public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: hank peng <pengxihan@gmail.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@oss.sgi.com
Subject: Re: can xfs_repair guarantee a complete clean filesystem?
Date: Wed, 2 Dec 2009 08:46:20 +0800	[thread overview]
Message-ID: <389deec70912011646y682a2cc2rd5d4ea8cfe78d2f5@mail.gmail.com> (raw)
In-Reply-To: <4B1539C6.90000@sandeen.net>

2009/12/1 Eric Sandeen <sandeen@sandeen.net>:
> 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.
>
We did have plan to upgrade kernel to latest 2.6.31.
BTW, Is there some place where I can check those fixed bug list across versions?
> -Eric
>
>>> -Eric
>>>
>>
>>
>>
>
>



-- 
The simplest is not all best but the best is surely the simplest!

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

  reply	other threads:[~2009-12-02  0:45 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
2009-12-02  0:46               ` hank peng [this message]
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=389deec70912011646y682a2cc2rd5d4ea8cfe78d2f5@mail.gmail.com \
    --to=pengxihan@gmail.com \
    --cc=linux-xfs@oss.sgi.com \
    --cc=sandeen@sandeen.net \
    /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