Portál AbcLinuxu, 12. května 2025 13:32
dv -vh vypada nasledovne:
Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/VolGroup00-LogVol01 69418416 2316492 63518744 4% / /dev/mapper/VolGroup00-LogVol05 247967484 3165612 232002692 2% /usr0 /dev/mapper/VolGroup00-LogVol06 299008360 195552 283379080 1% /usr1 /dev/mapper/VolGroup00-LogVol03 29741864 197976 28008708 1% /tmp /dev/mapper/VolGroup00-LogVol04 49580256 266912 46754164 1% /var /dev/mapper/VolGroup00-LogVol02 247967484 3265908 231902396 2% /data /dev/md0 497765 23734 448332 6% /boot tmpfs 4012900 0 4012900 0% /dev/shm
Server nedela nic, ale presto je load average 0.2. To by nebylo nic tak strasneho, ale presto mam obavy, zda se nejedna o nejakou chybu. Prikaz 'top -i -d 1' ukazuje pouze 3 procesy (top, md1_raid1, kjournald). Ten md1_raid1 proces vyskoci kazdych 3-10 vterin, ma sice nasbirano za 3 dny 69 minut CPU casu, ale to je myslim zpusobeno synchronizaci kolem 4. hodiny rano, pres den se ta hodnota TIME (v prikazu ps) meni o par vterin za hodinu. Otazka: je to normalni, bezny stav u raidu?
sudo stap - <<EOF probe syscall.vfork.return { return_trace(name, $return) } probe syscall.fork.return { return_trace(name, $return) } probe syscall.clone.return { return_trace(name, $return) } function return_trace(name, retval) { printf("%s: %d -> %d\n", name, pid(), retval); } probe syscall.execve { printf("%s: %d %s\n", name, pid(), args); } EOFPro použití stap budeš potřebovat nainstalovat kernel debug symboly. Vypíše to něco jako
execve: 22761 "ls" "--color=tty" clone: 22638 -> 22762 clone: 22649 -> 22763 clone: 22652 -> 22764 clone: 22698 -> 22765 clone: 22713 -> 22766 clone: 22740 -> 22767 clone: 22650 -> 22768 clone: 21838 -> 22769 clone: 21838 -> 22770 clone: 22752 -> 22771 execve: 22771 "ip" "a" clone: 21838 -> 22772 clone: 22752 -> 22773 execve: 22773 "ls" "--color=tty" clone: 21838 -> 22774 clone: 22752 -> 22775 execve: 22775 "ps" clone: 21838 -> 22776 ^Cclone: 21838 -> 22777
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.