From: "Norbert Scheibner" <scno@gmx.net>
To: Roman Mamedov <rm@romanrm.ru>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Freeing space over reboot question
Date: Sat, 11 Feb 2012 14:47:15 +0100 [thread overview]
Message-ID: <20120211134715.200530@gmx.net> (raw)
In-Reply-To: <20120210002055.6819f76c@natsu>
On: Fri, 10 Feb 2012 00:20:55 +0600 Roman Mamedov <rm@romanrm.ru> wrote
> AFAIK the only reliable way currently to ensure the space after a
> subvolume
> deletion is freed, is to remount the FS.
Have You tried it Yourself? I think the problem was the remount
before the space has been completely freed in background. It
left a valid and working fs, with still work to do.
In my opinion the kernel should either stall the umount till the
space is given free or restart the cleaner after the next mount.
To stall the umount could be annoying and make the user believe
something is broken, because the cleaner could take a while and
it feels to classic for modern fs.
Is there a way to leave an entry in the log to replay after the
next mount? Pardon me if I use the wrong terms here, I'm just
an interested user and not a fs-crack or even a programmer.
Regards
Norbert
next prev parent reply other threads:[~2012-02-11 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 17:42 Freeing space over reboot question Norbert Scheibner
2012-02-09 18:11 ` Chester
2012-02-09 18:57 ` Norbert Scheibner
2012-02-09 18:20 ` Roman Mamedov
2012-02-09 19:02 ` cwillu
2012-02-11 13:47 ` Norbert Scheibner [this message]
2012-02-11 13:56 ` Roman Mamedov
2012-02-11 16:42 ` Norbert Scheibner
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=20120211134715.200530@gmx.net \
--to=scno@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.ru \
/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).