-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 2016-12-29 20:39, Michael Hamilton wrote:
On Fri, 30 Dec 2016, Paul Neuwirth wrote:
On Wednesday 2016-12-28 17:32, sdm wrote:
then if it were me, I would opt for btrfs built-in software RAID 1 over mdadm RAID 1+btrfs.
I think it's time to give up, after repairing the mdadm raid, btrfs check segfaults trying to repair the volume. luckily I have a backup... How would you proceed, to create a new setup with btrfs with built-in software RAID 1. I would like to clone the subvolume layout.
first idea is to do a clean new Install (does Yast setup let me set up this btrfs RAID?) - start a rescue system, restore the backup to the new install, clean up /etc/fstab, chroot, dracut, reinstall bootloader.
or is there a faster way (i don't know how to clone the btrfs layout and set up btrfs raid manually) instead of a fresh install. Any literature?
thanks a lot
I recently wrote up how to clone the root sub-volume structure here:
https://forums.opensuse.org/showthread.php/521277-LEAP-42-2-btrfs-root-files...
But I have no experience with brtrs RAID, so I cannot help there.
I suspect it may be easier to completely reinstall a minimum install and then restore over the top of it. But I guess this may result in other problems. You should probably practice in a virtualbox. I don't think the available btrfs docs and google-results have sufficient details to be safe without practising before hand.
If you follow the link provided, you will also see that I gave up on btrfs and returned to ext4 because, like yourself, I have recovery processes and procedures that would need quite a bit of rethinking for btrfs.
Cheers, Michael
a) solution finally.. I did a clean install (btrfs raid options are not supported by the installer) on a partition of the 1st hdd, then created a identical partition on the 2nd hard disk, added the partition to the btrfs filesystem, converted to RAID1 layout, according to this manual https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices a bit more tricky was the restore, because there is no recent openSuSE live system downloadable anymore. I needed dar to restore backup, i do not think it's in the install system available. So I used a debian live image, mounted all subvolumes to /mnt and restored all files with dar from a nfs mount, assembled a new fstab. But create a new initrd/install bootloader did not work in chroot environment (debian is maybe too different). But with some convenience I manually booted through grub2 console using an initrd from the btrfs snapshot (version before restore). very useful these snapshots in this case.. ;) these could have saved lots of time in the passed. b) open issue btrfs raid1 Only question, how can I install the generic bootcode to the MBR of both disks, not only the first one? there's no "custom root partition" or anything in the yast module. Also configuration for serial console seems to be gone :( c) bugs found I also found some bugs (maybe) 1) setting keyboard layout using the images from software.opensuse.org does not work (set language to english, but keyboard layout de-ch) - reproducable 2) in yast (ncurses) shift+tab did the same as only tab.. in the newly installed OS (without additional repos), very annoying ;) thank you all for your help, learned a lot about btrfs . d) problem continued just wanted to send.. but somehow I destroyed the bootloader now, only getting into rescue mode. what I did: I booted into system with the kernel/initrd from install, but the filesystem contents were from the old install. Worked fine, created new initrd, installed bootloader. When I booted using the new kernel/initrd, many kernel modules were not loaded: messages were: systemd-modules-load: Failed to lookup alias 'sg': Function not implemented systemd: Unit systemd-modules-load.service entered failed state. maybe related to changed hardware (added scsi card, 2 scanners, 1 tape drive, 1 fdd) ? I tried again to install the bootloader in this broken environment. Afterwards grub2 only gets into rescue mode, it looks for data in the old md-volume, which does not exist anymore (error: disk 'mduuid/...' not found.), seems I missed some configuration... ? e) and solved no progress using grub rescue possible, because btrfs support is missing "unknown filesystem". using the installer image, rescue mode worked to boot into system with current kernel. did not find anything referencing the old md-volume grub2 wanted in any config in /etc/grub.d/ /etc/sysconfig/ or /etc/default/ ? installed new updates/patches, including new kernel. looking into new grub2 generated config, and dracut output seems to be ok. reboot. grub2 menu loads and looks ok. boot. all modules came up. systemctl does not show any failed unit. finally done :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Topal (http://freshmeat.net/projects/topal) iQIcBAEBAgAGBQJYZ3yAAAoJEIiaa+Y8YDPuVWUP/2RbaCSaVE1E73pO3O57fbp6 7UVgDPNu2D1xlIKlnuyxp9fc0o3DBRw0inUuVVus7Ds1e/kL8Bz2ZJaJSvbL0tHO Xoc5hQJVpXM8GW7s+TQGQMZLr7uaJr+NMAPyusI67R7OADYvizZl9yqiY5kC7FRA P1tBBRoSiW2zIUUDHzSvqXsijAN06esxi1XWGt7WlzM+t3b6/UeJE4fIF+0R/4LI QI2IgUmq1fU+GzRMpESPGdQ8sFFuyVLoN22GN0udVuADkNXOquQQ76nHtpBc5i66 2D61W7z1ZJc7kJcZsBBdHsPZDlrOqvPCcHRKSJCc8HHgruMoaf/37c2+s8Tc7i4P 2CqEzamKHP3Aziv2BBapp+KUD8uovwyetUF6jxAQV9wC4nP+VZ82IM7vy8QL49Bw WZ6zJCaFqAKnIZ666dpdlwIAEN08JTosDpCJjez8MiYvuvVwbPOfL5D0TvZOuWuC uhRhmpATghAvm/QlcyuyqNo5LLRhoO2S+n2Tqe2Qo5zwN0B9TGK0Q6GZ5MgHfAOF /U9Y3nu9OuY4NPVaW19TrSuAFi1We0WtNUYt/hwp2vd/4RTqVEEwbDL4LeHk5zwV 2zmbCrhlQdGdgw/kFBnVnjnt0OXqSuSx07yGRSrJabBzAbfuD5UEpO0VOMLOXgZJ BDFWu/GgMAY1MKNjS6ya =yB9G -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org