we're running into a scenario similar to this with CentOS 6, zero length files after a system crash. http://oss.sgi.com/archives/xfs/2012-02/msg00607.html I'm not exactly sure which kernel version they are running in production (its in China), but I'm trying to find out. its probably a year or so old, our manufacturing operations folks do NOT like installing random updates without very good reasons. meanwhile, I wonder if anyone familiar with it knows if the fix that Dave Chinner discusses in that posting I link above has been backported to a recent EL6 kernel. -- john r pierce 37N 122W somewhere on the middle of the left coast
John R Pierce:> we're running into a scenario similar to this with CentOS 6, zero length > files after a system crash. > http://oss.sgi.com/archives/xfs/2012-02/msg00607.html > > I'm not exactly sure which kernel version they are running in production > (its in China), but I'm trying to find out. its probably a year or so > old, our manufacturing operations folks do NOT like installing random > updates without very good reasons. > > meanwhile, I wonder if anyone familiar with it knows if the fix that > Dave Chinner discusses in that posting I link above has been backported > to a recent EL6 kernel.This was fixed in EL6 kernels a while ago - see: <http://rhn.redhat.com/errata/RHSA-2012-1401.html> James Pearson
Maybe Matching Threads
- [PATCH v6 6/6] xfs: disable map_sync for async flush
- [PATCH v6 6/6] xfs: disable map_sync for async flush
- [PATCH v4 5/5] xfs: disable map_sync for async flush
- [PATCH v4 5/5] xfs: disable map_sync for async flush
- [PATCH v4 5/5] xfs: disable map_sync for async flush