search for: remirror

...ed across both drives, so like 16k on the first disk, then > 16k on the 2nd then 16k back on the first, repeat (replace 16k with > whatever your raid stripe size is). > > if its a raid 1 mirror, then either disk by itself has the complete file > system on it, so you should be able to remirror the changed disk onto the > other drive. you MUST do that re-mirror because your two disks are no > longer identical, and reads will alternate between them, so some reads will > get new data and others will get old data, which will be highly chaotic. > > > > On Wed, Nov 4, 20...

My computer running CentOS 7 is configured to use BIOS RAID0 and has two identical SSDs which are also encrypted. I had a crash the other day and due to a bug in the operating system update, I am unable to boot the system in RAID mode since dracut does not recognize the disks in grub. After modifying the grub command line I am able to boot the system from one of the harddisks after entering the

...journaled so they can be played back when things resume. I'm open to other approaches, so far I've found very little in this category... I briefly considered using LVM mirroring over iscsi to the slave, but A) this is synchronous, B) recovery from a service interruption would require remirroring the whole volume. I've been reading about GFS but am somewhat confused as to its capabilities. The examples given on redhat's pages seem to involve shared storage (SAN or whatever) and distributed cluster access, I don't need any of that, just simple master->slave one way as...

...d across both drives, so like 16k on the first disk, then > 16k on the 2nd then 16k back on the first, repeat (replace 16k with > whatever your raid stripe size is). > > if its a raid 1 mirror, then either disk by itself has the complete file > system on it, so you should be able to remirror the changed disk onto the > other drive. you MUST do that re-mirror because your two disks are no > longer identical, and reads will alternate between them, so some reads will > get new data and others will get old data, which will be highly chaotic. > John, I figure, BIOS RAID is e...

...hed it. blocks are striped across both drives, so like 16k on the first disk, then 16k on the 2nd then 16k back on the first, repeat (replace 16k with whatever your raid stripe size is). if its a raid 1 mirror, then either disk by itself has the complete file system on it, so you should be able to remirror the changed disk onto the other drive. you MUST do that re-mirror because your two disks are no longer identical, and reads will alternate between them, so some reads will get new data and others will get old data, which will be highly chaotic. On Wed, Nov 4, 2020 at 6:18 PM H <agents at me...

...8, Debian Sid), and I discovered an interesting segfault at the last step of reboot: when the kernel flush out the md devices (raid1) the kernel prints the stack dump and reboot immidietly. After rebooting, the state of first md deveice is clean, but the second md device is dirty and starts the remirror procedure. The halt procedure stops cleanly the machine (the halt command or acpi button event). The reboot works correctly without the pciback.hide parameter. Any idea?! Thanks -- Gabor HALASZ <halasz.g@freemail.hu> _______________________________________________ Xen-users mailing lis...

Has anybody tried or knows if it is possible to create a MD RAID1 device using networked iSCSI devices like those created using OpenFiler? The idea I'm thinking of here is to use two OpenFiler servers with physical drives in RAID 1, to create iSCSI virtual devices and run CentOS guest VMs off the MD RAID 1 device. Since theoretically, this setup would survive both a single physical drive