From: Steve <gentoo_sjh@shic.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 20:46:20 +0000 [thread overview]
Message-ID: <4B9FEE1C.7050309@shic.co.uk> (raw)
In-Reply-To: <25EC8AD5-9178-4556-AB64-6069AAB40845@stellar.eclipse.co.uk>
On 16/03/2010 19:57, Stroller wrote:
> 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.
Well, at the moment, I don't have a RAID system... A flash drive (USB
key) seems a reasonable strategy - I could even have two containing
identical data - so, if the first were to fail then the second would
kick in - if not automatically - then after the duff flash-drive is
removed. A neat side effect of this would be to eliminate a moving part
on the server - making it quieter... and the drives themselves can be
located at two physically remote places on my LAN.
>>> 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.
> If you do not need data sharing (i.e. if your volumes are only mounted
Yes - I don't think I'd need sharing. It strikes me that it should be
possible to have a 'live' backup server which just reads until
fail-over... with a different /var/* - of course.
> 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.
You could, but the advantage of ZFS is the efficiency of snap-shots.
With your strategy I'd need to process all of the large file every time
I want to make a snapshot... which, even for a mere 100gig, won't be quick.
next prev parent reply other threads:[~2010-03-16 20:46 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
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 [this message]
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=4B9FEE1C.7050309@shic.co.uk \
--to=gentoo_sjh@shic.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