Cloning this bug as it's now being seeing on RHEL5

SCENARIO - [fs_io_A]
Create snapshots of origin with fs data, and then verify that data on snapshots
Making origin volume
Placing an ext filesystem on origin volume
mke2fs 1.39 (29-May-2006)
Mounting origin volume

Writing files to /mnt/origin
checkit starting with:
CREATE
Num files:          500
Random Seed:        12647
Verify XIOR Stream: /tmp/checkit_origin_1
Working dir:        /mnt/origin

Checking files on /mnt/origin
checkit starting with:
VERIFY
Verify XIOR Stream: /tmp/checkit_origin_1
Working dir:        /mnt/origin
Making 1st snapshot of origin volume
Mounting 1st snap volume
Checking files on /mnt/fs_snap1
checkit starting with:
VERIFY
Verify XIOR Stream: /tmp/checkit_origin_1
Working dir:        /mnt/fs_snap1
*** DATA COMPARISON ERROR [file:dxvpxwvnqsjerbwemynqfepxdmsvygnegmvgjstbngh] ***
Corrupt regions follow - unprintable chars are represented as '.'
-----------------------------------------------------------------
corrupt bytes starting at file offset 0
    1st 32 expected bytes:  FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
    1st 32 actual bytes:    EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

checkit verify failed



[root@hayes-03 tmp]# lvs -a -o +devices
  LV       VG         Attr   LSize  Origin Snap%  Move Log Copy%  Convert Devices              
  LogVol00 VolGroup00 -wi-ao 72.44G                                       /dev/sda2(0)         
  LogVol01 VolGroup00 -wi-ao  1.94G                                       /dev/sda2(2318)      
  fs_snap1 snapper    swi-ao  3.50G origin   0.00                         /dev/etherd/e1.1p2(0)
  origin   snapper    owi-ao  4.00G                                       /dev/etherd/e1.1p1(0)


2.6.18-92.el5

lvm2-2.02.39-2.el5    BUILT: Wed Jul  9 07:26:29 CDT 2008
lvm2-cluster-2.02.39-1.el5    BUILT: Thu Jul  3 09:31:57 CDT 2008
device-mapper-1.02.27-1.el5    BUILT: Thu Jul  3 03:22:29 CDT 2008

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time.  This request will be
reviewed for a future Red Hat Enterprise Linux release.

I'm currently unable to reproduce this corruption with the latest 5.3 release. Will close this bug if not seen again in the next couple months...

============================================================
Iteration 607 of 10000 started at Thu Jan 15 14:45:24 CST 2009
============================================================  
SCENARIO - [fs_io_A]                        

2.6.18-128.el5

lvm2-2.02.40-6.el5    BUILT: Fri Oct 24 07:37:33 CDT 2008
lvm2-cluster-2.02.40-7.el5    BUILT: Wed Nov 26 07:19:19 CST 2008
device-mapper-1.02.28-2.el5    BUILT: Fri Sep 19 02:50:32 CDT 2008
cmirror-1.1.36-1.el5    BUILT: Tue Dec  9 16:38:13 CST 2008
kmod-cmirror-0.1.21-10.el5    BUILT: Wed Dec 17 15:18:59 CST 2008

Corey, it has been a few months.  Want to close this?

Eric, I'm wondering if anything related to quiescing an ext3 file system has been fixed in the last 6 months or so?

not in rhel5 anyway ...

Unable to reproduce this in 5.4. Closing...