public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* Occassional problems with unfreeze
@ 2014-07-16 11:20 Hrishikesh Barua
  2014-07-16 12:47 ` Brian Foster
  0 siblings, 1 reply; 6+ messages in thread
From: Hrishikesh Barua @ 2014-07-16 11:20 UTC (permalink / raw)
  To: xfs


[-- Attachment #1.1: Type: text/plain, Size: 938 bytes --]

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) ?

Regards
Hrish

[-- Attachment #1.2: Type: text/html, Size: 1902 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2014-09-26 12:02 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-07-16 11:20 Occassional problems with unfreeze Hrishikesh Barua
2014-07-16 12:47 ` Brian Foster
2014-07-16 13:23   ` Hrishikesh Barua
2014-09-25  6:07     ` Hrishikesh Barua
2014-09-25  7:18       ` Dave Chinner
2014-09-26 12:02         ` Hrishikesh Barua

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox