Search

kernel sles:~ # grep crash /proc/cmdline root=/dev/disk/by-uuid/10a83ffe-5a9f-48a2-b8cb-551c2cc6b42d resume=/dev/sda3 splash=silent text showopts crashkernel=128 sles:~ # /etc/init.d/boot.kdump status ... If the Linux server crashes, not only do you need to restore operations, you also need to analyze the problem. What happened? Where is the root of the error? What preventive measures are necessary

@maibutter:~# df -h / Filesystem Size Used Avail Use% Mounted on /dev/m/maibutter-root 60G 4.8G 47G 10% / The number of replicas of a file on RAID 1 and of a stripe on RAID 10 is always two, regardless

map for a setup consisting of six OSDs (i.e., individual storage devices in servers) distributed over three racks: crushtool --num_osds 6 -o crush.example.map --build host straw 1 rack straw 2 root

42 spawn $env(SHELL) 43 match_max 100000 44 expect -exact "]0;khess@trapper: ~khess@trapper:~\$ " 45 send -- "ssh aspen\r" 46 expect -exact "ssh aspen\r 47 khess@aspen's password: " 48 send