OpenVZ Forum


Home » Mailing lists » Users » ploop and mount options
ploop and mount options [message #47056] Tue, 03 July 2012 07:52 Go to next message
Corin Langosch is currently offline  Corin Langosch
Messages: 18
Registered: March 2012
Junior Member
From: *parallels.com
Hi there,

Is there any way to specify mount options for the container's root
filesystem in the container's config when using ploop?

So a normal options string like
" noatime,data=writeback,journal_async_commit,barrier=0,errors =remount-ro ".

Thanks for any hints :)

Corin
Re: ploop and mount options [message #47065 is a reply to message #47056] Tue, 03 July 2012 14:16 Go to previous messageGo to next message
Corin Langosch is currently offline  Corin Langosch
Messages: 18
Registered: March 2012
Junior Member
From: *parallels.com
Hi again,

just a small follow up on this:

Inside the the container I'm able to change the barrier mount option with:

"mount -o remount,barrier=0 /" or "mount -o remount,barrier=1 /"

But changing other options like "noatime" (mount -o remount,noatime /)
fails with "mount: permission denied".

Now I wonder if this is intended or a bug? Why allow changing barrier
and deny noatime option?

BTW: I still haven't found a way to specify mount options in the
container's config :(

Corin

On 03.07.2012 at 09:52 +0200, Corin Langosch <info@corinlangosch.com> wrote:
> Hi there,
>
> Is there any way to specify mount options for the container's root
> filesystem in the container's config when using ploop?
>
> So a normal options string like
> " noatime,data=writeback,journal_async_commit,barrier=0,errors =remount-ro ".
>
> Thanks for any hints :)
>
> Corin
Re: find out CT ploop device [message #47081 is a reply to message #47056] Wed, 04 July 2012 11:35 Go to previous messageGo to next message
stealth is currently offline  stealth
Messages: 17
Registered: June 2010
Junior Member
From: *parallels.com
Hi there,


What is the right way to find out ploop device used for CT and where
it's image file located?
Re: find out CT ploop device [message #47082 is a reply to message #47081] Wed, 04 July 2012 11:43 Go to previous messageGo to next message
Antanas is currently offline  Antanas
Messages: 2
Registered: July 2012
Junior Member
From: *mikrovisata.net
Hello,
maybe this way: ls -al /dev/ploop/*101* ?
where is 101 is veid.

-Antanas

On Wed, Jul 4, 2012 at 2:35 PM, Stealth <st@overlogic.org> wrote:

> Hi there,
>
>
> What is the right way to find out ploop device used for CT and where it's
> image file located?
> ______________________________**_________________
> Users mailing list
> Users@openvz.org
> https://openvz.org/mailman/**listinfo/users<https://openvz.org/mailman/listinfo/users>
>
Re: ploop and mount options [message #47748 is a reply to message #47056] Thu, 06 September 2012 11:53 Go to previous messageGo to next message
Corin Langosch is currently offline  Corin Langosch
Messages: 18
Registered: March 2012
Junior Member
From: *parallels.com
Hi again,

just a small follow up on this:

Inside the the container I'm able to change the barrier mount option with:

"mount -o remount,barrier=0 /" or "mount -o remount,barrier=1 /"

But changing other options like "noatime" (mount -o remount,noatime /)
fails with "mount: permission denied".

Now I wonder if this is intended or a bug? Why allow changing barrier
and deny noatime option?

BTW: I still haven't found a way to specify mount options in the
container's config :(

Corin

On 03.07.2012 at 09:52 +0200, Corin Langosch <info@corinlangosch.com> wrote:
> Hi there,
>
> Is there any way to specify mount options for the container's root
> filesystem in the container's config when using ploop?
>
> So a normal options string like
> " noatime,data=writeback,journal_async_commit,barrier=0,errors =remount-ro ".
>
> Thanks for any hints :)
>
> Corin
Re: ploop and mount options [message #47773 is a reply to message #47748] Sat, 08 September 2012 09:19 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

From: *parallels.com
On 09/06/2012 03:53 PM, Corin Langosch wrote:
> Hi again,
>
> just a small follow up on this:
>
> Inside the the container I'm able to change the barrier mount option
> with:
>
> "mount -o remount,barrier=0 /" or "mount -o remount,barrier=1 /"
>
> But changing other options like "noatime" (mount -o remount,noatime /)
> fails with "mount: permission denied".
>
> Now I wonder if this is intended or a bug? Why allow changing barrier
> and deny noatime option?

Well, I can't tell why it lets you remount with barrier but does not let
you remount with noatime.
But I can tell noatime is not needed nowdays, since relatime is used by
default and makes much more sense.

You can file a bug to bugzilla.openvz.org, component ploop

>
> BTW: I still haven't found a way to specify mount options in the
> container's config :(

Again, file a bug (enhancement) to bugzilla.openvz.org, component vzctl.


>
> Corin
>
> On 03.07.2012 at 09:52 +0200, Corin Langosch <info@corinlangosch.com>
> wrote:
>> Hi there,
>>
>> Is there any way to specify mount options for the container's root
>> filesystem in the container's config when using ploop?
>>
>> So a normal options string like
>> " noatime,data=writeback,journal_async_commit,barrier=0,errors =remount-ro ".
>>
>>
>> Thanks for any hints :)
>>
>> Corin


Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Re: ploop and mount options [message #47774 is a reply to message #47773] Sat, 08 September 2012 13:31 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

From: *parallels.com
On 09/08/2012 01:19 PM, Kir Kolyshkin wrote:
> On 09/06/2012 03:53 PM, Corin Langosch wrote:
>> Hi again,
>>
>> just a small follow up on this:
>>
>> Inside the the container I'm able to change the barrier mount option
>> with:
>>
>> "mount -o remount,barrier=0 /" or "mount -o remount,barrier=1 /"
>>
>> But changing other options like "noatime" (mount -o remount,noatime
>> /) fails with "mount: permission denied".
>>
>> Now I wonder if this is intended or a bug? Why allow changing barrier
>> and deny noatime option?
>
> Well, I can't tell why it lets you remount with barrier but does not
> let you remount with noatime.
> But I can tell noatime is not needed nowdays, since relatime is used
> by default and makes much more sense.
>
> You can file a bug to bugzilla.openvz.org, component ploop
>
>>
>> BTW: I still haven't found a way to specify mount options in the
>> container's config :(
>
> Again, file a bug (enhancement) to bugzilla.openvz.org, component vzctl.

In fact I just implemented that as a --mount_opts option to vzctl set.
See these git commits:
http://git.openvz.org/?p=vzctl;a=commit;h=af95fbdf
http://git.openvz.org/?p=vzctl;a=commit;h=287d0d
http://git.openvz.org/?p=vzctl;a=commit;h=7eb61c

Feel free to test and report your results.


Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Re: ploop and mount options [message #47807 is a reply to message #47774] Wed, 12 September 2012 11:59 Go to previous messageGo to next message
Corin Langosch is currently offline  Corin Langosch
Messages: 18
Registered: March 2012
Junior Member
From: *parallels.com
On 08.09.2012 at 15:31 +0200, Kir Kolyshkin <kir@openvz.org> wrote:
>
> In fact I just implemented that as a --mount_opts option to vzctl set.
> See these git commits:
> http://git.openvz.org/?p=vzctl;a=commit;h=af95fbdf
> http://git.openvz.org/?p=vzctl;a=commit;h=287d0d
> http://git.openvz.org/?p=vzctl;a=commit;h=7eb61c
>
> Feel free to test and report your results.

That's really great news. :)

I just checked out the repo and tried to compile with:

./autogen.sh
./configure --prefix=/usr

Now configure complains:

checking ploop/dynload.h usability... no
checking ploop/dynload.h presence... no
checking for ploop/dynload.h... no
configure: error:
The ploop library headers not found or way too old. You need to either
install recent ploop library headers (most probably ploop-devel package),
or use ./configure --without-ploop

Now I also checked out the repo "ploop", but is doesn't contain the
missing file "dynload.h". Where can I get it?

I also wonder how to build the nice tar.gz archives which can be found
on the website. Is there some script to build them once compilation
succeeds?

Corin
Re: ploop and mount options [message #47808 is a reply to message #47807] Wed, 12 September 2012 12:21 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

From: *parallels.com
On 09/12/2012 03:59 PM, Corin Langosch wrote:
>
> On 08.09.2012 at 15:31 +0200, Kir Kolyshkin <kir@openvz.org> wrote:
>>
>> In fact I just implemented that as a --mount_opts option to vzctl
>> set. See these git commits:
>> http://git.openvz.org/?p=vzctl;a=commit;h=af95fbdf
>> http://git.openvz.org/?p=vzctl;a=commit;h=287d0d
>> http://git.openvz.org/?p=vzctl;a=commit;h=7eb61c
>>
>> Feel free to test and report your results.
>
> That's really great news. :)
>
> I just checked out the repo and tried to compile with:
>
> ./autogen.sh
> ./configure --prefix=/usr
>
> Now configure complains:
>
> checking ploop/dynload.h usability... no
> checking ploop/dynload.h presence... no
> checking for ploop/dynload.h... no
> configure: error:
> The ploop library headers not found or way too old. You need to either
> install recent ploop library headers (most probably ploop-devel package),
> or use ./configure --without-ploop
>
> Now I also checked out the repo "ploop", but is doesn't contain the
> missing file "dynload.h". Where can I get it?

The file is auto-generated. The best way to proceed is compile and
install ploop package first.

cd ploop
./setver.sh -i

Will build and install ploop rpms for you (and you can use same for vzctl).

>
> I also wonder how to build the nice tar.gz archives which can be found
> on the website. Is there some script to build them once compilation
> succeeds?

Those are produced from rpms using rpm2cpio.


Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Re: ploop and mount options [message #47817 is a reply to message #47808] Wed, 12 September 2012 18:57 Go to previous message
Corin Langosch is currently offline  Corin Langosch
Messages: 18
Registered: March 2012
Junior Member
From: *parallels.com
On 12.09.2012 at 14:21 +0200, Kir Kolyshkin <kir@openvz.org> wrote:
> On 09/12/2012 03:59 PM, Corin Langosch wrote:
>>
>> On 08.09.2012 at 15:31 +0200, Kir Kolyshkin <kir@openvz.org> wrote:
>>>
>>> In fact I just implemented that as a --mount_opts option to vzctl
>>> set. See these git commits:
>>> http://git.openvz.org/?p=vzctl;a=commit;h=af95fbdf
>>> http://git.openvz.org/?p=vzctl;a=commit;h=287d0d
>>> http://git.openvz.org/?p=vzctl;a=commit;h=7eb61c
>>>
>>> Feel free to test and report your results.
>>
>> That's really great news. :)
>>
>> I just checked out the repo and tried to compile with:
>>
>> ./autogen.sh
>> ./configure --prefix=/usr
>>
>> Now configure complains:
>>
>> checking ploop/dynload.h usability... no
>> checking ploop/dynload.h presence... no
>> checking for ploop/dynload.h... no
>> configure: error:
>> The ploop library headers not found or way too old. You need to either
>> install recent ploop library headers (most probably ploop-devel
>> package),
>> or use ./configure --without-ploop
>>
>> Now I also checked out the repo "ploop", but is doesn't contain the
>> missing file "dynload.h". Where can I get it?
>
> The file is auto-generated. The best way to proceed is compile and
> install ploop package first.
>
> cd ploop
> ./setver.sh -i
>
> Will build and install ploop rpms for you (and you can use same for
> vzctl).

Wow, I finally managed to compile and install everything. It wasn't that
easy because I needed to setup a centos6 vm first as I didn't get the
stuff compiled using debian squeeze. But now it works great without any
problems!

Corin
Previous Topic: linux-openvz-2.6.32.59.7-gcc46.patch useful for bug id=2012?
Next Topic: ploop and trim/ discard support
Goto Forum:
  


Current Time: Fri Nov 24 05:23:57 GMT 2017