From: Hans Reiser <reiser@namesys.com>
To: JP Howard <jh_lists@fastmail.fm>
Cc: Russell Coker <bofh@coker.com.au>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: back up to disk
Date: Wed, 16 Oct 2002 05:15:33 +0400 [thread overview]
Message-ID: <3DACBDB5.9020303@namesys.com> (raw)
In-Reply-To: 20021015224213.4BBAA1AEC13E@server5.fastmail.fm
JP Howard wrote:
>We've been thinking about something like that, using this extremely nifty
>trick:
>
>http://www.mikerubel.org/computers/rsync_snapshots/
>
This is brilliantly simple.
>
>Back in the old days (i.e. last week) when we were planning around Ext3,
>we were thinking of combining it with this product:
>
>http://www.shaolinmicro.com/product/cogofs/index.php
>
This looks reasonable as a product, and not unreasonably expensive for
servers. There are some advantages to tight integration though, in
that you can compress at flush time.
>
>The two combined, with ATA RAID, provide fast, redundent, incremental,
>compressed backups.
>
>Does ReiserFS support transparent compression?
>
This is one of the features that won't make the Halloween deadline, but
might be slipped in later.
> If not, are there any
>plans in this direction? Benchmarks I've seen in the past suggest that
>compressed file systems generally improve performance (especially when
>using something fast like LZOP) since CPUs are so fast--and of course for
>backups being able to store more on fewer disks is nice...
>
What I had heard was that they generally slowed peformance, but maybe my
info is old.
CPUs are faster now, and maybe compression algorithms are faster.
Can you give more details?
next prev parent reply other threads:[~2002-10-16 1:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 22:42 back up to disk JP Howard
2002-10-16 1:15 ` Hans Reiser [this message]
2002-10-16 4:05 ` Valdis.Kletnieks
2002-10-16 6:19 ` Toby Dickenson
-- strict thread matches above, loose matches on Subject: below --
2002-10-16 2:15 JP Howard
2002-10-16 17:29 ` Edward Shishkin
2002-10-15 21:17 Bingner Sam J Contractor CAF CSS/SCHE
2002-10-15 21:05 Russell Coker
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=3DACBDB5.9020303@namesys.com \
--to=reiser@namesys.com \
--cc=bofh@coker.com.au \
--cc=jh_lists@fastmail.fm \
--cc=reiserfs-list@namesys.com \
/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.