In message <[EMAIL PROTECTED]>,Chaskiel M Grundman writes: >--==========E0A3C7D627E180487321========== >I'm not claiming there isn't a problem. I'm claiming that whatever problem=20 >exists is not preallocs that are not being discarded because of the=20 >truncate optimization.
dont know. the ext2 behavior's is rather strange then. looking at my cache, i see things like: 8 -rw------- 1 root root 2048 Apr 15 22:27 V6123 8 -rw------- 1 root root 2048 Apr 15 22:27 V6125 8 -rw------- 1 root root 2048 Apr 15 22:27 V6126 8 -rw------- 1 root root 2048 Apr 15 22:27 V6129 8 -rw------- 1 root root 2048 Apr 15 22:27 V6131 8 -rw------- 1 root root 4096 Apr 15 22:25 V4506 8 -rw------- 1 root root 4096 Apr 15 22:25 V4967 8 -rw------- 1 root root 4096 Apr 15 22:25 V5472 8 -rw------- 1 root root 4096 Apr 15 22:25 V5473 8 blocks to store 2048 bytes? normally i would just say its the filesystem trying to helpful, but creating a similar file with dd, shows # dd if=/dev/zero bs=2048 of=/cache/dd.out count=1 1+0 records in 1+0 records out # ls -ls /cache/dd.out 2 -rw-r--r-- 1 root root 2048 Apr 15 22:33 /cache/dd.out >afs holds one file open: the CacheItems file (on bsd's, it holds two files=20 >open: the CacheItems file and the VolumeItems file). That's it. other calls = you learn something new every day. _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
