From: Chris Hofstaedtler | Deduktiva <chris.hofstaedtler@deduktiva.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] FC-Luns only local devices?
Date: Sun, 26 Jul 2020 23:55:42 +0200 [thread overview]
Message-ID: <20200726215542.4pg3j4zujbabcevo@percival.namespace.at> (raw)
In-Reply-To: <e75109af-629c-3a00-263e-9be6f1709b2f@hw.wewi.de>
Hi,
* Hermann <pve@hw.wewi.de> [200725 18:05]:
> Could you explain in a short sentence, why you avoid partitioning? I
> remember running into difficulties with an image I had created this way
> in another setup. I could not change the size when it was necessary an
> had to delete and recreate everything, which was quite painful, because
> I had to move around a TB of Files.
I don't know about images, but we were talking about LVM PVs on top
of LUNs (SCSI disks from a Linux point of view).
Now, if the only thing that goes on the LUN is an LVM PV, why add an
extra layer, an MBR or GPT partitioning layer?
From my experience this adds two things:
1) another size definition, which you have to edit when resizing the LUN
2) another size definition, which is also read and cached by the
Linux kernel, and - at least in the past - was often impossible to
get updated without closing all open handles to the block device.
Effectively, this meant rebooting.
Also, local staff isn't too happy to fiddle with fdisk: delete and
recreate a partition to resize it. Or use parted and find the magic
flags so it doesn't actually do something unexpected.
Chris
--
Chris Hofstaedtler / Deduktiva GmbH (FN 418592 b, HG Wien)
www.deduktiva.com / +43 1 353 1707
prev parent reply other threads:[~2020-07-26 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8e7395ee-c3ab-03fc-aa2d-9bf2e0781375@hw.wewi.de>
[not found] ` <20200630102125.nnrf3okkiwtdmojw@zeha.at>
2020-07-25 16:04 ` Hermann
2020-07-26 21:55 ` Chris Hofstaedtler | Deduktiva [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=20200726215542.4pg3j4zujbabcevo@percival.namespace.at \
--to=chris.hofstaedtler@deduktiva.com \
--cc=pve-user@lists.proxmox.com \
/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