Am Freitag, 7. September 2012 schrieb Bob Proulx: > Unfortunately I have some recent FUD concerning xfs. I have had some > recent small idle xfs filesystems trigger kernel watchdog timer > recoveries recently. Emphasis on idle. Active filesystems are always > fine. I used /tmp as a large xfs filesystem but swapped it to be ext4 > due to these lockups. Squeeze. Everything current. But when idle it > would periodically lock up and the only messages in the syslog and on > the system console were concerning xfs threads timed out. When the > kernel froze it always had these messages displayed[1]. It was simply > using /tmp as a hundred gig or so xfs filesystem. Doing nothing but > changing /tmp from xfs to ext4 resolved the problem and it hasn't seen > a kernel lockup since. I saw that problem on three different machines > but effectively all mine and very similar software configurations. > And by kernel lockup I mean unresponsive and it took a power cycle to > free it. > > I hesitated to say anything because of lacking real data but it means > I can't completely recommend xfs today even though I have given it > strong recommendations in the past. I am thinking that recent kernels > are not completely clean specifically for idle xfs filesystems. > Meanwhile active ones seem to be just fine. Would love to have this > resolved one way or the other so I could go back to recommending xfs > again without reservations.
Squeeze and everything current? No way. At least when using 2.6.32 default squeeze kernel. Its really old. Did you try with the latest 3.2 squeeze-backports kernel? -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201209082013.01653.mar...@lichtvoll.de
