similar to: Clustered Samba and OCFS2

On 03/07/16 21:47, Volker Lendecke wrote: > On Sun, Jul 03, 2016 at 08:42:36PM +0100, Alex Crow wrote: >> I've only put the "private dir" onto MooseFS, as instructed in the CTDB >> docs. > Can you quote these docs, so that we can correct them? Here, under the lustre section. I applied the same config at it's a similar FS (ie distributed with a central metadata

Am 02.02.2015 um 18:02 schrieb Lars Hanke: > My file servers join AD, but are not the DC itself. Does it mean that > CTDB is an option or not? Yes. > A common FQDN would mean I simply add two A records for e.g. > smb.samdom.example.com, resolving to each IP of the file servers? Can it > be as simple as that? A first start and introduction to CTDB you will find in the Wiki:

Hello everyone, this is my first thread I watched the CTDB solution and allows to build a NAS Cluster with load balancing and failover https://wiki.samba.org/index.php/CTDB_Setup But still does not work as Active Directory Domain Controler. The question is: if i build to setup an AD DC in an single server over a cluster system files( example GPFS or Lustre ) this setup can work with a high

On 03/11/16 19:37, Volker Lendecke wrote: > On Thu, Nov 03, 2016 at 07:11:12PM +0000, Alex Crow via samba wrote: >> >> On 03/11/16 14:28, Ralph Böhme wrote: >>>> Ah, my smb.conf is missing the "ctdb socket" parameter. According to "man >>>> smb.conf" this should be set, but I don't remember seeing it on the wiki >>>> pages.

Hello, I try to set up a clustered samba server (on Novell SLES11SP2) based upon CTDB and NFS. My problem is that I do not yet understand the structure of the setup when using NFS. I followed the documentation in http://wiki.samba.org/index.php/CTDB_Setup#Setting_up_CTDB_for_clustered_NFS As far as I understand this documentation, it should be possible to set up a samba cluster say having 3

I have a couple lines like: part / --ondisk=sda --fstype ext3 --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /home --ondisk=sda --fstype ext3 --size=1 --asprimary --grow in my kickstart file. Is there a way to have 1 kickstart file that works for hda and sda both??? So I would like to have 1 kickstart file that works for either a hda

Hi , I have set up a 2-node CTDB cluster serving NFS and CIFS authenticating Windows and Linux users via Active Directory. The setup works fine, except only one server in the CTDB-cluster is able to join the AD domain at a given instance. If you manually add the other server into AD, the already connected server gets disconnected. There is no specific error message logged in /var/log/message or

Hello. A couple of years ago I installed two file-servers using kickstart. The server has two 1TB sata disks with two software raid1 partitions as follows: # cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdb4[1] sda4[0] 933448704 blocks [2/2] [UU] md0 : active raid1 sdb1[1] sda2[2](F) 40957568 blocks [2/1] [_U] Now the drives are starting to be failing and next week

-----BEGIN PGP SIGNED MESSAGE----- ******************************************************************** The contents of this email are intended exclusively for the addressee. If you are not the addressee you must not read use or disclose the email contents ; you should notify us immediately [ by clicking "Reply" ] and delete this email. Nationwide monitors e-mails to ensure its systems

Hello, I'm trying to do a kickstart install of centos5. I'm pulling it off a network server and i'm getting an error, in the parsing of the file. It refers to line 31, i'm not going to show the complete file, but here is the indicated line: raid swap --fstype swap --level=RAID1 raid.4 raid.7 and the raid lines: part raid.7 --size=512 --ondisk=hdb part raid.4 --size=512

This is what I have for configuring software raid on sata drives in my kickstart config <snip kickstart.cfg> clearpart --initlabel --all part swap --size=2048 --ondisk=sdb part swap --size=2048 --ondisk=sda part raid.01 --size=101 --ondisk=sda part raid.02 --size=101 --ondisk=sdb part raid.04 --size=1 --grow --ondisk=sdb part raid.03 --size=1 --grow --ondisk=sda raid / --fstype ext3

Greetings. There must be some minor changes to anaconda. I'm getting the error: "Cannot open repomd.xml file...." the file seems to be located in the repodata directory... I'm using the following .cf taken directly from the CentOS 4.4 install : install url --url ftp://centos.westmancom.com/5.0/os/i386/ #cdrom lang en_US.UTF-8 langsupport --default=en_US.UTF-8 en_US.UTF-8

Hi all, I still use the following kickstart partition scheme for C7 installations (via virt-install): Briefly, fixed size for /root and /boot, and the rest is filled up for /srv. The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work with Fedora29 (EL8). I get a "device is too small for new format" error. Any hints? part /RESCUE --fstype="ext4"

I have 2 questions dealing with 2 different kickstart files. 1) my kickstart sections for RAID disk setup and kickstart reports it cannot find sda. Why is that. sda is there and works. clearpart --all --initlabel part raid.01 --asprimary --bytes-per-inode=4096 --fstype="raid" --onpart=sda1 --size=20000 part swap --asprimary --bytes-per-inode=4096 --fstype="swap"

I was just wondering how (or indeed if) people use the %include directive in Kickstart configuration files when building systems via NFS. I've been trying to modularise our Kickstart files a little to make things more readable, having generic defaults and role specific stuff split out into separate configs. I've tried this configuration... [root at archive kickstart]# cat

On Thu, 2016-08-04 at 22:21 -0400, Jonathan Billings wrote: > Is it a BIOS boot, or are you using the UEFI firmware for booting? > Either way, you might need a small boot partition (not /boot) at the > beginning of the disk. /boot/efi formatted FAT16, circa 150 MB -- Regards, Paul. England, EU. England's place is in the European Union.

I am trying to add an efi partition to my working kickstart file. bootloader --driveorder=sda --append="rhgb quiet biosdevname=0 net.ifnames=0" clearpart --all --initlabel part / --ondisk=sda --fstype xfs --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /boot/efi --ondisk=sda --fstype efi --size=1000 --asprimary part /home --ondisk=sda

I am trying to install Centos 7 on a couple 4TB drives with software raid. In the Supermicro bios I set UEFI/BIOS boot mode to legacy. I am using the Centos 7 minimal install ISO flashed to a USB thumb drive. So I do custom drive layout something like this using sda and sdb. Create /boot as 512 MB XFS raid1 array. Create SWAP as 32 GB SWAP raid1 array. Create / on 3.xxx TB XFS raid1 array.

On 03/07/16 13:06, Volker Lendecke wrote: > On Fri, Jul 01, 2016 at 10:00:21AM +0100, Alex Crow wrote: >> We've had a strange issue after following the recommendations at >> https://wiki.samba.org/index.php/Ping_pong, particularly the part >> about mmap coherence. We are running CTDB/Samba over a MooseFS >> clustered FS, and we'd not done the ping-pong before.

Hi all, I stumbled over a curious thing. The Linux tools "df" and "du" aren't working correctly on an OCFS2 filesystem. "df" shows approx. twice the size as there is on the volume. Here how I found out about this issue: - same dir(a few files more in OCFS but the files are ca. 12 kB in size), first on XFS second on the OCFS volume # du -ms