The reason I ask is because the topic of
set-default-subvolume is being revisited in Debian. So to be clear, the
"[an]other system" was also Debian? I'd also sincerely appreciate it if
you would share your rationale for why you tried it, as well as why you
stopped using it.
Yes — it was De
Leszek Dubiel writes:
>> What was this other system? I'm curious because, as far as I know, no
>> distribution officially supports the use of "set-default-subvolume".
>
> I have tested it again.
> Setting default subvolume is not relevant in this case.
> This is debian, but settting default is w
What was this other system? I'm curious because, as far as I know, no
distribution officially supports the use of "set-default-subvolume".
I have tested it again.
Setting default subvolume is not relevant in this case.
This is debian, but settting default is what I used to do in the past.
Control: tag -1 moreinfo
Hi Leszek,
Leszek Dubiel writes:
> Package: btrfs-progs
> Version: 4.20.1-2
[snip]
> Another system has set "default subvolume" to mount.
What was this other system? I'm curious because, as far as I know, no
distribution officially supports the use of "set-default-s
Package: btrfs-progs
Version: 4.20.1-2
Severity: normal
Dear Maintainer,
1. created some subvolumes, transfered them successfully to another BTRFS file
system with send/receive
2. created new subvolume, cp -a --reflink=always files, send to the same system
and got error
Another system has set
5 matches
Mail list logo
