[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-56831-13602@https.bugzilla.kernel.org/>
Date: Fri, 19 Apr 2013 13:41:02 +0000 (UTC)
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 56831] New: RHEL Linux Data Corruption found with EXT4 system
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@...nel-bugs.osdl.org
ReportedBy: searchfordave@...il.com
CC: lalwanihiro@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists