> Cred ca foarte putin. > Gindeste-te ca aceste informatii sint cache-uite in RAM. > Probabil dureaza citeva secunde. > > Pentru poster-ul original: > Ma ingrijoreaza mai mult cit dureaza un ls in acel director. > Ce zice "time ls -lR /dir"? > Dar "tune2fs -l /dev/sd?"?
# time ls -lR blabla > /dev/null real 0m1.146s user 0m0.670s sys 0m0.480s s-au inmultit si fisierele: # ls -lR blabla | wc -l 53578 # tune2fs -l /dev/sda7 tune2fs 1.26 (3-Feb-2002) Filesystem volume name: /usr Last mounted on: <not available> Filesystem UUID: 0be6e684-31a5-11d9-91c6-dab1b2ec6936 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super large_file Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 5537792 Block count: 11062752 Reserved block count: 553137 Free blocks: 8392810 Free inodes: 5368462 First block: 0 Block size: 4096 Fragment size: 4096 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16384 Inode blocks per group: 512 Last mount time: Tue May 3 13:27:43 2005 Last write time: Tue May 3 13:27:43 2005 Mount count: 9 Maximum mount count: -1 Last checked: Mon Nov 8 17:41:32 2004 Check interval: 0 (<none>) Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal UUID: <none> Journal inode: 8 Journal device: 0x0000 First orphan inode: 0 --- Detalii despre listele noastre de mail: http://www.lug.ro/
