linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rich <rich@pcfusion.co.uk>
To: Rich <rich@pcfusion.co.uk>
Cc: gmccullagh@gmail.com, linux-raid@vger.kernel.org
Subject: Re: LINEAR RAID, little help
Date: Thu, 12 Apr 2007 08:58:00 +0100	[thread overview]
Message-ID: <461DE688.4070808@pcfusion.co.uk> (raw)
In-Reply-To: <461DE4CA.9020406@pcfusion.co.uk>

I forgot to ask something, sorry. With RAID0 and all the odd size drives 
I have I'd get a lot of left over unused space. Is there anyway to make 
use of this slack?

Thanks,

Rich

Rich wrote:
> Neil Brown wrote:
>> (This is maybe sort of off topic since this list about raid and not
>> filesystems and virtual such either.)
>>
>> Maybe you just want the appearance of things being as one volume? I
>> might recommend you looking into unionfs:
>>
>> http://www.filesystems.org/project-unionfs.html
>>
>> It's actually quite useful. You might have some logical division of the
>> data. Put TV stuff on one disk, Movies on another. The unionfs overlay
>> maps everything together into a virtual bigdisk. It's also very simple
>> and no superblocks or headers needed either.
> Thanks I shall take a look into it :)
>>
>> Linux raid0 works with varying sized drives without problem.   
> Ah, kewl.. I might do, depends how much drive space I loose. Speed 
> wise I don't find linear to bad I can read and write over gigabit 
> network at around 30mb/sec.
>>
>> If you lose one drive, you should consider that you have lost the
>> whole array.  You might be able to recover some data, if you are lucky
>> and spend a lot of time hunting for it.  But it is quite unlikely that
>> you will get much that is useful.
>>
>>   
> Ah right, well for the time being A lot of my friends have the same 
> data so loosing it is just inconvenient rather than a major no-go.
>>
>> The man page is out of date.  With reasonably recent kernel/mdadm you
>> can
>>   mdadm --grow /dev/mdX --add /dev/sdY
>>
>> To add a drive to a linear array.  You then need to grow the
>> filesystem of course.
>>
>> But yes:  A big linear array is good for scratch space, but I wouldn't
>> want to store data that I couldn't afford to lose.
>>
>> NeilBrown
>>   
> Cheers Neil, Once I can find enough hdd space else where to backup I 
> might play around with RAID0 etc I do plan to replace my odd size 
> drives with 500GB ones and RAID5 but I can't afford that at the moment.
>
>
> Thanks,
>
> Rich
>
>
>
>
>


  parent reply	other threads:[~2007-04-12  7:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-07 11:17 LINEAR RAID, little help Rich
2007-04-07 17:33 ` Gavin McCullagh
2007-04-07 18:41   ` Rich
2007-04-07 20:34     ` Gavin McCullagh
2007-04-10 21:49       ` Henrik Holst
2007-04-10 23:12     ` Neil Brown
     [not found]       ` <461DE4CA.9020406@pcfusion.co.uk>
2007-04-12  7:58         ` Rich [this message]
2007-04-12  8:08           ` Neil Brown
2007-04-12 11:19             ` matt s.
2007-04-12 14:55             ` 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=461DE688.4070808@pcfusion.co.uk \
    --to=rich@pcfusion.co.uk \
    --cc=gmccullagh@gmail.com \
    --cc=linux-raid@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).