linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Spelic <spelic@shiftmail.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Peter Stuge <peter@stuge.se>,
	Alexey A Nikitin <moonwalker@syrius.us>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS fsck tool
Date: Sat, 12 Mar 2011 23:49:52 +0100	[thread overview]
Message-ID: <4D7BF890.5010601@shiftmail.org> (raw)
In-Reply-To: <1299762048-sup-3940@think>

On 03/10/2011 02:02 PM, Chris Mason wrote:
> Cutting the power isn't problem unless you're using something
> where cache flushes are not supported.

Some disks lie about cache flush having completed.

But why doesn't the option for mounting with an earlier superblock work?
Could you improve that area?

I think that, except on "near to enospc" situations, the new blocks
being allocated for FS operation should have been free for a while, at
least one hour (*). In this way new filesystem operations would not
overwrite old superblocks and old data structures and these would remain
readable to get a consistent "old version" of the filesystem.
So in case of abrupt poweroff and wrong flush mechanism, the user could
still mount with an, e.g., 10-minutes older superblock and get a
workable 10-minutes older version of the filesystem.
Or am I missing something?

(*) 1 hour would render highly unlikely that data stays for that long
uncommitted in the drive's writeback cache. The drive flushes all data
out whenever it's idle...

Thank you

  parent reply	other threads:[~2011-03-12 22:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 23:59 BTRFS fsck tool Alexey A Nikitin
2011-03-05  0:05 ` cwillu
2011-03-05  1:20   ` Alexey A Nikitin
2011-03-05  3:00     ` cwillu
2011-03-05  3:27       ` Alexey A Nikitin
2011-03-05  7:12 ` Helmut Hullen
2011-03-05 10:55   ` Alexey A Nikitin
2011-03-08  2:17 ` Spelic
2011-03-08  4:52   ` Alexey A Nikitin
2011-03-08  6:52     ` Peter Stuge
2011-03-10 12:21       ` Clemens Eisserer
2011-03-10 13:02       ` Chris Mason
2011-03-10 13:29         ` Peter Stuge
2011-03-10 13:58           ` Chris Mason
2011-03-10 17:30         ` Alexey A Nikitin
2011-03-10 17:41           ` Chris Mason
2011-03-12 22:49         ` Spelic [this message]
2011-03-12 23:53           ` Ric Wheeler
2011-03-15 14:18             ` Hubert Kario
2011-03-15 14:22               ` Peter Stuge

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=4D7BF890.5010601@shiftmail.org \
    --to=spelic@shiftmail.org \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=moonwalker@syrius.us \
    --cc=peter@stuge.se \
    /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;
as well as URLs for NNTP newsgroup(s).