From: John Robinson <john.robinson@anonymous.org.uk>
To: Maxime Boissonneault <maxime.boissonneault@usherbrooke.ca>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID5 reconstruction ?
Date: Sat, 30 May 2009 16:46:13 +0100 [thread overview]
Message-ID: <4A2154C5.6050500@anonymous.org.uk> (raw)
In-Reply-To: <4A213D6B.8040501@usherbrooke.ca>
On 30/05/2009 15:06, Maxime Boissonneault wrote:
> I don't know how it goes for Linux, but hasn't ZFS been developped
> exactly for that purpose ? From what I understand, ZFS manage both the
> file system and the RAID features at once. Therefore, the "raid" part
> knows where are the files and the filesystem knows about the raid.
> Reconstruction is then done intelligently (not reconstructing unused
> space).
Yes, ZFS can do this, but ext4 and md could do it too, and probably will
at some point. I prefer separating the layers, then I can switch one and
not the other, e.g. start using a hardware RAID controller instead of md.
Cheers,
John.
next prev parent reply other threads:[~2009-05-30 15:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 5:44 RAID5 reconstruction ? SandeepKsinha
2009-05-30 12:52 ` Sujit Karataparambil
2009-05-30 13:28 ` SandeepKsinha
2009-05-30 13:31 ` Sujit Karataparambil
2009-06-09 4:13 ` Nifty Fedora Mitch
2009-05-30 13:35 ` John Robinson
2009-05-30 14:06 ` Maxime Boissonneault
2009-05-30 15:46 ` John Robinson [this message]
2009-05-30 16:16 ` Maxime Boissonneault
2009-05-30 16:30 ` John Robinson
2009-05-30 16:08 ` Redeeman
2009-05-30 18:39 ` Bill Davidsen
2009-05-30 18:54 ` Goswin von Brederlow
2009-05-31 8:10 ` SandeepKsinha
2009-05-30 18:55 ` Goswin von Brederlow
2009-05-30 19:37 ` Redeeman
2009-05-31 8:02 ` SandeepKsinha
2009-05-31 11:54 ` Goswin von Brederlow
2009-05-31 12:11 ` John Robinson
2009-05-31 12:14 ` NeilBrown
2009-06-03 1:54 ` Greg Freemyer
2009-06-02 18:42 ` Bill Davidsen
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=4A2154C5.6050500@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=maxime.boissonneault@usherbrooke.ca \
/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).