in theory, can't you just use the stat structure for the stat/fstat functions? also in theory, shouldn't this be reported by st_blksize/st_blocks ? if not, i'm sure another one could be added in this structure and then worked into the C++ API. it shouldn't really be this big of a deal. my suggestion st_attrblksize & st_attrblocks. sure you should have the ability to see the total size used somewhere, but it's not really user friendly and can cause some confusion based on block sizes and such. if a user sees this and sees his file takes up 8192 bytes on the bfs partition then when goes to burn a cd and it only takes up 6144 bytes on a iso9660. or goes to copy it to a linux or dos partition with different block sizes he may be lead to think that the file is bad because a different size shows up. now i'm sure people have meant "show it in addition to" used data size, which is fine. i just personally feel it's something that should be hidden in like a file info window or something under an advanced tab or something. my 2 cents, soco