|
From: Anton A. <ai...@ca...> - 2001-03-15 23:21:44
|
At 15:47 15/03/2001, Michael N. Filippov wrote:
>/*
> * Attribute: Index allocation (0xa0).
> *
> * Always non-resident (doesn't make sense to be resident anyway!).
> *
> * This is an array of index blocks. Each index block starts with an
> * INDEX_BLOCK_HEADER structure containing an index header, followed by a
> * sequence of index entries (INDEX_ENTRY structures), as described by the
> * index header.
> */
>typedef struct {
> NTFS_RECORD_HEADER ntfs; /* Magic is "INDX". */
>
>//
>// shouldnt log_sequence_number be here ?
>//
Yes, it should. In fact, it is there in CVS. I fixed it only after
releasing 0.0.1. It will be right in 0.0.2...
> __u64 index_block_vcn; /* Virtual cluster number of this
> index block. */
> INDEX_HEADER index; /* Index header describing the
> following index entries. */
>} __attribute__ ((__packed__)) INDEX_BLOCK_HEADER;
>
>Btw: Why not to place log_sequence_number (lsn) into NTFS_RECORD_HEADER.
Gary Nebett's book does actually put it there, but I don't think it belongs
there, as it can mean different things depending on where it is, at least
this is the impression I have ATM; If you look at logfile.h, the lsn
following the NTFS_RECORD{_HEADER} struct is named chkdsk_lsn. I am not
quite sure what this is but it is only used when the magic of the
NTFS_RECORD is "CHKD" instead of "RSTR", so has something to do with chkdsk
but I haven't investigated this any further.
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://sourceforge.net/projects/linux-ntfs/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
|
