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 19:08:44 -0600 [thread overview]
Message-ID: <4B15BE1C.2030209@sandeen.net> (raw)
In-Reply-To: <389deec70912011646y682a2cc2rd5d4ea8cfe78d2f5@mail.gmail.com>
hank peng wrote:
> 2009/12/1 Eric Sandeen <sandeen@sandeen.net>:
...
>>> 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.
Well, I'm just suggesting testing it for now, not necessarily
upgrading your product. Would just be good to know if the bug you
are seeing persists upstream on ppc.
> BTW, Is there some place where I can check those fixed bug list across versions?
You can look at the changelogs on kernel.org, for instance:
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.32
Or with git, git log --pretty-oneline fs/xfs
There isn't a great bug <-> commit <-> kernelversion mapping, I guess.
-Eric
>> -Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-12-02 1:08 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
2009-12-02 1:08 ` Eric Sandeen [this message]
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=4B15BE1C.2030209@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