[Top] [All Lists]

Occassional problems with unfreeze

To: xfs@xxxxxxxxxxx
Subject: Occassional problems with unfreeze
From: Hrishikesh Barua <talonx@xxxxxxxxx>
Date: Wed, 16 Jul 2014 16:50:22 +0530
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=hxVbuTjrq80JwOdcbXQNtitzijtoGGcO1ZfLu8QssPE=; b=U/HXV3MDlEOsOmd0bCsEs8QyTnf2jmjuSHbd/fyNTix8Vd5Nul0CSjNdw/yVrylpIh p3SvkdWBNU1DuHSBtWUP7PNKCLREIoVpfPezj14+kNzpR6NZXcg0nVKd+waCdXGm3W3D DhOAmrMfgUu3XIWcCjbFLpvdntIeauJ6qgjr8fAsmqtnGU5yoK3a3DR9W7Aj0DL9iXgF JpX+e2/wbdUOa2ThhW1hn2NULFS6HeEVp3lXul+v1UnCZP65mWuTyfzh2zBOoYjmPeug xrc8N6IA9JPMg6Y698A5DHgOoxSCVDYNLxQE9z3QziZnq7tVkBJ/FVKD/M9YkM4KIRHZ sEqw==
We use XFS on Amazon EBS on Ubuntu 12.04.3, kernel "3.2.0-54-virtual".

Our backup scripts invoke "xfs_freeze -f" before taking a snapshot to ensure filesystem consistency. After the snapshot is taken, we invoke "xfs_freeze -u".

Recently, we have observed that some of these unfreeze calls exit with code 255. This results in a frozen filesystem, processes queuing up and us having to reboot the EC2 instance. Invoking freeze -u manually results in multiple processes like this -

ÂÂÂÂ 17628 ?ÂÂÂÂÂÂÂ DÂÂÂÂÂ 0:00 /usr/sbin/xfs_io -F -r -p xfs_freeze -x -c thaw /mysql-vol-a
ÂÂÂÂ 17694 ?ÂÂÂÂÂÂÂ DÂÂÂÂÂ 0:00 /usr/sbin/xfs_io -F -r -p xfs_freeze -x -c thaw /mysql-vol-a

A search on this list reveals at least one other instance of this problem - http://oss.sgi.com/archives/xfs/2013-01/msg00437.html

No resolution seems to have happened there. Is this a known bug, or has it been fixed since (I'm running xfsprogs 3.1.7) ?

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