From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Junfeng Yang <yjf@stanford.edu>
Cc: Andrew Morton <akpm@osdl.org>, <chaffee@bmrc.berkeley.edu>,
<mc@cs.Stanford.EDU>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [CHECKER] crash + fsck cause file systems to contain loops (msdos and vfat, 2.6.11)
Date: Sun, 13 Mar 2005 20:52:41 +0900 [thread overview]
Message-ID: <87k6ob4vau.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <Pine.GSO.4.44.0503122146410.4831-100000@elaine24.Stanford.EDU> (Junfeng Yang's message of "Sat, 12 Mar 2005 21:53:54 -0800 (PST)")
Junfeng Yang <yjf@stanford.edu> writes:
> I'm using dosfsck 2.10, 22 Sep 2003, FAT32, LFN, and yes,
> I do see root directory after I run dosfsck on the crashed disk
> image.
You can download fixed version of dosfsck at
http://user.parknet.co.jp/hirofumi/tmp/fatfsprogs.tar.bz2
(vanilla dosfsck-2.10 doesn't fix this corruption.)
> I'm checking 2.6.11. By "your testing tree didn't have my
> patches yet", you mean you have the patch but haven't made it
> public?
No. My patches was merged to linus tree at 2 or 3 days ago (merged
after 2.6.11 release). So, I guessed your tree didn't have my patches
yet.
> This "testing tree" is the Linux source tree?
Yes.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2005-03-13 11:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 10:29 Junfeng Yang
2005-03-12 10:41 ` Andrew Morton
2005-03-12 11:21 ` Junfeng Yang
2005-03-12 14:28 ` OGAWA Hirofumi
2005-03-13 5:53 ` Junfeng Yang
2005-03-13 11:52 ` OGAWA Hirofumi [this message]
2005-03-13 13:45 ` OGAWA Hirofumi
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=87k6ob4vau.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@osdl.org \
--cc=chaffee@bmrc.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mc@cs.Stanford.EDU \
--cc=yjf@stanford.edu \
/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
all inboxes | Powered by JetHome®