linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Partap <mpartap@gmx.net>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: How to view transaction log chronologically, human-readable?
Date: Wed, 23 Apr 2014 18:34:42 +0200	[thread overview]
Message-ID: <5357EBA2.7030605@gmx.net> (raw)
In-Reply-To: <CAKcLGm9Ng4J2rGsC_JUpG+A6Q5bR81kSD8zBAONjkrqsLuUyWQ@mail.gmail.com>

> 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 sounds like you've effectively tried this manually, but here's a
> link to an btrfs undelete script that also makes use of
> btrfs-find-root and 'btrfs restore':
Actually I was using that script as a starting point.. Unfortunately,
the files I was looking for were nowhere to be found..
>From a journal-type functionality I was hoping for a way to actually see
the most recent file system actions..
Is there no hope to recreate that information from the roots
btrfs-find-root comes up with?

#Regards

      reply	other threads:[~2014-04-23 16:34 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
2014-04-21  4:12     ` Mitch Harder
2014-04-23 16:34       ` Marcel Partap [this message]

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=5357EBA2.7030605@gmx.net \
    --to=mpartap@gmx.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mitch.harder@sabayonlinux.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).