|
From: SourceForge.net <no...@so...> - 2005-09-05 21:55:11
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3326211 By: uvman When an attribute grows large, there are 3 ways to deal with it. 1) Make it non-resident. (you already know that one) 2) When all the attributes that can be non-resident are indeed non-resident, an attribute list is allocated. Basically, it will make the MFT record (except the 0x10 attribute) non-resident. All attributes >0x20 are moved outside the MFT record into the payload of the attribute list. 3) When the attribute list is so fragmented that it can't be stored in one MFT record, an extension MFT record is allocated. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
