Messages in this thread | | | Subject | Re: ext2 corruption? | Date | Sun, 10 Jan 1999 17:35:41 EST | From | Kev <> |
| |
> Can anyone explain how is this possible?
sure
> -rw------- 1 chuka etf 100664896 Apr 26 1996 attributes > -rw------- 1 chuka etf 67110035 Nov 6 1997 filter > -rw------- 1 chuka etf 67108951 Apr 26 1996 headers > -rw------- 1 chuka etf 420 May 28 1998 newsgroups > -rw------- 1 chuka etf 67108941 Apr 26 1996 posted > -rw------- 1 chuka etf 7430 May 28 1998 tinrc > galeb-Sat09-12:38pm/users/etf/chuka/.tin# du -sk > 17 .
du counts the actual number of disk blocks in use. Presumably, "attributes," "filter," "headers," and "posted" are files with holes in them; the software that created them wrote one block near the end of the file, and maybe some near the middle; because no other blocks were written, the filesystem didn't feel the need to allocate them. If the application asks for a chunk it hasn't written to, the filesystem will simply return a buffer full of zeros; when the application finally does write some data there, then the filesystem will allocate the blocks to that file. -- Kevin L. Mitchell <klmitch@mit.edu> ------------------------- -. .---- --.. ..- -..- -------------------------- http://web.mit.edu/klmitch/www/ (PGP keys availiable from here) RSA AE87D37D/1024: DE EA 1E 99 3F 2B F9 23 A0 D8 05 E0 6F BA B9 D2 DSS ED0DB34E/1024: D9BF 0E74 FDCB 43F5 C597 878F 9455 EC24 ED0D B34E DH 2A2C31D4/2048: 1A77 4BA5 9E32 14AE 87DA 9FEC 7106 FC62 2A2C 31D4
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |