From: Christoph Hellwig <hch@infradead.org>
To: venom@sns.it
Cc: Dave Kleikamp <shaggy@austin.ibm.com>,
Florian Huber <florian.huber@mnet-online.de>,
JFS Discussion <jfs-discussion@www-124.southbury.usf.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Jfs-discussion] md raid + jfs + jfs_fsck
Date: Wed, 28 Jan 2004 09:38:51 +0000 [thread overview]
Message-ID: <20040128093851.A26131@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.43.0401281021030.31225-100000@cibs9.sns.it>; from venom@sns.it on Wed, Jan 28, 2004 at 10:24:14AM +0100
On Wed, Jan 28, 2004 at 10:24:14AM +0100, venom@sns.it wrote:
> In most situation to create a new FS on a RAID1 MD is not an option.
> It happens that you have to mirror a partition, maybe alarge one, and it
> already had a filesystem on top of it. Then what should you do?
> backup, mirror and then restore? Sometimes it is not possible this too.
> Then you accept to deal with the possible problems...
Then you need to shrink the filesystem. As long as the space isn't used
yet it's rather trivial for most ondisk formats, but you absolutely need
to do it to be safe.
next prev parent reply other threads:[~2004-01-28 9:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 19:15 md raid + jfs + jfs_fsck Florian Huber
2004-01-27 19:28 ` [Jfs-discussion] " Dave Kleikamp
2004-01-27 19:39 ` Florian Huber
2004-01-27 19:52 ` Florian Huber
2004-01-27 20:43 ` Dave Kleikamp
2004-01-27 20:53 ` Christoph Hellwig
2004-01-27 21:19 ` Florian Huber
2004-01-27 21:22 ` Christoph Hellwig
2004-01-27 23:39 ` Neil Brown
2004-01-27 21:47 ` Gene Heskett
2004-01-28 2:47 ` Theodore Ts'o
2004-01-28 9:24 ` venom
2004-01-28 9:38 ` Christoph Hellwig [this message]
2004-01-28 16:29 ` venom
2004-01-28 10:54 ` Jakob Oestergaard
2004-01-29 22:52 ` Helge Hafting
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=20040128093851.A26131@infradead.org \
--to=hch@infradead.org \
--cc=florian.huber@mnet-online.de \
--cc=jfs-discussion@www-124.southbury.usf.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@austin.ibm.com \
--cc=venom@sns.it \
/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