Forum Discussion
I spun up a Vanilla Ubuntu 20.04 server, with same SNMPD version (just latest apt update), I could not get this behaviour triggered before I started adding in more disks:
I wasn't able to trigger this in service restart for this VM for some reason, only reboots on this one, some of the reboots also yielded the same indexes, so it's not always that this happens.
*** Added more disks ***
1 => Physical memory
10 => Swap space
3 => Virtual memory
35 => /run
36 => /
38 => /dev/shm
39 => /run/lock
40 => /sys/fs/cgroup
6 => Memory buffers
7 => Cached memory
70 => /run/snapd/ns
72 => /run/user/1000
73 => /data/backups/disk-1
74 => /data/backups/disk-2
75 => /data/backups/disk-3
76 => /data/backups/disk-4
77 => /data/backups/disk-5
8 => Shared memory
*** REBOOT ***
1 => Physical memory
10 => Swap space
3 => Virtual memory
35 => /run
36 => /
38 => /dev/shm
39 => /run/lock
40 => /sys/fs/cgroup
6 => Memory buffers
65 => /data/backups/disk-5
66 => /data/backups/disk-2
67 => /data/backups/disk-3
68 => /data/backups/disk-1
69 => /data/backups/disk-4
7 => Cached memory
75 => /run/snapd/ns
77 => /run/user/1000
8 => Shared memory
*** REBOOT ***
1 => Physical memory
10 => Swap space
3 => Virtual memory
35 => /run
36 => /
38 => /dev/shm
39 => /run/lock
40 => /sys/fs/cgroup
6 => Memory buffers
65 => /data/backups/disk-4
67 => /data/backups/disk-3
68 => /data/backups/disk-1
7 => Cached memory
72 => /data/backups/disk-5
73 => /data/backups/disk-2
75 => /run/snapd/ns
77 => /run/user/1000
8 => Shared memory
Related Content
- 10 months ago
- 4 days ago
- 2 months ago