forked from CameronLonsdale/bmap
-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathNOTES
More file actions
20 lines (15 loc) · 900 Bytes
/
Copy pathNOTES
File metadata and controls
20 lines (15 loc) · 900 Bytes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
OBSERVATIONS about 'bmap' in action.
(This document has been largely superceded by application notes contained in
the bmap documentation)
* ext2 reports file blockcounts overzealously. stat() returns a blockcount
measured in sectors on the author's system. However, stat claims that the
the stat(2) manpage suggests that this blockcount may not be in the same
units reported by bmap system call, but instead may be expressed in
'optimal' transfer units. The author has trouble buying an optimal transfer
blocksize of 512 bytes.
The kernel correctly reports the bmap blocksize with ioctl(FIGETBSZ,...).
* stat _seems_ to report extra blocks for ext2 files over 12k. Does stat
get caught up in the size of metadata affiliated with a file?
UPDATE: Walter Hofmann reported that indirect blocks count against the
stat-reported size in blocks.
* holes can be tricky to deal with