From: Marcel Partap <mpartap@gmx.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: How to view transaction log chronologically, human-readable?
Date: Sat, 19 Apr 2014 21:45:46 +0200 [thread overview]
Message-ID: <5352D26A.70601@gmx.net> (raw)
In-Reply-To: <5322E39C.3030802@gmx.net>
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.
>> 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 root trees. However, diffing these, I find the current one being
>> the same until 94 root trees back, and the ones before contain earlier
>> changes. Maybe by my own fault that is..whatever.
>>
>> Is there a way to just view the transaction history in a human-readable way?
>>
>> #Regards
>>
next prev parent reply other threads:[~2014-04-20 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 1:21 How to view transaction log chronologically, human-readable? Marcel Partap
2014-03-14 11:10 ` Marcel Partap
2014-04-19 19:45 ` Marcel Partap [this message]
2014-04-21 4:12 ` Mitch Harder
2014-04-23 16:34 ` Marcel Partap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5352D26A.70601@gmx.net \
--to=mpartap@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).