linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tiago Marques <bugs@tmarques.com>
To: linux-btrfs@vger.kernel.org
Subject: Can't recover space from deleted inode
Date: Wed, 4 Dec 2019 15:16:31 +0000	[thread overview]
Message-ID: <CAF6-ow=qsPEyZEPjNhacX8Hipnk69hXfQOiVQ_x+FajEU67RqQ@mail.gmail.com> (raw)

Hi everyone,

I stumbled upon a bug on one of my systems where I can't seem to
recover space that should be free. This is non standard though:

1) Was downloading an ISO with wget,
2) By mistake on another terminal I deleted the temporary file,
3) wget kept downloading but couldn't move the temporary file, so it
exited with an error (I realized something had gone wrong),
4) I use 'df -h' and notice the size of the ISO file is missing. After
reboot and 'btrfs scrub', can't recover that free space.

Is this a bug and is there a tool that fixes this. I've read the wiki
and manuals and BTRFS doesn't have anything that checks correctness of
the filesystem?

Best regards,
Tiago Marques

                 reply	other threads:[~2019-12-04 15:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAF6-ow=qsPEyZEPjNhacX8Hipnk69hXfQOiVQ_x+FajEU67RqQ@mail.gmail.com' \
    --to=bugs@tmarques.com \
    --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).