public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Strategy for using SAN/NAS for storage with Gentoo...
Date: Tue, 16 Mar 2010 19:57:49 +0000	[thread overview]
Message-ID: <25EC8AD5-9178-4556-AB64-6069AAB40845@stellar.eclipse.co.uk> (raw)
In-Reply-To: <4B9FB29D.7010902@shic.co.uk>


On 16 Mar 2010, at 16:32, Steve wrote:
> ...
>> Given the point above I would also stick with software RAID.
> ...
>> If reliability is your primary concern, I would go for a simple RAID1
>> setup;
> Absolutely.  Software raid is cheaper and implies less hardware to
> fail.  Similarly, RAID1 minimises the total number of disks required  
> to
> survive a failure. It's the only way for me to go.

How does your system boot if your RAID1 system volume fails? The one  
you have grub on? I think you mentioned a flash drive, which I've seen  
mentioned before. This seems sound, but just to point out that's  
another, different, single point of failure.

>> If you do not need data sharing (i.e. if your volumes are only  
>> mounted
>> by one client at a time), the simplest solution is to completely  
>> avoid
>> having a FS on the storage server side -- just export the raw block
>> device via iSCSI, and do everything on the client.
> ...
> Snap-shots, of course, are only really valuable for non-archive  
> data...
> so, in future, I could add a ZFS volume using the same iSCSI strategy.

I have wondered if it might be possible to create a large file (`dd  
if=/dev/zero of=/path/to/large/file` constrain at a size of 20gig or  
100gig or whatever) and treat it as a loopback device for stuff like  
this. It's not true snapshotting (in the ZFS / BTFS sense), but you  
can unmount it and make a copy quite quickly.

Stroller.




  reply	other threads:[~2010-03-16 19:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 13:20 [gentoo-user] Strategy for using SAN/NAS for storage with Gentoo Steve
2010-03-15 14:37 ` [gentoo-user] " Harry Putnam
2010-03-15 15:49   ` Kyle Bader
2010-03-15 16:26     ` Steve
2010-03-15 18:21       ` Stroller
2010-03-15 19:18         ` Steve
2010-03-15 22:29           ` Andrea Conti
2010-03-16 16:32             ` Steve
2010-03-16 19:57               ` Stroller [this message]
2010-03-16 20:04                 ` Neil Bothwick
2010-03-16 20:13                   ` Stroller
2010-03-16 20:44                     ` J. Roeleveld
2010-03-16 21:26                     ` Neil Bothwick
2010-03-17 20:44                       ` Florian Philipp
2010-03-17 21:00                         ` Neil Bothwick
2010-03-18 16:57                           ` Florian Philipp
2010-03-16 20:46                 ` Steve
2010-03-17  0:05               ` [gentoo-user] " Andrea Conti
2010-03-17 13:01   ` [gentoo-user] " Iain Buchanan
2010-03-17  4:57 ` [gentoo-user] " Keith Dart
2010-03-17  8:03   ` Steve

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=25EC8AD5-9178-4556-AB64-6069AAB40845@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.gentoo.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