From: Martin Steigerwald <Martin@lichtvoll.de>
To: "linux-btrfs" <linux-btrfs@vger.kernel.org>
Subject: Safe fsck / consistent backup while mounted
Date: Sat, 4 Jun 2011 12:25:55 +0200 [thread overview]
Message-ID: <201106041225.56028.Martin@lichtvoll.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
Hi!
In mailing list debian-user-german we are discussing safe ways to do a
fsck when mounted.
I tested with Ext4 that fsck -nf works either with mount -o remount,ro or
fsfreeze -f while writing with:
I=0; while true ; let I=I+1 ; do touch /boot/test$I ; sleep 0.2 ; done
In the read only mount case the write application returns errors, in the
fsfreeze case Linux kernel stacks the changes in memory, but the fsck
reports no errors like it should.
Now I thought about a way to safely backup a MySQL or other database -
without long service interruption:
- Tell DB to turn itself into consistent state and freeze there
- sync / btrfs filesystem sync ; fsfreeze -f /mountpoint
- btrfs subvolume snapshot
- fsfreeze -u /mountpoint
- Tell DB to continue business as usual
My questions are:
1) Would this work?
2) Is the sync needed? And if so how to avoid the race condition between
the sync and the fsfreeze invocation? Reading from the fsfreeze manpage I
understand that fsfreeze allows all ongoing transactions to complete. But
does that include everything what sync would bring to disk?
3) Is the fsfreeze needed at all? Does btrfs subvolume freeze the
filesystem prior to the snapshot? The manpage doesn´t tell it.
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2011-06-04 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 10:25 Martin Steigerwald [this message]
2011-06-04 14:13 ` Safe fsck / consistent backup while mounted Arne Jansen
2011-06-04 16:07 ` Calvin Walton
2011-06-05 7:58 ` David Pottage
-- strict thread matches above, loose matches on Subject: below --
2011-06-04 13:46 Tomasz Chmielewski
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=201106041225.56028.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.