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@vger.kernel.org>
Subject: Re: [CHECKER] crash + fsck cause file systems to contain loops (msdos and vfat, 2.6.11)
Date: Sat, 12 Mar 2005 23:28:34 +0900 [thread overview]
Message-ID: <87fyz1ey5p.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <Pine.GSO.4.44.0503120313140.11724-100000@elaine24.Stanford.EDU> (Junfeng Yang's message of "Sat, 12 Mar 2005 03:21:19 -0800 (PST)")
Junfeng Yang <yjf@stanford.edu> writes:
>> Linus's current tree includes support for `mount -o sync' on the msdos and
>> vfat filesystems.
>
> Thanks Andrew. I can just do a bk clone from
> http://linux.bkbits.net/linux-2.6 to get Linus's current tree, right?
>
> The warning reported here doesn't need mount -o sync to trigger though.
> A simple crash on a default mounted FS can usually cause the FS loop.
>
> (Also, I realized I made many typos in my report --- this implies I'm
> tired and should probably get some sleep :)
Interesting.
$ /devel/linux/works/fatfs/fatfstools/dosfstools-2.10/dosfsck/dosfsck -a bug10/crash.img
dosfsck 2.10, 22 Sep 2003, FAT32, LFN
/0006
Directory does not have any cluster ("." and "..").
Dropping it.
Reclaimed 3 unused clusters (6144 bytes) in 3 chains.
Performing changes.
crash.img: 8 files, 3/8167 clusters
My fixed dosfsck found the above corruption in bug10/crash.img (bug7
has same corruption). And probably you can see root directory via 0006
directory, I guess your testing tree didn't have my patches yet (seems
old behavior).
BTW, what mount options did you use?
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2005-03-12 14:31 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 [this message]
2005-03-13 5:53 ` Junfeng Yang
2005-03-13 11:52 ` OGAWA Hirofumi
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=87fyz1ey5p.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®