From: Tim Walberg <twalberg@mindspring.com>
To: "Karsten Römke" <biermann-roemke@onlinehome.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: big fault :-)
Date: Wed, 12 Oct 2005 09:41:33 -0500 [thread overview]
Message-ID: <20051012144133.GK2870@mindspring.com> (raw)
In-Reply-To: <434D18EF.6060507@onlinehome.de>
In order to do that, the file system that lives on the RAID device
has to support being shrunk first, which is possible in some cases,
but far from all. Typically this would involve dumping the data
somewhere, shrinking the RAID, then re-creating a filesystem and
moving the data back...
tw
On 10/12/2005 16:08 +0200, Karsten Römke wrote:
>> By the way: is it possible to make a raid1 array SMALLER?
>> I found hints howto get it bigger and the way seems very easy, but
>> to shrink it? Reason: When I set up the server I have some people behind
>> me, who mostly say: can't it be faster? - so I accepted the partions which
>> are
>> recommended by Suse (and which are not really suitable for my needs)
>>
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
End of included message
--
+--------------------------+------------------------------+
| Tim Walberg | twalberg@mindspring.com |
| 830 Carriage Dr. | www.mindspring.com/~twalberg |
| Algonquin, IL 60102 | |
+--------------------------+------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-10-12 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 16:26 big fault :-) Karsten Römke
2005-10-12 9:41 ` danci
2005-10-12 14:08 ` Karsten Römke
2005-10-12 14:41 ` Tim Walberg [this message]
2005-10-12 14:39 ` Dan Stromberg
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=20051012144133.GK2870@mindspring.com \
--to=twalberg@mindspring.com \
--cc=biermann-roemke@onlinehome.de \
--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 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.