Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: sri <toyours_sridhar@yahoo.co.in>
To: linux-btrfs@vger.kernel.org
Subject: btrfs on disk stability
Date: Tue, 26 May 2015 08:45:06 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150526T103943-385@post.gmane.org> (raw)

Hi,

According to btrfs wiki page, under "Stability status" it is written that

"The filesystem disk format is no longer unstable".

Does this mean if there are more I/Os are going on a btrfs file system, 
copy of entire disk (all disk blocks) gives a stable disk?

Just to elaborate more, if btrfs file system is created on 2 disks 
/dev/sda and /dev/sdb and if I start copying blocks of sda and sdb to sdc 
and sdc respectively by just opening file handlers of sda and sdb and 
mounting the new copy via /dev/sdc and /dev/sdd will give consistent file 
system??




             reply	other threads:[~2015-05-26  8:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  8:45 sri [this message]
2015-05-26  8:52 ` btrfs on disk stability Hugo Mills
2015-05-26  9:29   ` sri
2015-05-26 14:26     ` Hugo Mills
2015-05-26 16:26       ` Chris Murphy

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=loom.20150526T103943-385@post.gmane.org \
    --to=toyours_sridhar@yahoo.co.in \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox