From: Roman Mamedov <rm@romanrm.ru>
To: helmut@hullen.de
Cc: Hullen@t-online.de, linux-btrfs@vger.kernel.org
Subject: Re: kernel 3.3.4 damages filesystem (?)
Date: Wed, 9 May 2012 02:56:46 +0600 [thread overview]
Message-ID: <20120509025646.2894f7ea@natsu> (raw)
In-Reply-To: <C8TGo1T9CXB@helmut.hullen.de>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On 08 May 2012 22:19:00 +0200
Hullen@t-online.de (Helmut Hullen) wrote:
> What I still hope (may be it's impossible): when 1 disk/partition fails,
> then the contents of the other disks is "somehow" restorable. And not
> irreproducable.
You should look for file/directory-level tree merging, e.g. this FUSE based
virtual FS:
https://romanrm.ru/en/mhddfs
Or various other unionfs'es, some of which are kernel-based.
Regarding btrfs, AFAIK even "btrfs -d single" suggested above works not "per
file", but per allocation extent, so in case of one disk failure you will lose
random *parts* (extents) of random files, which in effect could mean no file
in your whole file system will remain undamaged.
--
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:[~2012-05-08 20:56 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 10:46 kernel 3.3.4 damages filesystem (?) Helmut Hullen
2012-05-07 10:58 ` Fajar A. Nugraha
2012-05-07 12:06 ` Helmut Hullen
2012-05-07 10:59 ` Hugo Mills
2012-05-07 12:15 ` Helmut Hullen
2012-05-07 13:34 ` Helmut Hullen
2012-05-07 14:05 ` Hugo Mills
2012-05-07 16:36 ` Helmut Hullen
2012-05-07 17:13 ` Felix Blanke
2012-05-07 17:52 ` Helmut Hullen
2012-05-07 18:00 ` Hugo Mills
2012-05-07 18:25 ` Helmut Hullen
2012-05-07 18:44 ` Hugo Mills
2012-05-09 13:04 ` failed disk (was: kernel 3.3.4 damages filesystem (?)) Helmut Hullen
2012-05-09 13:19 ` Hugo Mills
2012-05-09 14:25 ` Helmut Hullen
2012-05-09 14:37 ` Hugo Mills
2012-05-09 15:14 ` failed disk Helmut Hullen
2012-05-09 15:33 ` Hugo Mills
2012-05-09 18:49 ` Helmut Hullen
2012-05-09 16:13 ` failed disk (was: kernel 3.3.4 damages filesystem (?)) Ilya Dryomov
2012-05-10 2:49 ` failed disk Helmut Hullen
2012-05-07 19:30 ` kernel 3.3.4 damages filesystem (?) Daniel Lee
2012-05-07 20:21 ` Helmut Hullen
2012-05-07 20:51 ` Daniel Lee
2012-05-07 21:17 ` Helmut Hullen
2012-05-07 21:27 ` cwillu
2012-05-07 22:07 ` Martin Steigerwald
2012-05-08 7:39 ` Helmut Hullen
2012-05-08 7:44 ` Fajar A. Nugraha
2012-05-08 10:00 ` Helmut Hullen
2012-05-08 10:41 ` Clemens Eisserer
2012-05-08 13:13 ` Helmut Hullen
2012-05-08 13:44 ` Felix Blanke
2012-05-08 13:52 ` Hugo Mills
2012-05-08 16:53 ` Helmut Hullen
2012-05-08 17:24 ` Felix Blanke
2012-05-08 18:29 ` Helmut Hullen
2012-05-08 18:41 ` Felix Blanke
2012-05-08 19:12 ` David Sterba
2012-05-08 19:34 ` Helmut Hullen
2012-05-08 20:02 ` Hugo Mills
2012-05-08 20:19 ` Helmut Hullen
2012-05-08 20:56 ` Roman Mamedov [this message]
2012-05-09 14:46 ` Kaspar Schleiser
2012-05-10 10:40 ` Martin Steigerwald
2012-05-10 11:55 ` feature request (was: kernel 3.3.4 damages filesystem (?)) Helmut Hullen
2012-05-10 19:43 ` kernel 3.3.4 damages filesystem (?) Hubert Kario
2012-05-10 20:15 ` Hugo Mills
2012-05-10 20:23 ` Hubert Kario
2012-05-08 21:42 ` Hubert Kario
2012-05-07 12:53 ` Liu Bo
2012-05-09 17:32 ` Duncan
2012-05-09 18:06 ` Atila
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=20120509025646.2894f7ea@natsu \
--to=rm@romanrm.ru \
--cc=Hullen@t-online.de \
--cc=helmut@hullen.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 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).