New answers tagged kernel
You can't modify /proc/partitions directly (or any other file inside /proc). These files are automagically generated by the kernel whenever someone opens them. However, reading from a different (manually) created file should suffice, as already pointed out by others. Additionally, you shouldn't put the string /proc/partitions "more then 722 times" in your ...
The kernel timeout only applies if the connection is orphaned. If the connection is still attached to a socket, the program that owns that socket is responsible for timing out the shutdown of the connection. Likely it has called shutdown and is waiting for the connection to shut down cleanly. The application can wait as long as it likes for the shutdown to ...
Empty output from fdisk -l typically means you do not have the necessary permissions to access the partition table. Check whether you are really working as root and whether SELinux or some other mechanism for limiting access is active.
It could mean that your partition table is gpt, which is not supported in older versions of fdisk. If you provide the output we could see more.
You can create your own script to call the following command frequently: gcloud compute instances get-serial-port-output INSTANCE_NAME The serial port output will provide you with all the logs on your instance including the services that started as well.
shmmax and shmall are not allocations, they are control knobs in the kernel that allow you to control the maximum shared memory segment size and the number of shared memory pages. Quoting from the sysctl documentation: shmall: This parameter sets the total amount of shared memory pages that can be used system wide. Hence, SHMALL should always be at least ...
I recently went through this error in one of our Production clusters: Nov 11 14:56:41 xxx kernel: INFO: task xfsalloc/3:2393 blocked for more than 120 seconds. Nov 11 14:56:41 Xxxx kernel: Not tainted 2.6.32-504.8.1.el6.x86_64 #1 Nov 11 14:56:41 xxx: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. .. On ...
Red Hat kernels are quite different from vanilla ones. Even tunables (eg: sysctl) have significant different default values. I strongly suggest you to stay with RH kernels unless absolutely necessary. Please at least consider using ELRepo kernels, if you really need a more update kernels. Anyway, this question should be issued in the linux kernel mailing ...
your kernel panics because it is not a a PXE compatible kernel/initrd set. If I were you I would not reinvent the wheel; take a proved PXE compatible distro and customize initrd to your needs and add the required squashfs. For a big list of PXE compatible distros and their corresponding parameters see Serva
Top 50 recent answers are included