Dnia Thu, Mar 24, 2022 at 09:56:25AM -0400, Nick Holland napisał(a): > On 3/24/22 8:38 AM, Leo Unglaub wrote: > > Hey friends, > > > > i have a 500GB drive that is fully encrypted using a softraid with > > raidlevel C. It works perfectly. But now the drive is getting full and i > > have to grow it. This server is running in the Hetzner Cloud and > > resizing the drive is supported to 10TB. > > > > With an unencrypted partition this works well in OpenBSD. I can use > > disklabel and growfs to enlarge the drive, but that does not work with > > an encrypted partition. > > correct... you can growfs a FS within an encrypted partition, but can not > grow the encrypted partition. > > > Do you have any recommendations on what the best way forward is in this > > case? I tried adding a new 1TB drive and copying all the files over and > > just remounting it. But even with the super fast M2. SSD drives in there > > it took more than 3 days to finish. (lots of small files, its my email > > server) > > well, you might want to have a chat with your service provider. There's > nothing "super fast" about 500g in three days (though my VPS on my primary > web/mail server also brags about SSDs...and the slowest disk performance I > have seen in decades. I have a note-to-self in the .profile that a > sysupgrade takes 15 minutes to keep me from freaking out during upgrades. > Other systems I have with them have more expected performance. *shrug*) > > > Having my email server down for 3 days is not really a good option for > > obvious reasons. > > might be fun. :) > > though if you are worried about just your incoming mail, spinning up a > secondary MX and letting it spool your mail while your primary is down > would be an option. > > > I also tried doing an initial copy and then using rsync, but because > > dovecot (imap server from ports) uses a lot of hardlinks rsync is not > > working correctly even with the hard link option (bugs are described in > > the rsync man page) and openrsync does not support handling them. > > what? where? I'm not seeing what you are refering to here. > Also a quick web search isn't showing a problem, but I am seeing a lot > of people using rsync to back up dovecot maildir servers. (if totally > off-topic to OpenBSD, please advise me off-list) > > > Do you have any ideas what i can do in this case? > > Thanks and greetings > > well... like any HW migration, divide and conquer. > Move the static stuff first live, then move the changing stuff last. > > Move everything you can with rsync, then deal with your maildir separately. > I've used "imapsync" before on a 30,000 user e-mail system -- first run > took a day or more, final system-down cutover run took time, but we were > down only a few hours (this was over a decade ago, don't hold me to the > numbers). > > dovecot has a "dsync" tool. Haven't used it, but it would be worth a > look at, I think. > > Nick. > > > > Leo > > > >> OpenBSD 7.0 (GENERIC.MP) #5: Mon Jan 31 09:09:02 MST 2022 > >> > >> r...@syspatch-70-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > >> real mem = 4177379328 (3983MB) > >> avail mem = 4034740224 (3847MB) > >> random: good seed from bootblocks > >> mpath0 at root > >> scsibus0 at mpath0: 256 targets > >> mainbus0 at root > >> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5ad0 (10 entries) > >> bios0: vendor Hetzner version "20171111" date 11/11/2017 > >> bios0: Hetzner vServer > >> acpi0 at bios0: ACPI 1.0 > >> acpi0: sleep states S5 > >> acpi0: tables DSDT FACP APIC HPET > >> acpi0: wakeup devices > >> acpitimer0 at acpi0: 3579545 Hz, 24 bits > >> acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat > >> cpu0 at mainbus0: apid 0 (boot processor) > >> cpu0: Intel Xeon Processor (Skylake, IBRS), 2100.34 MHz, 06-55-04 > >> cpu0: > >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLWB,AVX512CD,AVX512BW,AVX512VL,PKU,MD_CLEAR,IBRS,IBPB,SSBD,ARAT,XSAVEOPT,XSAVEC,XGETBV1,MELTDOWN > >> cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > >> 64b/line 16-way L2 cache > >> cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > >> cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > >> cpu0: smt 0, core 0, package 0 > >> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > >> cpu0: apic clock running at 1000MHz > >> cpu1 at mainbus0: apid 1 (application processor) > >> cpu1: Intel Xeon Processor (Skylake, IBRS), 2100.07 MHz, 06-55-04 > >> cpu1: > >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLWB,AVX512CD,AVX512BW,AVX512VL,PKU,MD_CLEAR,IBRS,IBPB,SSBD,ARAT,XSAVEOPT,XSAVEC,XGETBV1,MELTDOWN > >> cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > >> 64b/line 16-way L2 cache > >> cpu1: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > >> cpu1: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > >> cpu1: smt 0, core 1, package 0 > >> ioapic0 at mainbus0: apid 0 pa 0xfec00000, version 11, 24 pins > >> acpihpet0 at acpi0: 100000000 Hz > >> acpiprt0 at acpi0: bus 0 (PCI0) > >> "ACPI0006" at acpi0 not configured > >> acpipci0 at acpi0 PCI0 > >> acpicmos0 at acpi0 > >> "PNP0A06" at acpi0 not configured > >> "PNP0A06" at acpi0 not configured > >> "PNP0A06" at acpi0 not configured > >> "QEMU0002" at acpi0 not configured > >> "ACPI0010" at acpi0 not configured > >> acpicpu0 at acpi0: C1(@1 halt!) > >> acpicpu1 at acpi0: C1(@1 halt!) > >> cpu0: using VERW MDS workaround > >> pvbus0 at mainbus0: KVM > >> pvclock0 at pvbus0 > >> pci0 at mainbus0 bus 0 > >> pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 > >> pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 > >> pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, > >> channel 0 wired to compatibility, channel 1 wired to compatibility > >> pciide0: channel 0 disabled (no drives) > >> atapiscsi0 at pciide0 channel 1 drive 0 > >> scsibus1 at atapiscsi0: 2 targets > >> cd0 at scsibus1 targ 0 lun 0: <QEMU, QEMU DVD-ROM, 2.5+> removable > >> cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 > >> piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 > >> int 9 > >> iic0 at piixpm0 > >> vga1 at pci0 dev 2 function 0 "Bochs VGA" rev 0x02 > >> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > >> wsdisplay0: screen 1-5 added (80x25, vt100 emulation) > >> virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00 > >> vio0 at virtio0: address 96:00:00:31:1f:b5 > >> virtio0: msix shared > >> virtio1 at pci0 dev 4 function 0 "Qumranet Virtio SCSI" rev 0x00 > >> vioscsi0 at virtio1: qsize 128 > >> scsibus2 at vioscsi0: 255 targets > >> sd0 at scsibus2 targ 0 lun 0: <QEMU, QEMU HARDDISK, 2.5+> > >> sd0: 39064MB, 512 bytes/sector, 80003072 sectors, thin > >> sd1 at scsibus2 targ 0 lun 2: <HC, Volume, 2.5+> serial.HC_Volume_17997513 > >> sd1: 1024000MB, 512 bytes/sector, 2097152000 sectors, thin > >> sd2 at scsibus2 targ 0 lun 1: <HC, Volume, 2.5+> serial.HC_Volume_10410864 > >> sd2: 512000MB, 512 bytes/sector, 1048576000 sectors, thin > >> virtio1: msix shared > >> virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Memory Balloon" rev 0x00 > >> viomb0 at virtio2 > >> virtio2: apic 0 int 10 > >> virtio3 at pci0 dev 6 function 0 "Qumranet Virtio Console" rev 0x00 > >> virtio3: no matching child driver; not configured > >> virtio4 at pci0 dev 7 function 0 "Qumranet Virtio SCSI" rev 0x00 > >> vioscsi1 at virtio4: qsize 128 > >> scsibus3 at vioscsi1: 255 targets > >> virtio4: msix shared > >> xhci0 at pci0 dev 8 function 0 vendor "Red Hat", unknown product 0x000d > >> rev 0x01: apic 0 int 11, xHCI 0.0 > >> usb0 at xhci0: USB revision 3.0 > >> uhub0 at usb0 configuration 1 interface 0 "Red Hat xHCI root hub" rev > >> 3.00/1.00 addr 1 > >> isa0 at pcib0 > >> isadma0 at isa0 > >> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 > >> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo > >> pckbc0 at isa0 port 0x60/5 irq 1 irq 12 > >> pckbd0 at pckbc0 (kbd slot) > >> wskbd0 at pckbd0: console keyboard, using wsdisplay0 > >> pms0 at pckbc0 (aux slot) > >> wsmouse0 at pms0 mux 0 > >> pcppi0 at isa0 port 0x61 > >> spkr0 at pcppi0 > >> dt: 445 probes > >> uhidev0 at uhub0 port 5 configuration 1 interface 0 "QEMU QEMU USB Tablet" > >> rev 2.00/0.00 addr 2 > >> uhidev0: iclass 3/0 > >> ums0 at uhidev0: 3 buttons, Z dir > >> wsmouse1 at ums0 mux 0 > >> vscsi0 at root > >> scsibus4 at vscsi0: 256 targets > >> softraid0 at root > >> scsibus5 at softraid0: 256 targets > >> sd3 at scsibus5 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006> > >> sd3: 39056MB, 512 bytes/sector, 79987043 sectors > >> softraid0: volume sd3 is roaming, it used to be sd2, updating metadata > >> root on sd3a (3aa1953775dc1966.a) swap on sd3b dump on sd3b > >> fd0 at fdc0 drive 1: density unknown > >> sd4 at scsibus5 targ 2 lun 0: <OPENBSD, SR CRYPTO, 006> > >> sd4: 511993MB, 512 bytes/sector, 1048561958 sectors > >> softraid0: volume sd4 is roaming, it used to be sd3, updating metadata > >> softraid0: roaming device sd1a -> sd2a > >> sd5 at scsibus5 targ 3 lun 0: <OPENBSD, SR CRYPTO, 006> > >> sd5: 1023994MB, 512 bytes/sector, 2097140573 sectors > > >
Dovecot has mechanism to do realtime master-master replication between two servers (probably uses dsync under the hood, but I didn't check). I'm using it to create high availability, in case one of my mail servers goes down second one works normally (I just need to point my imap/smtp clients to working one) https://wiki.dovecot.org/Replication -- Łukasz Moskała
