#833 PR merged: Fix btrfs subvolumes with TSM, sshd config¶
Labels: enhancement, fixed / solved / done
Joeri-MS opened issue at 2016-05-12 09:07:¶
Avoid Problems with ssh-logins when the original sshd_config has some
extra secure lines.
Fix the problem where the btrfs subvlums are not restored via TSM.
See Issue #823
jsmeix commented at 2016-05-12 09:20:¶
@Joeri-MS
many thanks for your valuable contribution!
As I wrote in
https://github.com/rear/rear/issues/823
I cannot check myself if it works
(because I do not have TSM)
which means I could only "basically blindly" acccept it.
With "basically blindly" I mean that I can only look
at the code whether or not it looks o.k. for me
but I cannot verify by a test that it actually works.
Because your code looks o.k. for me
I will "basically blindly" acccept your pull request
provided you could report here with some details
on which system you have tested it so that it is
documented where it can be expected to work.
Joeri-MS commented at 2016-05-12 10:07:¶
Tested it with SLES 12 SP1.
jsmeix commented at 2016-05-12 11:52:¶
@Joeri-MS
I merged your pull request.
vishualways commented at 2016-12-01 13:12:¶
Hi, We are facing similar issue while recovering SLES 12 SP1 (Rear 1.19)
with default btrfs for systemvg. We can backup and create image fine
however during recovering it gives errors. Could you please help us in
overcoming this issue and it has became a kind of show-stopper atm. Is
there a workaround/patch/update to get it working on SLES12 SP1? I have
contacted SLES support and they said they only support REAR on SLES for
SAP version and not the normal SLES.
I am not well-verse with github so please excuse my non-awareness
regarding posts. Your help/advice would be much appreciated.
Thanks and regards,
Vish
jsmeix commented at 2016-12-01 14:11:¶
Cf. https://github.com/rear/rear/issues/1095
[Export of Github issue for rear/rear.]