I am not a dev, but since BTRFS utilizes a COW (Copy On Write)
architecture, it doesn't keep a journal or history of transactions
that can be unwound.
Ok, thanks for making that clear, I wasn't aware of that.
But shouldn't the chain of recent root trees kinda allow similar
functionality?
It
This is the BTRFS development list, right? Someone here should know how
to achieve this I hope?
#Regards
On 01/03/14 02:21, Marcel Partap wrote:
Dear BTFRS devs,
I have a 1TB btrfs volume mounted read-only since two years because I
deleted a bunch of files and didn't want to give up on them.
On Sat, Apr 19, 2014 at 2:45 PM, Marcel Partap mpar...@gmx.net wrote:
This is the BTRFS development list, right? Someone here should know how
to achieve this I hope?
#Regards
On 01/03/14 02:21, Marcel Partap wrote:
Dear BTFRS devs,
I have a 1TB btrfs volume mounted read-only since two years
[...]
Theoretically, there should be someone on this mailing list capable of
answering this question, no?
Please feel invited to share your insights ;)
#Regards
On 01/03/14 02:21, Marcel Partap wrote:
Dear BTFRS devs,
I have a 1TB btrfs volume mounted read-only since two years because I
Dear BTFRS devs,
I have a 1TB btrfs volume mounted read-only since two years because I
deleted a bunch of files and didn't want to give up on them.
Now with latest btrfs-find-root and btrfs restore --dry-run -t in a
loop, I generated the full list of files contained in the last several
hundred
