From: Nikolay Borisov <nborisov@suse.com>
To: Alex Shashkov <oleks.sha74@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Deletion on BTRFS - how does it work
Date: Thu, 22 Aug 2019 19:18:40 +0300 [thread overview]
Message-ID: <cdc805dc-a276-8943-6b40-f878e698c580@suse.com> (raw)
In-Reply-To: <CAKzB54QYNFjgfPUM8KqAHGPwSWPVczbhZidKpCpL7baJO8hzAA@mail.gmail.com>
On 9.08.19 г. 7:25 ч., Alex Shashkov wrote:
> I'm trying to understand how deletion works on BTRFS. Let's say
> directory containing files and other directories gets deleted. What is
> essentially happening during this action, what strucutres get updated,
> what artifacts remain after the deletion, is it possible to find them
> and recover deleted objects, if yes, then how? Thanks in advance!
You want to look into btrfs_unlink_inode to see how unlinking works in
bttrfs.
>
next prev parent reply other threads:[~2019-08-22 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 1:24 [PATCH v1.2 0/3] btrfs: tree-checker: Add extent items check Qu Wenruo
2019-08-09 1:24 ` [PATCH v1.2 1/3] btrfs: tree-checker: Add EXTENT_ITEM and METADATA_ITEM check Qu Wenruo
2019-08-22 14:59 ` David Sterba
2019-08-09 1:24 ` [PATCH v1.2 2/3] btrfs: tree-checker: Add simple keyed refs check Qu Wenruo
[not found] ` <CAKzB54SN1FmGhGHQOfT2fvn=ESQn4vOwbPpPM7p8eJRkNmvf7w@mail.gmail.com>
2019-08-09 4:25 ` Deletion on BTRFS - how does it work Alex Shashkov
2019-08-22 16:18 ` Nikolay Borisov [this message]
2019-08-22 15:02 ` [PATCH v1.2 2/3] btrfs: tree-checker: Add simple keyed refs check David Sterba
2019-08-09 1:24 ` [PATCH v1.2 3/3] btrfs: tree-checker: Add EXTENT_DATA_REF check Qu Wenruo
2019-08-22 15:08 ` [PATCH v1.2 0/3] btrfs: tree-checker: Add extent items check David Sterba
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=cdc805dc-a276-8943-6b40-f878e698c580@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=oleks.sha74@gmail.com \
/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).