Skip to content

Unexpected behaviour when using -one-file-system #1416

@xSWIGx

Description

@xSWIGx

Output of restic version

root@Server:~# restic version
restic 0.7.3
compiled with go1.9 on linux/amd64

How did you run restic exactly?

restic -r /mnt/backup/ backup --one-file-system / /mnt/storage/ --exclude "/mnt/files"

What backend/server/service did you use?

Filesystem

Expected behavior

I would like filesystem snapshot with:

  1. / - root filesystem without sys, dev, etc...
  2. /mnt/storage - this mounted filesystem on its own place

Actual behavior

What i have:

  1. / - root filesystem without sys, dev, etc...
  2. /mnt/storage - this mounted filesystem on its own place
  3. /storage - this folder contain all duplicated files from /mnt/storage

Steps to reproduce the behavior

  1. Use restic -r /mnt/backup/ backup --one-file-system / /mnt/storage/ --exclude "/mnt/files" to make backup snapshot.
  2. Use restic -r /mnt/backup/ mount /mnt/restic/ then check /mnt/restic/snapshots/<snapshot_name>/. This will contain both /mnt/storage and /storage
    OR
    Use restic -r /mnt/backup/ restore latest --target /tmp/restore --path "/" then check /tmp/restore for /mnt/storage and /storage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions