From: Gilles PIETRI <contact+dev@gilouweb.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup
Date: Wed, 02 Sep 2009 12:12:44 +0200 [thread overview]
Message-ID: <4A9E451C.5010101@gilouweb.com> (raw)
In-Reply-To: <7020fd000909011814m147b1d15xb0219d34d33d31f1@mail.gmail.com>
On 02/09/2009 03:14, solarflow99 wrote:
> can anyone say if this command is needed when resizing a partition?
> What if I just used resize2fs? how could it know about the change of
> size? Also its a shame information like this has to be a secret, no one
> seems to know or say anything about it.
>
> Thanks,
>
I have a question myself that is somehow related.. I do not know much
about the internals of the payload alignment (--align-payload option of
luksFormat), but I thought about something.. Say I have a RAID device of
6 disks, that I have a stripe size of 64K, and that I use
--align-payload (stripe width is 512 blocks here). Fine, should be
aligned with the stripes.
Now, say that I add a disk there and migrate the array over it, the
stripe width will increase to 640 blocks.. but how can I tell luks about
it? Should I? Maybe newly written data could benefit from being aligned
to the new stripe width (and let us say it won't be optimal for older
data, but so be it)?
I know that xfs can then deal with the swidth growth by specifying the
info in the mount options, so once cryptsetup knows about the geometry
change, it should be fine..
Cheers,
Gilou
next prev parent reply other threads:[~2009-09-02 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 1:14 [dm-crypt] cryptsetup solarflow99
2009-09-02 2:42 ` test532
2009-09-02 3:01 ` f-dm-c
2009-09-02 5:13 ` Milan Broz
2009-09-02 10:12 ` Gilles PIETRI [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-20 11:37 omar ahizoun
[not found] <CAAdJYJY6e9XTbZs8VTji9WKSPvEs7w4J8xxXLeo9=htOZS_5Hw@mail.gmail.com>
2017-11-10 17:05 ` [dm-crypt] Cryptsetup Steven Houtchen
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=4A9E451C.5010101@gilouweb.com \
--to=contact+dev@gilouweb.com \
--cc=dm-crypt@saout.de \
/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.