VFAT i_pos value

OGAWA Hirofumi hirofumi at mail.parknet.co.jp
Fri Dec 9 06:01:43 EST 2011


Kai Meyer <kai at gnukai.com> writes:

> [root at dev1 sblsnap]# ./vfat_entry /dev/sblsnap0 523781
> block 4092, sector 32736, offset 5
> name      3~1     ZER
> attr      32
> lcase     0
> ctime_cs  100
> ctime     29092
> cdate     16264
> adate     16264
> starthi   4
> time      29092
> date      16264
> start     7427
> size      37748736
> next pos: 32736

Looks like sane entry.

> [root at dev1 sblsnap]# ./vfat_entry /dev/sblsnap0 32736
> block 255, sector 2040, offset 96
> name
> attr      0
> lcase     0
> ctime_cs  0
> ctime     0
> cdate     0
> adate     0
> starthi   0
> time      0
> date      0
> start     0
> size      0
> next pos: 2040
>
> Does that look like what would be causing my error? meaning, sector 2040 
> has bad data?

The next pos means the position of data cluster (i.e that entry is using
the cluster of this position to store data). You have to walk the
cluster position chain on FAT table, not directory entry.
-- 
OGAWA Hirofumi <hirofumi at mail.parknet.co.jp>



More information about the Kernelnewbies mailing list