Hi Mike,
On 24-Oct-99, Mike Roark wrote to Murray Lesser:
MR> Friday October 22 1999 22:03, Murray Lesser wrote to Mike Roark:
MR>>> That 47 byte file would take up a 32k cluster on a 1 gig fat
>>> partition. Notice it only takes 512 bytes of space. I just gained
>>> 31k of space for something else.
ML>> I don't know what program you were using to produce your
ML>> "directory" display, but a one-byte file under HPFS takes up at
ML>> least 1 KB of disk space (one sector for the file itself and a
ML>> minimum of one sector for its Fnode). There is only one sector
ML>> used for the Fnode, irrespective of the size of the file, unless
ML>> the Extended Attributes portion of the Fnode takes up more room
ML>> than is available in that sector.
MR> I'm sure it does. As for what made the directory. It was a
MR> straight 'dir' command using 4dos as the command processor. I just
MR> tried it with the OS/2 cmd.exe, and it says it uses 47 bytes.
MR> Nothing I have short of DFsee shows anything about the fnode. But
MR> I do have a question. Isn't the fnode already allocated in the
MR> HPFS section of the drive? I hope I'm clear about what I'm asking.
MR> I mean the part that is allocated before any files are put on the
MR> drive
The minimum allocation for a file is 1024 bytes or 2 clusters, one for
the file and one for EAs - what Murray called the FNODE. Thereafter a
file is extended by by 1 cluster for file data or EAs as required,
however the maximum EA size that OS/2 supports is 64k. When a REXX
script is run the tokenised version is stored in the EAs if it is less
than 64k, this means that a REXX script does not normally have to be
tokenised each time it is run.
George
--- Terminate 5.00/Pro
633/260
2501/209
* Origin: A country point under OS/2 (2:257/609.6)
|