From: Stuart Rowan <strr-debian@decisionsoft.co.uk>
To: xfs@oss.sgi.com
Subject: xfs_freeze -f misbehaving under lenny / xfsprogs 2.9.8
Date: Mon, 30 Mar 2009 11:30:04 +0100 [thread overview]
Message-ID: <49D09F2C.8060406@decisionsoft.co.uk> (raw)
Hi,
We have a backup script running on another machine that ssh's in to the
affected server and does the following:
mkdir -p /tmp/foo;
/usr/sbin/xfs_freeze -f /home;
/sbin/lvcreate -s -L 20G -n snap-shot home ;
/usr/sbin/xfs_freeze -u /home;
mount -o nouuid,ro /dev/data/snap-shot /tmp/foo;
It then rsyncs (over ssh) the data to the backup store from /tmp/foo
The above command set hangs at running "/sbin/lvcreate -s -L 20G -n
snap-shot home;"
All I/O to /home is of course blocked at this point so for example exim
starts queueing up all the mail.
As soon as I manually log in some hours later and run /usr/sbin/xfs_freeze
-u /home; ... the lvcreate succeeds, the backup runs etc.
We recently upgraded this server to lenny from etch. It is still using the
same kernel as it did with etch. The kernel is 2.6.26-bpo.1-amd64.
So this has never happened before and it occurring directly coincides with
my upgrade to lenny on Friday.
The error occurred on Friday night
Backup proceeded normally on Saturday night
The error occurred on Sunday night
This suggests to me that there's some sort of race going on?
Previous version of xfsprogs (using etch): 2.8.11-1
Current version of xfsprogs (using lenny): 2.9.8-1lenny1
Anyone have any thoughts / is this a known issue with the 2.9.8 release?
Kind regards,
Stu.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-03-30 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 10:30 Stuart Rowan [this message]
2009-03-30 13:45 ` xfs_freeze -f misbehaving under lenny / xfsprogs 2.9.8 Eric Sandeen
2009-03-30 13:58 ` Stuart Rowan
2009-03-30 14:11 ` Eric Sandeen
2009-03-31 12:34 ` Michael Monnerie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49D09F2C.8060406@decisionsoft.co.uk \
--to=strr-debian@decisionsoft.co.uk \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox