From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 103111] New: auto_da_alloc mount option not working
Date: Wed, 19 Aug 2015 13:34:48 +0000 [thread overview]
Message-ID: <bug-103111-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=103111
Bug ID: 103111
Summary: auto_da_alloc mount option not working
Product: File System
Version: 2.5
Kernel Version: 2.6.39
Hardware: Intel
OS: Linux
Tree: Fedora
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: patelrakeshcomp@gmail.com
Regression: No
As per the ext4 guide,
ext4 will detect the replace-via-rename and replace-via-truncate patterns
and force that any delayed allocation blocks are allocated such
that at the next journal commit, in the
default data=ordered mode, the data blocks of the new file are
forced to disk before the rename() opera‐
tion is committed.
But it looks like this feature is not working anymore.
Kernel version: 2.6.39.
Filesystem: ext4
Here is the sample code:
ofstream myfile;
myfile.open ("example.txt",std::ofstream::trunc);
myfile << "Writing this to a file.\n";
system("mv example.txt example.txt1");
Expected behaviour: Ext4 should detect trunc() call and should allocate blocks
for same. So there should be no zero-length file after abnormal
shutdown(withing 30sec).
Actual results: File is having zero-length after abnormal reboot(power outage).
--
You are receiving this mail because:
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-08-19 13:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 13:34 bugzilla-daemon [this message]
2015-08-19 16:13 ` [Bug 103111] auto_da_alloc mount option not working bugzilla-daemon
2015-08-20 5:48 ` bugzilla-daemon
2015-08-20 5:53 ` bugzilla-daemon
2015-08-20 5:54 ` bugzilla-daemon
2015-08-21 14:56 ` bugzilla-daemon
2015-08-21 14:59 ` bugzilla-daemon
2015-08-21 15:13 ` bugzilla-daemon
2015-08-21 15:16 ` bugzilla-daemon
2015-08-21 18:36 ` bugzilla-daemon
2015-08-25 17:49 ` bugzilla-daemon
2015-08-25 18:05 ` bugzilla-daemon
2015-08-28 16:49 ` bugzilla-daemon
2015-08-28 16:51 ` bugzilla-daemon
2015-08-29 3:25 ` bugzilla-daemon
2015-08-29 3:28 ` bugzilla-daemon
2015-08-29 19:33 ` 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-103111-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).