From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 213627] New: Fail to read block descriptors data of ext4 filesystem
Date: Wed, 30 Jun 2021 18:06:52 +0000 [thread overview]
Message-ID: <bug-213627-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=213627
Bug ID: 213627
Summary: Fail to read block descriptors data of ext4 filesystem
Product: File System
Version: 2.5
Kernel Version: 5.3.x-5.4.x
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: nipunasri.eerapu@arcserve.com
Regression: No
Our product takes backup of filesystems (ext2/3/4,xfs,btrfs) after taking the
snapshot of the volume. We have our own drivers for taking snapshot.
After taking snapshot, we calculate block group count and group descriptors
blocks in Block group0 (group zero). From group descriptors, we read block
bitmap and inode bitmaps.
All this was working well till 5.0.x kernels and from 5.3.x kernels, block
bitmap and inode bitmap values are getting garbage. It doesnot happen all the
time.Everytime after reboot, it works fine.
Our driver simply bypasses read/write calls to system block driver, not sure
why data is corrupted.
Can you please help me what have been changed between 5.0.x and 5.3.x kernels
regarding ext,block driver.
We are not seeing this issue for xfs and btrfs filesystem.
We are suspecting something might have changed in ext2/3/4 and block driver in
5.3.x kernels.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-06-30 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 18:06 bugzilla-daemon [this message]
2021-06-30 18:07 ` [Bug 213627] Fail to read block descriptors data of ext4 filesystem bugzilla-daemon
2021-07-01 0:24 ` bugzilla-daemon
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-213627-13602@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).