On Wed, Apr 13, 2011 at 6:04 PM, Ross Walker <rswwalker at gmail.com> wrote: > > > > One was a hardware raid over fibre channel, which silently corrupted > > itself. System checked out fine, raid array checked out fine, xfs was > > replaced with ext3, and the system ran without issue. > > > > Second was multiple hardware arrays over linux md raid0, also over fibre > > channel. This was not so silent corruption, as in xfs would detect it > > and lock the filesystem into read-only before it, pardon the pun, truly > > fscked itself. Happened two or three times, before we gave up, split up > > the raid, and went ext3, Again, no issues. > > Every now and then I hear these XFS horror stories. They seem too > impossible to believe. > > Nothing breaks for absolutely no reason and failure to know where the > breakage was shows that maybe there wasn't adequately skilled techinicians > for the technology deployed. > > XFS if run in a properly configured environment will run flawlessly. > > That's not entirely true. Even in Centos 5.3(?), we ran into an issue of XFS running on an md array would lock up for seemingly no reason due to possible corruption. I've even bookmarked the relevant bug thread for posterity sake since it caused us so much grief. https://bugzilla.redhat.com/show_bug.cgi?id=512552 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110413/2c378e92/attachment-0005.html>