All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naohiro Aota <naohiro.aota@wdc.com>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs fixes for 5.13-rc5
Date: Fri, 4 Jun 2021 10:17:07 +0900	[thread overview]
Message-ID: <20210604011707.l6mvqn5z2yvm4j3z@naota-xeon> (raw)
In-Reply-To: <cover.1622728563.git.dsterba@suse.com>

On Thu, Jun 03, 2021 at 04:50:15PM +0200, David Sterba wrote:
> Hi,
> 
> this is a batch from last week, I wanted to give it more testing because
> last pull request introduced a bug, interacting zoned and subpage
> features. Otherwise there are error handling improvements and bug
> fixes. The last commit is from today, adding IRC link to maintainers
> file.
> 
> Please pull, thanks.
> 
> - error handling improvements, caught by error injection
>   - handle errors during checksum deletion
>   - set error on mapping when ordered extent io cannot be finished
>   - inode link count fixup in tree-log
>   - missing return value checks for inode updates in tree-log
>   - abort transaction in rename exchange if adding second reference fails
> 
> - fixes
>   - fix fsync failure after writes to prealloc extents
>   - fix deadlock when cloning inline extents and low on available space
>   - fix compressed writes that cross stripe boundary
>

David,

Could you also add commit "btrfs: zoned: fix zone number to
sector/physical calculation" for pull? Without this commit, on a
device larger than 4 TB, zoned btrfs will overwrite the primary
superblock with the 2nd copy and causes a mount failure after the
first mount/umount.

https://lore.kernel.org/linux-btrfs/20210527062732.2683788-1-naohiro.aota@wdc.com/

Thanks,

  parent reply	other threads:[~2021-06-04  1:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 14:50 [GIT PULL] Btrfs fixes for 5.13-rc5 David Sterba
2021-06-03 19:09 ` pr-tracker-bot
2021-06-04  1:17 ` Naohiro Aota [this message]
2021-06-04 11:10   ` 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=20210604011707.l6mvqn5z2yvm4j3z@naota-xeon \
    --to=naohiro.aota@wdc.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.