linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@mikefedyk.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Disk space accounting and subvolume delete
Date: Mon, 31 May 2010 13:34:56 -0700	[thread overview]
Message-ID: <AANLkTilyZTk9j54i7Dzj-eeQHyWE3G5tYwzPIznDdKy1@mail.gmail.com> (raw)
In-Reply-To: <20100531190107.GA20103@untroubled.org>

On Mon, May 31, 2010 at 12:01 PM, Bruce Guenter <bruce@untroubled.org> =
wrote:
> On Wed, May 12, 2010 at 01:02:07PM +0800, Yan, Zheng =C2=A0wrote:
>> Dropping a tree can be lengthy. It's not good to let sync wait for h=
ours.
>> For most linux FS, 'sync' just force an transaction/journal commit. =
I don't
>> think they wait for large operations that can span multiple transact=
ions to
>> complete.
>
> What happens to the consistency of the filesystem if a crash happens
> during this process?

There's a good test case for you to try.  Let us know what you find.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-05-31 20:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 18:23 Disk space accounting and subvolume delete Bruce Guenter
2010-05-10 18:50 ` Josef Bacik
2010-05-11  0:10 ` Yan, Zheng 
2010-05-11 15:45   ` Bruce Guenter
2010-05-12  5:02     ` Yan, Zheng 
2010-05-12 21:56       ` Mike Fleetwood
2010-05-31 19:01       ` Bruce Guenter
2010-05-31 20:34         ` Mike Fedyk [this message]
2010-06-01  2:32         ` Yan, Zheng 

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=AANLkTilyZTk9j54i7Dzj-eeQHyWE3G5tYwzPIznDdKy1@mail.gmail.com \
    --to=mfedyk@mikefedyk.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).