inding's questions

You need to install it in an environment where there is no network.

So I was installing via RPM.

In the meantime, a crash occurred and the installation could not proceed.

I found yum install --downloadonly while searching for various things.

It is said that after downloading rpm from a network where it is possible, you can install it where the network is not possible.

If so, I have a question for you.

1. Should the OS version of the download location be the same?
2. Does it matter that the rpm's installed in the download and install places are different?
3. How does this feature's dependency resolution work? (If you don't know this, it's okay not to answer)

I need your help as I am new to rpm installation.

Thank you in advance.

I need to install DRBD in a server without internet. (redhat 7.x)

It's a sad place where you can't use yum.....

You have to compile using the source.

So, I have the following questions:

1. Is it possible to install all the currently uploaded sources?
2. Do I need to install all 3 of DRBD 9.x Linux Kernel Driver / DRBD 9.0.x Linux Kernel Driver / DRBD Utilities ? If not, which one should I install?
3. What other libraries do I need to install?
4. If anyone has installed DRBD9 by source compile on RHEL 7.x, can you tell me how?

If you can answer the above questions, I would be very grateful.

thank you in advance

Now I am using WinDRBD on Windows Server 2019

So far, I have checked whether DRBD is running with the command below.

drbdadm status foo

However, I need to write some code in the batch file to check if DRBD is working.

I looked at the process in the windows task manager. However, I did not find the process.

I may have missed it. What is the process name of WinDRBD?

I have a question.

Currently, this OS is Windows Server 2019. The volume configuration is Raid-5. The two servers are connected by a heartbeat network Both nodes were mirrored using WinDRBD. Both nodes have the same configuration. I left unformatted G: and set D: to be visible to the primary node.

my resource are below

include "global_common.conf";

resource "foo" {
    protocol    A;

    net {
        use-rle no;
    }
    on node1 {
        address     XXX.XXX.XXX.XXX:7600;
        node-id 1;
        volume 1 {
            disk        "G:";
            device      minor 1;
            meta-disk   internal;
        }
    }
    on node2 {
        address     XXX.XXX.XXX.XXX:7600;
        node-id 2;
        volume 1 {
            disk            "G:";
            device      minor 1;
            meta-disk   internal;
        }
    }
}

Both nodes worked normally. The tests were completed by switching roles. ( primary → secondary / secondary → primary )

However, the problem occurred after booting.

After booting, the status appears as below. (both nodes)

foo role:Secondary
  volume:1 disk:Diskless
  node2 connection:StandAlone

I thought and searched a lot, but couldn't find an answer.

There were a few things I was suspicious about.

I wonder if it's because I tried before the G: letter was assigned to the drive. If my thinking is correct, is there a workaround?

If it is now my opinion, but the above problem continues to occur, what is the cause?

Once it was solved in the following way. But I want to find the cause and fix it accurately.

drbdadm down foo
drbdadm up foo

Thanks in advance for your help.