From: John Robinson <john.robinson@anonymous.org.uk>
To: Jon@eHardcastle.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Is this likely to cause me problems?
Date: Wed, 22 Sep 2010 12:25:35 +0100 [thread overview]
Message-ID: <4C99E7AF.4090503@anonymous.org.uk> (raw)
In-Reply-To: <672252.64237.qm@web51306.mail.re2.yahoo.com>
On 22/09/2010 07:42, Jon Hardcastle wrote:
[...]
> So do you have any recommendations? I would like to 'trust' the new version of fdisk but I can not risk torpedoing myself. I have 2 more drives I need to 'phase out' at some point; but they will liklely be with 1.5TB drives.
The new layout you've got is meant for SSDs and drives with 4K sectors;
the old layout is fine for you.
> My gut tells me that i should whilst I have other drives the same size use the same paratermeters... then when i have a bigger drive that is definately not going to cause any size issues let fdisk do its magic.
>
> So following that premsis is there any down side to copy the partition table off another drive?
I can't think of one. For backup, if I remember correctly Doug Ledford's
hot-swap auto-rebuilding onto virgin drives work was going to create
partition tables by copying them from existing drives (or by having the
user copy the required partition table from a drive in advance).
Cheers,
John.
next prev parent reply other threads:[~2010-09-22 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 20:33 Is this likely to cause me problems? Jon Hardcastle
2010-09-21 21:15 ` John Robinson
2010-09-21 21:18 ` Jon Hardcastle
2010-09-21 22:34 ` John Robinson
2010-09-22 6:42 ` Jon Hardcastle
2010-09-22 11:25 ` John Robinson [this message]
2010-09-22 14:38 ` Jon Hardcastle
2010-09-23 13:14 ` John Robinson
[not found] <94202.62107.qm@web51304.mail.re2.yahoo.com>
2010-09-22 9:09 ` Tim Small
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=4C99E7AF.4090503@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=Jon@eHardcastle.com \
--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).