On 28/09/2007, Szabolcs Szakacsits <[EMAIL PROTECTED]> wrote: > > Hi, > > On Fri, 28 Sep 2007, Jean-Pierre ANDRE wrote: > > > I probably can insert $Mapping into $Extend. I would > > however want to know more about the rationale.
The rationale is consistency with what Windows (2000+) does - putting all new special metadata ($ObjId, $Quota, $Reparse, $UsnJrnl) in $Extend. Windows hide MFT records <24. If you put a new file in the root and not assign it a reserved record number, Windows will show it (and ntfs-3g should do too). You mustn't assign a reserved number or the MFT won't be able to grow when it gets fragmented. $Extend is 11, which is <24, so it is hidden. > > This could have consequences on external tools : how > > would the file be saved/restored by plain tar ? $Extend is hidden. The user mapping will be in the same status as quota, reparse points, transactions, etc. It tar will be NTFS-aware, it will be able to backup it. If not, you can enable a mounting option to show special files. > > how would a user (acting as root) create or update it ? vim /mnt/xxx/\$Extend/\$Mapping You can put any file you want to hide in $Extend even while you are in Windows. Once you cd to $Extend, you can "dir" (or "ls") and edit files normally. > > How is $Extend processed by standard Windows tools, for > > instance, would chkdsk not delete it during a clean up ? It won't. > However I suggest renaming it to $UserMapping because $Mapping > is general and could mean anything. Seconded. -- Yuval Fledel ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
