mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: venom@sns.it
Cc: Christoph Hellwig <hch@infradead.org>,
	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: Thu, 29 Jan 2004 23:52:40 +0100	[thread overview]
Message-ID: <20040129225240.GA3118@hh.idb.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.43.0401281021030.31225-100000@cibs9.sns.it>

On Wed, Jan 28, 2004 at 10:24:14AM +0100, venom@sns.it wrote:
> 
> 
> On Tue, 27 Jan 2004, Christoph Hellwig wrote:
> >
> > Yes, it does.  But JFS should get the right size from the gendisk anyway.
> > Or did you create the raid with the filesystem already existant?  While that
> > appears to work for a non-full ext2/ext3 filesystem it's not something you
> > should do because it makes the filesystem internal bookkeeping wrong and
> > you'll run into trouble with any filesystem sooner or later.
> >
> 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...
> 
If you need to mirror it - then you have an empty mirror disk ready, right?
Create a degraded array on the mirror disk, then make a fs there. Then
copy everything over from the original partition.  After this, change
the original partition to raid and add it to the other array. (It will
then be updated from the copy). 


This approach works with all filesystems, including those that
cannot be resized.  Data is copied twice instead of once, but
teh copying step will defragment files and you have the option
of changing filesystem or take advantage of sparse files if
you so wish.

Helge Hafting

      parent reply	other threads:[~2004-01-29 22:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 19:15 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
2004-01-28 16:29             ` venom
2004-01-28 10:54           ` Jakob Oestergaard
2004-01-29 22:52           ` Helge Hafting [this message]

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=20040129225240.GA3118@hh.idb.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=florian.huber@mnet-online.de \
    --cc=hch@infradead.org \
    --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

all inboxes | Powered by JetHome®