From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 194739] New: fallocate --collapse-range causes temporal data corruption on fragmented file
Date: Wed, 01 Mar 2017 00:00:51 +0000 [thread overview]
Message-ID: <bug-194739-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=194739
Bug ID: 194739
Summary: fallocate --collapse-range causes temporal data
corruption on fragmented file
Product: File System
Version: 2.5
Kernel Version: 4.10.1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: iive@yahoo.com
Regression: No
I use `fallocate -c` to cut the start of the file without having to copy the
whole file again.
However recently, after collapsing the file it seems to repeat a portion of the
data, that should have been moved. That is, the new start of the file is found
somewhere around its old location.
Restarting the computer (or just hibernate) seems to fix the file.
Doing:
`echo 3 > /proc/sys/vm/drop_caches`
also seems to fix the issue. Using just `echo 1` fixes some of the data, but
the file still might be broken.
I've noticed this problem on 4.9 kernel. I'm not sure if it is regression,
because the problem might be triggered by high fragmentation. This partition
got quite full and the files are quite big, thus they are always very
fragmented.
Just want to make it clear.
Data on disk is not damaged.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2017-03-01 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 0:00 bugzilla-daemon [this message]
2017-03-15 17:48 ` [Bug 194739] fallocate --collapse-range causes temporal data corruption on fragmented file 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-194739-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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.