Johannes Meixner

FYI for clarification to avoid misunderstandings: I refuse to think about what is commonly called "user expectations" or similar. It is right to ask for what one himself needs. It...

FYI see also https://github.com/rear/rear/issues/2604

After sleeping on it for some time now I meanwhile got a vague tentative untested idea how it might be possible to implement that some btrfs subvolumes get automatically included...

@pcahyna could you show me on a Fedora installation the output of ``` # lsblk -ipo NAME,KNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINTS ``` if this works on Fedora (i.e. with 'MOUNTPOINTS' plural) plus the disklayout.conf...

This issue will be fixed by https://github.com/rear/rear/pull/3175

@lzaoral thank you for this enhancement! I will test how it behaves on SLES systems with their rather complicated default btrfs structure. Offhandedly I think the main problem is possibly...

Only an offhanded thought: I fear btrfs normal subvolumes versus btrfs snapshot subvolumes is only one example of a very generic problem when by default every mounted "thingy" is included...

Perhaps we can by default have every mounted "thingy" included in the 'tar' backup BUT we may need some check for duplicates in the 'tar' backup i.e. something that detects...

Currently I am exploring how 'tar' behaves in general when exact same files are provided as 'tar' arguments to be archived. It seems 'tar' behaves well forgiving in this case:...

Yes. The whole point of my experiments with 'tar' here is to find out if my "fear" above is true or not and in general to better understand what we...