Red Hat Bugzilla – Bug 155473
ext3 data corruption under Samba share
Last modified: 2007-11-30 17:07:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.3) Gecko/20040924
Description of problem:
Based on the fsck log we collected from a customer site that reported data corruptions with a 1.8TB filesystem on RHEL 3 system, it was tentatively concluded that the issues found in bugzilla 138951 (opened against RHEL 4) was the cause.
The filesystem is mounted as smb share that gets accessed via Window machines.
The symptoms include "ls" error messages such as:
ï»¿[root@nycpr350fil graphics]# ls -al
ls: athletic.zip: Input/output error
ls: â¢DSC_0010.psd: Input/output error
ls: â¢DSC_0014.psd: Input/output error
ls: WeatherPlusLOGOfeb9.eps: Input/output erro
From /var/log/messages file:
EXT3-fs error (device power2(232,49)): ext3_free_blocks: bit already cleared for block 33103513
that shows bitmap corruption. The blocks that are in use may be marked as available for reuse and subsequently get allocated as "free" blocks.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. (occurs twice on mission cirtical production system)
Actual Results: filesystem corrupted
Expected Results: no corrutions
This has been occurred twice on a mission critical system with large LUN (1.8TB). Other than downtime is not acceptable, the fsck time for the LUN with this size is also unmanageable.
Created attachment 113428 [details]
Created attachment 113429 [details]
Stephen Tweedie backported these two patches into RHEL 3. A RHEL 3 .31EL
beehive based test kernel with these two patches had been sent to customer
*** Bug 161056 has been marked as a duplicate of this bug. ***
Created attachment 116401 [details]
Test case from bug #161056.
A fix for this problem has just been committed to the RHEL3 U6
patch pool this evening (in kernel version 2.4.21-32.12.EL).
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.