linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 206419] online resize + fstrim -> bad block checksum
Date: Tue, 04 Feb 2020 23:40:58 +0000	[thread overview]
Message-ID: <bug-206419-13602-ArShzbabgi@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206419-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=206419

--- Comment #1 from bugzilla.kernel.org@plan9.de ---
I was able to umount the filesystem and ran e2fsck, which offered:

Inode 34852 extent tree (at level 2) could be narrower.  Optimize<y>? yes

And then went on to correct bitmpa differences - no sign of the bitmap block
checksum error. Afterwards, I mounted again and now fstrim works without
complaints.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      reply	other threads:[~2020-02-04 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 23:14 [Bug 206419] New: online resize + fstrim -> bad block checksum bugzilla-daemon
2020-02-04 23:40 ` bugzilla-daemon [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=bug-206419-13602-ArShzbabgi@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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).