All of lore.kernel.org
 help / color / mirror / Atom feed
From: hirofumi@mail.parknet.co.jp (OGAWA Hirofumi)
To: kernelnewbies@lists.kernelnewbies.org
Subject: VFAT i_pos value
Date: Fri, 02 Dec 2011 04:20:40 +0900	[thread overview]
Message-ID: <871usoxfnb.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <4ED7AD8F.7000206@gnukai.com> (Kai Meyer's message of "Thu, 01 Dec 2011 09:38:39 -0700")

Kai Meyer <kai@gnukai.com> writes:

>> The i_pos means directory entry (contains inode information in unix-fs)
>> position,
>>
>>      block number == i_pos / (logical-blocksize / 32)
>>      offset       == i_pos&  (logical-blocksize / 32)
>>
>> the above position's directory entry contains information for
>> problematic file. This is how to use i_pos information.
>>
>> FWIW, in this error case, the cluster chain in FAT table which is
>> pointed by that entry, it has invalid cluster value.
>>
>> Thanks.
>
> If you would verify my math for me, I would appreciate it.
>
> In this case, my logical block size is 4096, because byte 13 of the 8Gb 
> file system is 8, and I take that to be 8 * 512, which is 4096. So:
>
> block_number = 523791 / (4096 / 32) = 4092
> offset = 523791 % (4096 / 32) = 15  // I assume you meant modulo in your 
> original post, and not binary AND.

Whoops, you are right. (I forgot "-1")

> So if the block_number is 4092, I would multiply that by 8 (sectors per 
> logical block) to get the sector number:
> 32736

Right.

> Does the error indicate that sector contains the corrupted data?

No.

> Or is it the sector that contains the information that points to the
> corrupted data?

Right.

The i_pos is pointing a directory entry (include/linux/msdos_fs.h:
struct msdos_dir_entry).

And starthi (if FAT32) and start contain the pointer to next cluster
number. That message was outputted when walking in cluster chain.

If you want to see actual corrupted data, you can check the cluster
chain by pointing from that directory entry.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2011-12-01 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 22:33 VFAT i_pos value Kai Meyer
2011-11-30 23:22 ` Abhijit Hoskeri
2011-12-01 14:38 ` OGAWA Hirofumi
2011-12-01 16:38   ` Kai Meyer
2011-12-01 19:20     ` OGAWA Hirofumi [this message]
2011-12-01 20:46       ` Kai Meyer
2011-12-03  6:20         ` OGAWA Hirofumi
2011-12-03  6:23           ` OGAWA Hirofumi
2011-12-08 21:35             ` Kai Meyer
2011-12-09 11:01               ` 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=871usoxfnb.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.