Zvlastni (jednoduchy) problem s ext3
Dalibor Straka
dast na panelnet.cz
Pondělí Září 24 20:53:07 CEST 2007
Ahoj,
mam dva stroje jeden amd64 a druhy amd32. Na obou bezi debian stable.
Udelal jsem patititon ext3 a v ni mam adresar s (bohuzel) 2 miliony
souboru. Stejne operace "rm adresar/ -rf", "chown root:root adr/ -R"
trvaji na jednom stroji s amd64 nekolik hodin a na amd32 minutu.
Posilam vystup "tune2fs -l /dev/md4", lisi se take dir_index, ale
to jsou jen nejake bstromy, ktere by naopak meli urychlovat ;).
Kdyz postvu strace na tentyz proces rm nebo chown na obou strojich
na amd64 bezi jednotky za sekundu, na druhem stovky-tisice/s.
Nedomnivam se, ze by zpomaloval procesor, ale spise nejaky parametr
ext3 nebo nejake jine kontroly systemu. Hdparm -t dava na amd64
66 MB/sec na amd32 51 MB/sec. Na obou je sw raid1 (md) nad ide/sata
disky.
amd64(dualcore opteron):
tune2fs 1.40-WIP (14-Nov-2006)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 384a6534-9ae5-4f06-b81d-57d4da441fb5
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal resize_inode dir_index filetype
needs_recovery sparse_super large_file
Filesystem flags: signed directory hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 13434880
Block count: 26854624
Reserved block count: 268546
Free blocks: 24784530
Free inodes: 13373811
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1017
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Tue Jul 31 18:58:29 2007
Last mount time: Wed Sep 12 20:49:47 2007
Last write time: Wed Sep 12 20:49:47 2007
Mount count: 17
Maximum mount count: 21
Last checked: Tue Jul 31 18:58:29 2007
Check interval: 15552000 (6 months)
Next check after: Sun Jan 27 17:58:29 2008
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: a80ed3ed-df64-4659-a75f-647a2dd909a3
Journal backup: inode blocks
amd32 (Sempron):
tune2fs 1.37 (21-Mar-2005)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 24eb6230-6416-4f3b-b784-abdc502de7a0
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery
sparse_super large_file
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 7585792
Block count: 15162560
Reserved block count: 758128
Free blocks: 3112550
Free inodes: 4795638
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
Filesystem created: Fri Feb 11 03:12:00 2005
Last mount time: Sat Sep 22 15:03:48 2007
Last write time: Sat Sep 22 15:03:48 2007
Mount count: 3
Maximum mount count: 39
Last checked: Sun May 20 16:10:38 2007
Check interval: 15552000 (6 months)
Next check after: Fri Nov 16 15:10:38 2007
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: 4d790370-67e7-4dc2-86b3-1a4dd5c2be4b
Journal backup: inode blocks
Nenapada vas neco?
-- Zcela zeleny Dalibor
P.S. Mam jedno jedine podezreni (par debilnich procesu prave nad tim
adresarem neco dela, lsof ukaze par viniku, ale jejich intenzitu moc
neposoudim).
Další informace o konferenci Linux