Skip to content

Fix btrfs subvolumes with TSM, sshd config #833

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
jsmeix merged 3 commits into from
May 12, 2016
Merged

Fix btrfs subvolumes with TSM, sshd config #833

jsmeix merged 3 commits into from
May 12, 2016

Conversation

@Joeri-MS
Copy link
Contributor

@Joeri-MS Joeri-MS commented May 12, 2016

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

Stephan Joerrens added 3 commits May 12, 2016 08:37
Update 40_verify_tsm.sh
29ef69b 
Add BTRFS subvolumes to TSM restore list.
Update 40_verify_tsm.sh
0f622ca 
Exclude /.snapshots from btrfs subvolumes.
Update run-sshd
d54bdf5 
Set PermitRootLogin yes and ClientAliveInterval 0 to avoid ssh-login problems with systems wich have secure ssh settings.
@jsmeix jsmeix added enhancement Adaptions and new features waiting for info Also used to mark an issue as stale, cf. stale.yml labels May 12, 2016
@jsmeix jsmeix added this to the Rear v1.19 milestone May 12, 2016
@jsmeix jsmeix self-assigned this May 12, 2016
@jsmeix
Copy link
Member

jsmeix commented May 12, 2016 •
edited
Loading

@Joeri-MS
many thanks for your valuable contribution!

As I wrote in #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
Copy link
Contributor Author

Joeri-MS commented May 12, 2016

Tested it with SLES 12 SP1.

@jsmeix jsmeix merged commit f02fa4a into rear:master May 12, 2016
@jsmeix jsmeix added fixed / solved / done and removed waiting for info Also used to mark an issue as stale, cf. stale.yml labels May 12, 2016
@jsmeix
Copy link
Member

jsmeix commented May 12, 2016

@Joeri-MS
I merged your pull request.

This was referenced May 12, 2016
Closed
Closed
@vishualways
Copy link

vishualways commented Dec 1, 2016

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
Copy link
Member

jsmeix commented Dec 1, 2016

Cf. #1095

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@jsmeix jsmeix

Labels

enhancement Adaptions and new features fixed / solved / done

Projects

None yet

Milestone

Rear v1.19

Development

Successfully merging this pull request may close these issues.

3 participants

@Joeri-MS @jsmeix @vishualways