> -----Original Message----- > From: [email protected] <drbd-user- > [email protected]> On Behalf Of Roland Kammerer > Sent: Thursday, April 28, 2022 9:47 AM > To: [email protected] > Subject: Re: [DRBD-user] Adding a Physical Disk to a Storage Pool > > On Thu, Apr 28, 2022 at 02:41:53PM +0000, Eric Robinson wrote: > > There are about 200 resources between the two nodes. 'systemctl > > restart linstor-satellite' does not touch the running resources or > > disrupt service, right? > > There are no interruptions. That is the lovely part when control and data > plane are separated. >
Turns out there was no need. I added a small resource as a test and the storage pool numbers now show correctly. You were right, thanks! This does raise a related question, though. I only recently read the part of the Linstor User Guide where it talks about confining failure domains by creating one storage pool for each backend device (section 1.10.1). I wish I had known that sooner. When we created our volume groups, we did it like this... # vgcreate vg0 /dev/nvme0n1 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1 /dev/nvme5n1 It's all one big volume group and we let Linstor provision resources wherever it wants. What is the effect If one NVME drive fails? Do all resources on the node go diskless, or just resources that happen to live entirely on the failed drive? > Regards, rck > _______________________________________________ > Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list drbd- > [email protected] https://lists.linbit.com/mailman/listinfo/drbd-user Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. _______________________________________________ Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list [email protected] https://lists.linbit.com/mailman/listinfo/drbd-user
