From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Peder Stray <peder@ifi.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Files truncate on vfat filesystem
Date: Wed, 07 May 2003 05:02:46 +0900 [thread overview]
Message-ID: <87addzu9ll.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <Pine.SOL.4.51.0305062018090.25815@tyrfing.ifi.uio.no>
Peder Stray <peder@ifi.uio.no> writes:
> > What partition size do you use? And does that FAT use what logical
> > sector size? The directory entry pointer may be overflowed...
>
> 250GB partition, FAT32 LBA (partition type 0x0c i think).
>
> The problem is verry inconsistent as i said earlier, so the number of
> files in a directory doesn't seem to matter, nor do the depth in the
> directory structure. Some files i manage to copy yo the disk, some files i
> don't... I havent managed to find any pattern in what files this affects.
I meant, "directory entry pointer" is position of the directory entry
in the _partition_. like the following,
in fs/fat/misc.c:fat__get_entry()
offset &= sb->s_blocksize - 1;
*de = (struct msdos_dir_entry *) ((*bh)->b_data + offset);
*ino = (sector << sbi->dir_per_block_bits) + (offset >> MSDOS_DIR_BITS);
^^^
This is used for _updates_ (not create) of the directory entry. And
there is a possibility of cause of the problem which you said. If my
guess is right and a partition will be splited small, a problem will
not occur.
In short, I think it's the bug of fat driver and it's needed the fix.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2003-05-06 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 15:29 Files truncate on vfat filesystem Peder Stray
2003-05-06 17:47 ` OGAWA Hirofumi
2003-05-06 18:22 ` Peder Stray
2003-05-06 20:02 ` OGAWA Hirofumi [this message]
2003-05-06 20:19 ` Peder Stray
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 16:04 Sumit Narayan
2003-05-06 16:12 ` Peder Stray
2003-05-06 16:26 Sumit Narayan
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=87addzu9ll.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=peder@ifi.uio.no \
/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