similar to: Notes regarding PXE-booting from GlusterFS

Hello, I am trying to boot a node using initramfs.? (actually it is a little more complicated, I am booting the node using perceus and vnfs images). Anyway, when booting with a kernel and using initramfs.img, dracut is trying to to configure both Network NICs, the first one would be fine, but I don't want it to ven try to configure the 2nd one using dhcp. How can I stop dracut from

Hello Guys, i read the official red hat documentation of "How built pxe initramfs", but it does not work" the inluded version of initramfs is about 42MB, mine 13MB. This is again one of more failure of redhat documentation. That's why i ask here. In my despair tried a very hard version: dracut -v -f -m "nfs network base" --add-drivers "nfsv4 (find

+gluster-users Another guideline we can provide is to disable all performance xlators for workloads requiring strict metadata consistency (even for non gluster-block usecases like native fuse mount etc). Note that we might still can have few perf xlators turned on. But, that will require some experimentation. The safest and easiest would be to turn off following xlators: * performance.read-ahead

Hi 1. Is it possible to load an initrd from initramfs ? How would you do this if the initramfs is being loaded dynamically in the kernel (ie having the initramfs as initrd ) Because in this case, you will say root = /dev/initrd and specify 'initrd' as your 'initramfs source file' How will you specify the second initrd source? Thanks Rachita.

CentOS Errata and Security Advisory 2018:2892 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2018:2892 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 131786837b080aba5234623fbd2277efe4873585ee2628b5e65bb26e99425c65 glusterfs-3.12.2-18.el6.i686.rpm

Hello, I'm trying to switch from initrd to initramfs for diskless workstations, but I have some problems. I just made a symlink /init -> /sbin/init and gzipped cpio file, then tried to compile image in the kernel or use image with initrd option. In the first case I'm getting "corrupted or invalid kernel" immediately. In the second kernel and initrd can be downloaded

TODO: Fix selinux :P --- Makefile.am | 1 + ovirt-node.spec.in | 3 ++ scripts/ovirt | 3 ++ scripts/ovirt-managed-rsyslog | 72 +++++++++++++++++++++++++++++++++++++++++ 4 files changed, 79 insertions(+), 0 deletions(-) create mode 100755 scripts/ovirt-managed-rsyslog diff --git a/Makefile.am b/Makefile.am index 0374f07..5201a79 100644

Hi Team, I am trying to setup a samba CTDB cluster to export gluster volme as samba share. While CTDB cluster works well, I ran into an issue with creating subdirectories and also creating files/directories within subdictories when accessing the share from both linux and windows servers. Setup details : We have a three node cluster with nodes snode1, snode2 and snode3. I have a gluster

Hello, I've recently ran into a problem trying to boot over TFTP using pxelinux.0. On the console, I got the following message: Could not find ramdisk image: initramfs-3.10.0-123.13.2el7.x86_64 It took me a while to figure out that the file *could* be found but that the file permissions were set wrong and the file couldn't be read. At the protocol level (tcpdump), the server

Hi there. I had a quick look through the archives, and I spotted a similar issue being reported in October, but no resolution, unfortunately. "[syslinux] Syslinux 6.02 BIOS" I am booting in legacy (bios) mode on a gpt partition on my laptop. It's a HP ENVY dv7. CPU: Intel i7, BIOS: InsydeH2O version: F. 12 With syslinux 4.06, it boots flawlessly. With syslinux 6.01 and 6.02, the

On Sat, Nov 23, 2013 at 5:49 AM, Evert Vorster <evorster at gmail.com> wrote: > Hi there. > > I had a quick look through the archives, and I spotted a similar issue > being reported in October, but no resolution, unfortunately. > "[syslinux] Syslinux 6.02 BIOS" > > I am booting in legacy (bios) mode on a gpt partition on my laptop. > It's a HP ENVY dv7.

Hey, i'm using latest Syslinx 6.01 and try to get the linux kernel booted via tftp in EFI mode. My menu entry: LABEL rescue64 MENU LABEL ^1. 64-Bit Rescue-System - wheezy - 3.10.2 LINUX /rescue/dev-64/vmlinuz INITRD /rescue/dev-64/initramfs.cpio.gz APPEND ... If i select the entry i get: "Bad file number!". Over http it works like a charm. With the pxelinux.0 it works via

Hello Andreas, Andreas Gruenbacher wrote: > Hello, > > I've recently ran into a problem trying to boot over TFTP using > pxelinux.0. On the console, I got the following message: > > Could not find ramdisk image: initramfs-3.10.0-123.13.2el7.x86_64 > > It took me a while to figure out that the file *could* be found but that > the file permissions were set

>> Straight away the booting process looks different than with 4.06. >> The periods that were showing progress in loading the initramfs now >> does not increase as the initramfs is loaded. So, only three periods >> after each initramfs. > > That happened in version 5.00. Good to know that this is expected behavior. However, some sort of indication that the initramfs

Hi Team, I am trying to setup a samba CTDB cluster to export gluster volme as samba share. While CTDB cluster works well, I ran into an issue with creating subdirectories and also creating files/directories within subdictories when accessing the share from both linux and windows servers. Setup details : We have a three node cluster with nodes snode1, snode2 and snode3. I have a

Hi, Greetings of the day, Our configuration is like: We have installed both glusterFS server and GlusterFS client on node1 as well as node2. We have mounted node1 volume to both nodes. Our use case is : >From glusterFS node 1, we have to take an exclusive lock and open a file (which is a shared file between both the nodes) and we should write/read in that file. >From glusterFS node 2, we

Hello everyone, I have a problem with setting up a diskless system on CentOS. Currently I have successfully set up a small cluster of diskless clients following the following available HowTos: http://wiki.centos.org/HowTos/DisklessClients https://coda.jlab.org/wiki/index.php/CentOS6_Linux_Diskless_Setup The client system is CentOS 5.10 and the system is read-only. It has been working fine for a

CentOS Errata and BugFix Advisory 2016:C001 Upstream details at : https://bugs.centos.org/view.php?id=10538 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 96963d839797a7601ef6a4922c94e7ef82b42fcb70533f9a31c43adceee2fb19 glusterfs-3.7.1-16.0.1.el7.centos.x86_64.rpm

CentOS Errata and Bugfix Advisory 2018:2444 Upstream details at : https://access.redhat.com/errata/RHBA-2018:2444 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 59f5c080694bdf3606c516b206dd35cc1c3cb3fd7885aafe6bf31713fab2229e glusterfs-3.8.4-54.15.el7.centos.x86_64.rpm

rhbz#:51422 --- ovirt-node.spec.in | 149 +++++++++------------------------------------------ 1 files changed, 27 insertions(+), 122 deletions(-) diff --git a/ovirt-node.spec.in b/ovirt-node.spec.in index 3138011..b4e660d 100644 --- a/ovirt-node.spec.in +++ b/ovirt-node.spec.in @@ -43,76 +43,23 @@ Requires: nc Requires: grub Requires: /usr/sbin/crond Requires: anyterm