<P> Other bookkeeping information is typically associated with each file within a file system . The length of the data contained in a file may be stored as the number of blocks allocated for the file or as a byte count . The time that the file was last modified may be stored as the file's timestamp . File systems might store the file creation time, the time it was last accessed, the time the file's metadata was changed, or the time the file was last backed up . Other information can include the file's device type (e.g. block, character, socket, subdirectory, etc .), its owner user ID and group ID, its access permissions and other file attributes (e.g. whether the file is read - only, executable, etc .). </P> <P> A file system stores all the metadata associated with the file--including the file name, the length of the contents of a file, and the location of the file in the folder hierarchy--separate from the contents of the file . </P> <P> Most file systems store the names of all the files in one directory in one place--the directory table for that directory--which is often stored like any other file . Many file systems put only some of the metadata for a file in the directory table, and the rest of the metadata for that file in a completely separate structure, such as the inode . </P> <P> Most file systems also store metadata not associated with any one particular file . Such metadata includes information about unused regions--free space bitmap, block availability map--and information about bad sectors . Often such information about an allocation group is stored inside the allocation group itself . </P>

What is one more example of limitations on file names in windows