All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wendy Cheng <s.wendy.cheng@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Maximilian Wilhelm <max@rfc2324.org>,
	linux clustering <linux-cluster@redhat.com>
Subject: Re: [linux-lvm] Distributed LVM/filesystem/storage
Date: Sun, 01 Jun 2008 08:50:26 -0500	[thread overview]
Message-ID: <4842A922.6040102@gmail.com> (raw)
In-Reply-To: <20080601070726.GK19431@lug-owl.de>

Jan-Benedict Glaw wrote:
> On Sat, 2008-05-31 23:12:21 -0500, Wendy Cheng <s.wendy.cheng@gmail.com> wrote:
>   
>> Jan-Benedict Glaw wrote:
>>     
>>> On Fri, 2008-05-30 09:03:35 +0100, Gerrard Geldenhuis <Gerrard.Geldenhuis@datacash.com> wrote:
>>>       
>>>> On Behalf Of Jan-Benedict Glaw
>>>>         
>>>>> I'm just thinking about using my friend's overly empty harddisks for a
>>>>> common large filesystem by merging them all together into a single,
>>>>> large storage pool accessible by everybody.
>>>>>           
>>> [...]
>>>  
>>>       
>>>>> It would be nice to see if anybody of you did the same before (merging
>>>>> the free space from a lot computers into one commonly used large
>>>>> filesystem), if it was successful and what techniques
>>>>> (LVM/NBD/DM/MD/iSCSI/Tahoe/Freenet/Other P2P/...) you used to get there,
>>>>> and how well that worked out in the end.
>>>>>           
>>>> Maybe have a look at GFS.
>>>>         
>>> GFS (or GFS2 fwiw) imposes a single, shared storage as its backend. At
>>> least I get that from reading the documentation. This would result in
>>> merging all the single disks via NBD/LVM to one machine first and
>>> export that merged volume back via NBD/iSCSI to the nodes. In case the
>>> actual data is local to a client, it would still be first send to the
>>> central machine (running LVM) and loaded back from there. Not as
>>> distributed as I hoped, or are there other configuration possibilities
>>> to not go that route?
>>>       
>>                         However, with its symmetric architecture, 
>> nothing can prevent it running on top of a group of iscsi disks (with 
>> GFS node as initiator), as long as each node can see and access these 
>> disks. It doesn't care where the iscsi targets live, nor how many there 
>> are.
>>     
>
> So I'd configure each machine's empty disk/partition as an iSCSI
> target and let them show up an every "client" machine and run that
> setup. How good will GFS deal with temporary (or total) outage of
> single targets? Eg. 24h disconnects with ADSL connectivity etc.?
>
>   
High availability will not work well in this particular setup - it is 
more about data and storage sharing between GFS nodes.

Note that GFS normally runs on top of CLVM (clustered lvm, in case you 
don't know about it). You might want to check current (Linux) CLVM raid 
level support to see whether it fits your needs. 
 

-- Wendy

  reply	other threads:[~2008-06-01 13:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29 23:12 [linux-lvm] Distributed LVM/filesystem/storage Jan-Benedict Glaw
2008-05-30  8:03 ` Gerrard Geldenhuis
2008-05-31  7:03   ` Jan-Benedict Glaw
2008-06-01  0:42     ` Stuart D. Gathman
2008-06-01 18:26       ` David Brown
2008-06-01  4:12     ` Wendy Cheng
2008-06-01  7:07       ` Jan-Benedict Glaw
2008-06-01 13:50         ` Wendy Cheng [this message]
2008-06-01 15:56           ` Jan-Benedict Glaw
2008-06-01 21:09 ` Hannes Dorbath
2008-06-01 23:00   ` Jan-Benedict Glaw
2008-06-02 13:01     ` Greg Freemyer

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=4842A922.6040102@gmail.com \
    --to=s.wendy.cheng@gmail.com \
    --cc=linux-cluster@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=max@rfc2324.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.