From: Jack Byer <ojbyer@usa.net>
To: reiserfs-list@namesys.com
Subject: reiser4 resize
Date: Mon, 18 Sep 2006 20:12:14 -0500 [thread overview]
Message-ID: <eeng4b$i68$1@sea.gmane.org> (raw)
Short summary: Will a resize program for reiser4 be available within the
next six months?
Long explanation:
I use a 3ware SATA raid card for the main storage on my home network. I
currently have 8 250 GB drives in a raid 5 + hot spare configuration. I
chose this card because it allows for online capacity expansion. My
plan was to wait until a few generations of hard drives emerged then
upgrade them one at a time in cycles. This way my storage will
periodically expand without any major downtime.
When I first created the filesystem, there was a reiser4 resize program.
This is no longer the case.
I've began my next upgrade cycle with the purchase of two 750 GB drives.
I plan to buy one each month until all eight are replaced. Now I need to
make a decision. Do I backup my raid onto the new drives and reformat my
raid with another filesystem (xfs, reiser3, jfs), or do I put these new
drives into the array and assume that when the time comes to resize the
filesystem that a working program will exist?
next reply other threads:[~2006-09-19 1:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 1:12 Jack Byer [this message]
2006-09-19 13:23 ` reiser4 resize Vladimir V. Saveliev
2006-09-19 17:54 ` David Masover
2006-09-20 7:39 ` Alexey Polyakov
[not found] ` <op.tf52pansd4os1z@localhost>
2006-09-20 9:00 ` Alexey Polyakov
2006-09-21 7:30 ` David Masover
2006-09-21 7:49 ` Łukasz Mierzwa
2006-09-21 7:52 ` Łukasz Mierzwa
2006-09-21 7:48 ` David Masover
2006-09-20 1:09 ` Jack Byer
-- strict thread matches above, loose matches on Subject: below --
2008-01-25 14:38 Reiser4 resize Oleg Osovitskiy
2008-01-30 20:40 ` Edward Shishkin
2008-03-02 22:39 No space left on rfs4 Christopher Sawtell
2008-03-03 20:59 ` Reiser4 resize John
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='eeng4b$i68$1@sea.gmane.org' \
--to=ojbyer@usa.net \
--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 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).