From: Roman Mamedov <rm@romanrm.ru>
To: "Hervé CHIBOIS" <herve@chibois.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS fsck ?
Date: Tue, 22 Nov 2011 17:45:30 +0600 [thread overview]
Message-ID: <20111122174530.7994058d@natsu> (raw)
In-Reply-To: <4ECB8A60.2020402@chibois.net>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On Tue, 22 Nov 2011 12:41:20 +0100
Hervé CHIBOIS <herve@chibois.net> wrote:
> Hello Team
>
> for personnal use, I'm interested in cosolidating all my ext4
> sub-filesystems into a single one using BTRFS.
>
> I can"t afford loosing my data... and my question is : is there a
> release date for the fsck tool for btrfs ?
The ONLY guard against losing data is having an up-to-date backup, not fsck.
You are absolutely crazy if you store the data you can't afford to lose, without backups, just relying on what currently, ext4 fsck?
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-11-22 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 11:41 BTRFS fsck ? Hervé CHIBOIS
2011-11-22 11:45 ` Roman Mamedov [this message]
2011-11-22 22:31 ` Chris Mason
2011-12-23 16:55 ` Erik Logtenberg
2011-12-29 10:32 ` Gour
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=20111122174530.7994058d@natsu \
--to=rm@romanrm.ru \
--cc=herve@chibois.net \
--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.