3 Jul 2012 09:52
3 Jul 2012 16:16
Re: ploop and mount options
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@...> 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 :)(Continue reading)
4 Jul 2012 13:35
4 Jul 2012 13:43
Re: find out CT ploop device
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-AMbIAPZXqLPwcm3RLHvk2g@public.gmane.orgg> 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-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
https://openvz.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@... https://openvz.org/mailman/listinfo/users
6 Sep 2012 13:53
Re: ploop and mount options
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@...> 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 > _______________________________________________ > Users mailing list > Users@... > https://openvz.org/mailman/listinfo/users
8 Sep 2012 11:19
Re: ploop and mount options
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@...> > 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 >> _______________________________________________ >> Users mailing list >> Users@... >> https://openvz.org/mailman/listinfo/users > _______________________________________________ > Users mailing list > Users@... > https://openvz.org/mailman/listinfo/users
8 Sep 2012 15:31
Re: ploop and mount options
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.
12 Sep 2012 13:59
Re: ploop and mount options
On 08.09.2012 at 15:31 +0200, Kir Kolyshkin <kir@...> 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
12 Sep 2012 14:21
Re: ploop and mount options
On 09/12/2012 03:59 PM, Corin Langosch wrote: > > On 08.09.2012 at 15:31 +0200, Kir Kolyshkin <kir@...> 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.
12 Sep 2012 20:57
Re: ploop and mount options
On 12.09.2012 at 14:21 +0200, Kir Kolyshkin <kir@...> wrote: > On 09/12/2012 03:59 PM, Corin Langosch wrote: >> >> On 08.09.2012 at 15:31 +0200, Kir Kolyshkin <kir@...> 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
RSS Feed