Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_log

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_log_force\:\s+error\s+5\s+returend\s*$/: 4 ]

Total 4 documents matching your query.

1. xfs_log_force: error 5 returend (score: 1): Author: "Steffen Knauf" <Steffen.Knauf@xxxxxxx>; Date: Mon, 14 Sep 2009 12:05:48 +0200; hello, sometimes, our server crashed with xfs_log_force: error 5. It isn't reproducible and a xfs_check / xfs_repair don't find some errors. Perhaps it's a bug? Version: Linux version 2.6.26-bpo.1-am; /archives/xfs/2009-09/msg00135.html (6,184 bytes)
2. Re: xfs_log_force: error 5 returend (score: 1): Author: Tomek Kruszona <bloodyscarion@xxxxxxxxx>; Date: Mon, 14 Sep 2009 17:09:31 +0200; Hello! Look at http://oss.sgi.com/bugzilla/show_bug.cgi?id=840 Please provide your dmesg output regarding kernel oops message (maybe there is similar issue in your case as I had) It seems that in my; /archives/xfs/2009-09/msg00136.html (9,533 bytes)
3. Re: xfs_log_force: error 5 returend (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Mon, 14 Sep 2009 12:41:38 -0400; Error 5 is EIO, and xfs_log_force basically passed the error through from the underlying device. Most likely it is an issue with the underlying storage device.; /archives/xfs/2009-09/msg00137.html (7,080 bytes)
4. Re: xfs_log_force: error 5 returend (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Mon, 14 Sep 2009 12:46:40 -0500; Also, just to be semantically correct, it's unlikely that this was a "server crash" - most likely you got an IO error, xfs noticed it, and shut itself down for safety. -Eric; /archives/xfs/2009-09/msg00138.html (7,952 bytes)

Current List: 1 - 4
Page: [1]