From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: dsterba@suse.com
Subject: Re: Patch "Btrfs: do not start a transaction during fiemap"
Date: Wed, 29 May 2019 15:55:14 +0200 [thread overview]
Message-ID: <90f76cf541c5572c1a89b1388a26515994db60bc.camel@scientia.net> (raw)
In-Reply-To: <b2a668d7124f1d3e410367f587926f622b3f03a4.camel@scientia.net>
Hey David.
Regarding your patch "Btrfs: do not start a transaction during
fiemap"...
I assume since the blockdevice had to be set read-only in order for the
bug to happen... all these aborted transactions, etc. couldn't cause
any corruptions/etc. upon the fs,... so there's nothing further one
would need to check, right?
Thanks,
Chris.
prev parent reply other threads:[~2019-05-29 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 3:42 delayed_refs has NO entry / btrfs_update_root:136: Aborting unused transaction(No space left) Christoph Anton Mitterer
2019-03-20 0:59 ` Christoph Anton Mitterer
2019-03-20 9:59 ` Johannes Thumshirn
2019-04-12 22:46 ` Christoph Anton Mitterer
2019-04-12 22:52 ` Christoph Anton Mitterer
2019-04-15 8:42 ` Johannes Thumshirn
2019-05-03 2:42 ` Christoph Anton Mitterer
2019-05-16 9:12 ` Christoph Anton Mitterer
2019-05-29 13:55 ` Christoph Anton Mitterer [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=90f76cf541c5572c1a89b1388a26515994db60bc.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=dsterba@suse.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).