[Top] [All Lists]

2.6.31 xfs_fs_destroy_inode: cannot reclaim

To: xfs@xxxxxxxxxxx
Subject: 2.6.31 xfs_fs_destroy_inode: cannot reclaim
From: Tommy van Leeuwen <tommy@xxxxxxxxxxxxxxxx>
Date: Wed, 16 Sep 2009 12:27:21 +0200
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=NNnlC7HklWoZkCGDHf0Y9wHEY+vHFmFroYKSf2ij3ek=; b=xK8YaFD0WyhNteuoQickDWPYNGgqgEtSyF/mTssqtzLYWjfOk7VeWwpCRBS6Bz0H7D fpxgGIsf93bP8y9sZPZmPK0Yoncng5WDYRg0gfliDTIBFdvu8yDbiimLoFyqnatbRSZ5 IkHAD/LGaEBf/92fEUoOKP9/XCOLzSwRWhFf8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=VXT9VZ9YDdw5mymbgsUydk+pS0WE6igAbr7gH+qHbI4Px1kV7jbcaxeyIomzpmZ4GU Ry+e1SGdax0evnh7vFalxTojz7qt7InHDfHJZ1F6/N85pQb4HaVfkEQUeGBR8Z6BZKrQ p5Nn0F7uO/4z+GAYsG4wQ6917qiOBnmGqb9Ew=
Sender: chiparus@xxxxxxxxx
Hello All,

We had this error reported on the list about 1 or 2 months ago. During
that time a lot of fixes were applied. However, we still experience
this problem with the recent 2.6.31 tree. We've also applied an extra
log entry to aid in debugging.

printk("XFS: inode_init_always failed to re-initialize inode\n");

However, we didn't see this logging!

Here's a screenshot of our latest crash:

Here's the config used just in case:

For now we've downgraded to 2.6.28 again. Please let me know if we can
do something to better troubleshoot this. We have a set of 8 servers
which can easily reproduce this. It mostly happens within a few days
after a clean reboot.

Kind Regards,
Tommy van Leeuwen

**Warning** New Addres from May 25th, 2009!
News-Service.com - European Usenet Provider
Pobox 12026, 1100 AA Amsterdam, Netherlands
http://www.news-service.com - +3120-3981111

<Prev in Thread] Current Thread [Next in Thread>