How to use lvm directly on tmpfs?
Clash Royale CLAN TAG#URR8PPP
LVM can use devices as backing store for physical volumes
but not directories.
tmpfs can be mounted at any mountpoint but mountpoints are always
directories.
How can the two be reconciled?
I’m aware of the roundabout solution of creating a file on the tmpfs
first, binding it to a loop device, and then using that as the
store. However that implies using a resource (loop devs) that is not
namespaced and thus shared across containers. When isolation is a
concern, this approach is not an option.
What other options are there on a sufficiently recent Linux system?
linux lvm tmpfs
asked Feb 27 at 22:23
Philipp GesangPhilipp Gesang
12714
add a comment |
LVM can use devices as backing store for physical volumes
but not directories.
tmpfs can be mounted at any mountpoint but mountpoints are always
directories.
How can the two be reconciled?
I’m aware of the roundabout solution of creating a file on the tmpfs
first, binding it to a loop device, and then using that as the
store. However that implies using a resource (loop devs) that is not
namespaced and thus shared across containers. When isolation is a
concern, this approach is not an option.
What other options are there on a sufficiently recent Linux system?
linux lvm tmpfs
asked Feb 27 at 22:23
Philipp GesangPhilipp Gesang
12714
Have you considered using a ramdisk? Also, isn't it possible to choose which devices are available in a container? That would make it possible to exclude the loop devices. suse.com/support/kb/doc/?id=7012396
– Emmanuel Rosa
Feb 27 at 22:54
As for ramdisks,CONFIG_BLK_DEV_RAM=y(though that could be worked around). Regarding loop devices, they seem to leak out of the container onto the host. Not immediately but after a while.
– Philipp Gesang
Feb 27 at 23:05
add a comment |
LVM can use devices as backing store for physical volumes
but not directories.
tmpfs can be mounted at any mountpoint but mountpoints are always
directories.
How can the two be reconciled?
I’m aware of the roundabout solution of creating a file on the tmpfs
first, binding it to a loop device, and then using that as the
store. However that implies using a resource (loop devs) that is not
namespaced and thus shared across containers. When isolation is a
concern, this approach is not an option.
What other options are there on a sufficiently recent Linux system?
linux lvm tmpfs
asked Feb 27 at 22:23
Philipp GesangPhilipp Gesang
12714
LVM can use devices as backing store for physical volumes
but not directories.
tmpfs can be mounted at any mountpoint but mountpoints are always
directories.
How can the two be reconciled?
I’m aware of the roundabout solution of creating a file on the tmpfs
first, binding it to a loop device, and then using that as the
store. However that implies using a resource (loop devs) that is not
namespaced and thus shared across containers. When isolation is a
concern, this approach is not an option.
What other options are there on a sufficiently recent Linux system?
linux lvm tmpfs
linux lvm tmpfs
asked Feb 27 at 22:23
Philipp GesangPhilipp Gesang
12714
asked Feb 27 at 22:23
Philipp GesangPhilipp Gesang
12714
asked Feb 27 at 22:23
Philipp GesangPhilipp Gesang
12714
asked Feb 27 at 22:23
Philipp GesangPhilipp Gesang
12714
asked Feb 27 at 22:23
Philipp GesangPhilipp Gesang
12714
12714
Have you considered using a ramdisk? Also, isn't it possible to choose which devices are available in a container? That would make it possible to exclude the loop devices. suse.com/support/kb/doc/?id=7012396
– Emmanuel Rosa
Feb 27 at 22:54
As for ramdisks,CONFIG_BLK_DEV_RAM=y(though that could be worked around). Regarding loop devices, they seem to leak out of the container onto the host. Not immediately but after a while.
– Philipp Gesang
Feb 27 at 23:05
add a comment |
Have you considered using a ramdisk? Also, isn't it possible to choose which devices are available in a container? That would make it possible to exclude the loop devices. suse.com/support/kb/doc/?id=7012396
– Emmanuel Rosa
Feb 27 at 22:54
As for ramdisks,CONFIG_BLK_DEV_RAM=y(though that could be worked around). Regarding loop devices, they seem to leak out of the container onto the host. Not immediately but after a while.
– Philipp Gesang
Feb 27 at 23:05
Have you considered using a ramdisk? Also, isn't it possible to choose which devices are available in a container? That would make it possible to exclude the loop devices. suse.com/support/kb/doc/?id=7012396
– Emmanuel Rosa
Feb 27 at 22:54
Have you considered using a ramdisk? Also, isn't it possible to choose which devices are available in a container? That would make it possible to exclude the loop devices. suse.com/support/kb/doc/?id=7012396
– Emmanuel Rosa
Feb 27 at 22:54
As for ramdisks,
CONFIG_BLK_DEV_RAM=y (though that could be worked around). Regarding loop devices, they seem to leak out of the container onto the host. Not immediately but after a while.– Philipp Gesang
Feb 27 at 23:05
As for ramdisks,
CONFIG_BLK_DEV_RAM=y (though that could be worked around). Regarding loop devices, they seem to leak out of the container onto the host. Not immediately but after a while.– Philipp Gesang
Feb 27 at 23:05
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503433%2fhow-to-use-lvm-directly-on-tmpfs%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503433%2fhow-to-use-lvm-directly-on-tmpfs%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you considered using a ramdisk? Also, isn't it possible to choose which devices are available in a container? That would make it possible to exclude the loop devices. suse.com/support/kb/doc/?id=7012396
– Emmanuel Rosa
Feb 27 at 22:54
As for ramdisks,
CONFIG_BLK_DEV_RAM=y(though that could be worked around). Regarding loop devices, they seem to leak out of the container onto the host. Not immediately but after a while.– Philipp Gesang
Feb 27 at 23:05