Skip to content
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.

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

Empty (excluded?) directories get lost in restore #7

Open
raimi opened this issue Nov 22, 2012 · 2 comments
Open

Empty (excluded?) directories get lost in restore #7

raimi opened this issue Nov 22, 2012 · 2 comments
Assignees
Labels

Comments

@raimi
Copy link
Collaborator

raimi commented Nov 22, 2012

Noticed on using shaback to clone and adjust some machines: Empty and/or excluded directories get lost.

Problem (on Debian):

  • With missing /var/log/apache2/ apache won't start since it can't log.
  • With missing /var/log/fsck/ some logsave(8) processes wait forever

The actual problem are probably our (pi) default exclusion rules - but i wouldn't know a rule to exclude every file from /var/log/ retaining the subdir-structure...

Update 2013-01: This is problem! I just had to recover my entire root-filesystem and the recovery was incomplete. Special directories /dev /sys and /tmp were to created by the recovery process! The directories were part of the repo but they happened to be empty (because they are mount points or were just empty).

@raimi
Copy link
Collaborator Author

raimi commented Feb 10, 2013

How to reproduce (probably, I did not try):

mkdir -p /foo/bar
shaback backup /foo
shaback restore /foo

Bug: empty directory "bar" is not created inside foo.

@workflo
Copy link
Owner

workflo commented Jun 14, 2016

Depends on how you exclude directories:
Exclude even the directory itself:
addExcludePattern('/foo')
Exclude what's inside the directory:
addExcludePattern('/foo/*')

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants