Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+\/\s+xfssyncd\s+lock\-ups\s+on\s+2\.6\.38\-8\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+\/\s+xfssyncd\s+lock\-ups\s+on\s+2\.6\.38\-8\s*$/: 3 ]

Total 3 documents matching your query.

1. XFS / xfssyncd lock-ups on 2.6.38-8 (score: 1): Author: Mike Krieger <mikeyk@xxxxxxxxxxxxx>; Date: Sun, 20 Nov 2011 08:34:02 -0800; We're running a dozen Amazon AWS instances (on Ubuntu Natty Narwhal, kernel 2.6.38-8). We've recent brought up several machines based on some previous snapshots (EBS snapshots, rather than LVM), and; /archives/xfs/2011-11/msg00400.html (8,270 bytes)
2. Re: XFS / xfssyncd lock-ups on 2.6.38-8 (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Sun, 20 Nov 2011 13:32:23 -0500; This was fixed by: xfs: force the log if we encounter pinned buffers in .iop_pushbuf in Linux 3.1. I've also backported it to the 3.0-stable issues. I would recommend to upgrade to the latest Linux 3; /archives/xfs/2011-11/msg00401.html (7,332 bytes)
3. Re: XFS / xfssyncd lock-ups on 2.6.38-8 (score: 1): Author: "Haefliger, Juerg" <Juerg.Haefliger@xxxxxx>; Date: Fri, 13 Apr 2012 11:44:23 +0000; Can this patch be applied to 2.6.38 by itself or does it depend on other things that are not present in 2.6.38? I noticed it's small, applies and compiles but I can't judge if there are other depend; /archives/xfs/2012-04/msg00762.html (7,529 bytes)

Current List: 1 - 3
Page: [1]