From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 56831] New: RHEL Linux Data Corruption found with EXT4 system
Date: Fri, 19 Apr 2013 13:41:02 +0000 (UTC) [thread overview]
Message-ID: <bug-56831-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=56831
Summary: RHEL Linux Data Corruption found with EXT4 system
Product: File System
Version: 2.5
Kernel Version: 2.6.32-220
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: searchfordave@gmail.com
CC: lalwanihiro@gmail.com
Regression: No
The attached file when compiled on a 32GB Mem system, gives a data corruption
if run with number of threads greater than 15
How to run:
1. compile: # gcc random_multi_write_read.c -o test -lpthread
2. Usage: # ./test <file path> <no. of threads>
3. Run: # ./test file_1 15
Sample Output:
Starting 15 write threads to file_1 at different offsets and write sizes...
Parallelly reading the file for any data corruption...
DATA CORRUPTION HIT
Actual: '', Expected: 'K'd
, start:4581061500, end:5039167650
...
For More info, refer file "V_loop<%d>char<%c>" which gets created newly to
capture the corrupted data as soon as corruption is hit.
Test system details:
#CPUS: 2
#CORES: 6
SYSTEM MEMORY: 15 GB
SWAP MEMORY: 17 GB
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2013-04-19 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 13:41 bugzilla-daemon [this message]
2013-04-19 13:42 ` [Bug 56831] RHEL Linux Data Corruption found with EXT4 system bugzilla-daemon
2013-11-13 21:03 ` bugzilla-daemon
2013-11-13 21:04 ` bugzilla-daemon
2013-11-13 21:04 ` 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-56831-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 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.