Possible Problem with ext3 File Systems on SAN Storage

Issues have been reported when an ext3 file system fills up to the point where ENOSPC is returned to write requests for a long period of time, and the file system is subsequently unmounted. A forced check is initiated (fsck -fy) before the next mount. It appears that the fsck checks might cause corruption of the file system inode information.

This problem has been seen only on fiber channel (SAN) storage; it has not been seen with directly attached storage or NFS storage.

For more information about details and work arounds, consult Bugzilla number 175877 at the following URL:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175877