From: Paul Clements <paul.clements@steeleye.com>
To: Dan Graham <graham@molbio.uoregon.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Converting Ext3 to Ext3 under RAID 1
Date: Wed, 02 Aug 2006 15:31:43 -0400 [thread overview]
Message-ID: <44D0FD9F.9070605@steeleye.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0608021205110.626@molbio.uoregon.edu>
Dan Graham wrote:
> Is this scheme even half-way sane?
Yes. It sounds correct.
> Is 16 blocks a large enough area?
Maybe. The superblock will be between 64KB and 128KB from the end of the
partition. This depends on the size of the partition:
SB_LOC = PART_SIZE - 64K - (PART_SIZE & (64K-1))
So, by 16 blocks, I assume you mean 16 filesystem blocks (which are
generally 4KB for ext3). So as long as your partition ends exactly on a
64KB boundary, you should be OK.
Personally, I would err on the safe side and just shorten the filesystem
by 128KB. It's not like you're going to miss the extra 64KB.
--
Paul
next prev parent reply other threads:[~2006-08-02 19:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-16 0:56 Can't add disk to failed raid array Paul Waldo
2006-07-16 10:19 ` Neil Brown
2006-07-16 12:24 ` Paul Waldo
2006-07-18 5:36 ` Neil Brown
2006-07-23 11:04 ` In Trouble--Please Help! (was Re: Can't add disk to failed raid array) Paul Waldo
2006-07-23 11:25 ` Neil Brown
2006-07-23 11:50 ` Paul Waldo
2006-07-23 11:53 ` Paul Waldo
2006-07-23 11:59 ` Neil Brown
2006-07-23 12:32 ` Paul Waldo
2006-07-24 18:26 ` Dan Williams
2006-07-24 18:35 ` Paul Waldo
2006-07-24 19:06 ` Dan Williams
2006-07-25 14:27 ` Paul Waldo
2006-07-24 23:24 ` Neil Brown
2006-08-02 19:15 ` Converting Ext3 to Ext3 under RAID 1 Dan Graham
2006-08-02 19:28 ` dean gaudet
2006-08-02 19:31 ` Paul Clements [this message]
2006-08-03 7:50 ` Michael Tokarev
2006-08-02 22:38 ` Robert Heinzmann
[not found] ` <200607160913.32005.pwaldo@waldoware.com>
[not found] ` <Pine.LNX.4.62.0607161524170.7520@uplift.swm.pp.se>
2006-07-16 14:39 ` Can't add disk to failed raid array Paul Waldo
2006-07-17 18:36 ` Paul Waldo
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=44D0FD9F.9070605@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=graham@molbio.uoregon.edu \
--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 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).