Home » Mailing lists » Users » disk use/empty files question
| disk use/empty files question [message #46655] |
Thu, 31 May 2012 19:41  |
Keith Keller
Messages: 5
Registered: May 2012
|
Junior Member |
|
|
Hello openvz users,
I am brand new to OpenVZ, evaluating it to see if it will work in my
environment. I have been playing around, and had a question about disk
usage.
I noticed that, when I first started using my new VZ container, that df
always reported 0 blocks in use:
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 693G 0 693G 0% /
none 16G 4.0K 16G 1% /dev
This is even after having copied quite a bit of data into the container.
Recently, the hardware node seems to have had a hard crash (which I'm
still checking out). On restart, a large number of files that I'd
previously added were truncated to be empty, for example:
# ls -l /usr/lib64/libMagickWand.so.2.0.0
-rwxr-xr-x 1 root root 0 May 7 12:07 /usr/lib64/libMagickWand.so.2.0.0
I'm not sure how to interpret these events. Could they possibly be
related? Is there an issue with my configuration that's causing
problems with container storage?
I am using a CentOS 6.2 on the hardware node, and the stock packages
available from the OpenVZ repos. In addition, after the file size issue
occurred I modified the VZ's config to increase the disk space limits
(it was previously 2G:1000G), which I wonder might be the cause.
Some additional info below. If you need any more details please let me
know. Thanks!
# uname -a
Linux dhcp-128-32-252-85.lips.berkeley.edu 2.6.32-042stab055.10 #1 SMP
Thu May 10 15:38:32 MSD 2012 x86_64 x86_64 x86_64 GNU/Linux
# rpm -qa |grep vz
vzctl-3.2.1-1.x86_64
vzkernel-firmware-2.6.32-042stab055.10.noarch
vzctl-lib-3.2.1-1.x86_64
vzquota-3.0.12-1.x86_64
vzkernel-2.6.32-042stab055.10.x86_64
# cat /etc/vz/conf/21.conf
# RAM (this particular server has 128GB of physical memory)
PHYSPAGES="0:32G"
# Swap
SWAPPAGES="0:512M"
# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="1000G:2000G"
DISKINODES="400000:500000"
QUOTATIME="0"
# CPU fair scheduler parameter
CPUUNITS="1000"
VE_ROOT="/vz/root/$VEID"
VE_PRIVATE="/vz/private/$VEID"
OSTEMPLATE="centos-6-x86_64"
ORIGIN_SAMPLE="vswap-256m"
FEATURES=" nfs:on"
--
kkeller@wombat.san-francisco.ca.us
|
|
|
|
| Re: disk use/empty files question [message #46656 is a reply to message #46655] |
Thu, 31 May 2012 20:23  |
massimiliano.sciabica
Messages: 11
Registered: March 2012
|
Junior Member |
|
|
Hi,
I had a similar issue when I first tried to improve performance of VPS
with high number of small files.
When a VPS reports 0% usage it is usually due to a not ext2 family
filesystem. What fs where you using?
On 31/05/2012 21:41, Keith Keller wrote:
> Hello openvz users,
>
> I am brand new to OpenVZ, evaluating it to see if it will work in my
> environment. I have been playing around, and had a question about disk
> usage.
>
> I noticed that, when I first started using my new VZ container, that df
> always reported 0 blocks in use:
>
> # df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/simfs 693G 0 693G 0% /
> none 16G 4.0K 16G 1% /dev
>
> This is even after having copied quite a bit of data into the container.
>
> Recently, the hardware node seems to have had a hard crash (which I'm
> still checking out). On restart, a large number of files that I'd
> previously added were truncated to be empty, for example:
>
> # ls -l /usr/lib64/libMagickWand.so.2.0.0
> -rwxr-xr-x 1 root root 0 May 7 12:07 /usr/lib64/libMagickWand.so.2.0.0
>
> I'm not sure how to interpret these events. Could they possibly be
> related? Is there an issue with my configuration that's causing
> problems with container storage?
>
> I am using a CentOS 6.2 on the hardware node, and the stock packages
> available from the OpenVZ repos. In addition, after the file size issue
> occurred I modified the VZ's config to increase the disk space limits
> (it was previously 2G:1000G), which I wonder might be the cause.
>
> Some additional info below. If you need any more details please let me
> know. Thanks!
>
>
>
> # uname -a
> Linux dhcp-128-32-252-85.lips.berkeley.edu 2.6.32-042stab055.10 #1 SMP
> Thu May 10 15:38:32 MSD 2012 x86_64 x86_64 x86_64 GNU/Linux
>
> # rpm -qa |grep vz
> vzctl-3.2.1-1.x86_64
> vzkernel-firmware-2.6.32-042stab055.10.noarch
> vzctl-lib-3.2.1-1.x86_64
> vzquota-3.0.12-1.x86_64
> vzkernel-2.6.32-042stab055.10.x86_64
>
> # cat /etc/vz/conf/21.conf
>
> # RAM (this particular server has 128GB of physical memory)
> PHYSPAGES="0:32G"
>
> # Swap
> SWAPPAGES="0:512M"
>
> # Disk quota parameters (in form of softlimit:hardlimit)
> DISKSPACE="1000G:2000G"
> DISKINODES="400000:500000"
> QUOTATIME="0"
>
> # CPU fair scheduler parameter
> CPUUNITS="1000"
> VE_ROOT="/vz/root/$VEID"
> VE_PRIVATE="/vz/private/$VEID"
> OSTEMPLATE="centos-6-x86_64"
> ORIGIN_SAMPLE="vswap-256m"
> FEATURES=" nfs:on"
>
>
>
|
|
|
|
| Re: disk use/empty files question [message #46657 is a reply to message #46655] |
Thu, 31 May 2012 20:26 |
Kirill Kolyshkin
Messages: 9
Registered: October 2006
|
Junior Member |
|
|
On 31 May 2012 23:41, Keith Keller <kkeller@wombat.san-francisco.ca.us> wrote:
>
> Hello openvz users,
>
> I am brand new to OpenVZ, evaluating it to see if it will work in my
> environment. I have been playing around, and had a question about disk
> usage.
>
> I noticed that, when I first started using my new VZ container, that df
> always reported 0 blocks in use:
>
> # df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/simfs 693G 0 693G 0% /
> none 16G 4.0K 16G 1% /dev
>
> This is even after having copied quite a bit of data into the container.
Assuming you don't have DISK_QUOTA=no in global config (ie /etc/vz/vz.conf),
the figures shown come from vzquota, and in order for vzquota to work correctly
when you want to copy something to container you have to have it mounted (ie
vzctl status 21 should show the word 'mounted' among others) and copy the
data to VE_ROOT (ie /vz/root/21) but not to VE_PRIVATE (/vz/private/21).
If you have already done it wrong (I assume you did *), you have to recalculate
vzquota, the easiest way is to stop container, do vzquota drop 21 and
start container
again. This should fix your issue.
* what happened I guess is you have copied something big to under /vz/private/21
(bypassing vzquota) and then removed it from either /vz/root/21 or
right from inside the container
(not bypassing the vzquota), leading to disk space being accounted on
removal and the negative
result, which is shown as 0.
A nice alternative is to use ploop (http://wiki.openvz.org/Ploop)
instead of simfs+vzquota.
But I suggest you to fix your problem first.
>
> Recently, the hardware node seems to have had a hard crash (which I'm
> still checking out). On restart, a large number of files that I'd
> previously added were truncated to be empty, for example:
>
> # ls -l /usr/lib64/libMagickWand.so.2.0.0
> -rwxr-xr-x 1 root root 0 May 7 12:07 /usr/lib64/libMagickWand.so.2.0.0
I believe this is because of file system crash and the fsck (or journal replay)
which truncated your files. In other words, this is not directly
related to what you
have described above.
Speaking of kernel crashes, it's nice to have some console logger installed,
such as netconsole so whenever you have an oops you can report the bug.
See http://wiki.openvz.org/Remote_console_setup
>
> I'm not sure how to interpret these events. Could they possibly be
> related? Is there an issue with my configuration that's causing
> problems with container storage?
Configuration below looks fine to me, except...
>
> I am using a CentOS 6.2 on the hardware node, and the stock packages
> available from the OpenVZ repos. In addition, after the file size issue
> occurred I modified the VZ's config to increase the disk space limits
> (it was previously 2G:1000G), which I wonder might be the cause.
>
> Some additional info below. If you need any more details please let me
> know. Thanks!
>
>
>
> # uname -a
> Linux dhcp-128-32-252-85.lips.berkeley.edu 2.6.32-042stab055.10 #1 SMP
> Thu May 10 15:38:32 MSD 2012 x86_64 x86_64 x86_64 GNU/Linux
>
> # rpm -qa |grep vz
> vzctl-3.2.1-1.x86_64
> vzkernel-firmware-2.6.32-042stab055.10.noarch
> vzctl-lib-3.2.1-1.x86_64
> vzquota-3.0.12-1.x86_64
> vzkernel-2.6.32-042stab055.10.x86_64
>
> # cat /etc/vz/conf/21.conf
>
> # RAM (this particular server has 128GB of physical memory)
> PHYSPAGES="0:32G"
>
> # Swap
> SWAPPAGES="0:512M"
>
> # Disk quota parameters (in form of softlimit:hardlimit)
> DISKSPACE="1000G:2000G"
It looks like you have set disk quota values to more than your really
have. Since this doesn't make sense
my question is -- did you meant to disable disk space limit entirely?
If yes, you can just have
DISK_QUOTA=no in this config.
> DISKINODES="400000:500000"
> QUOTATIME="0"
>
> # CPU fair scheduler parameter
> CPUUNITS="1000"
> VE_ROOT="/vz/root/$VEID"
> VE_PRIVATE="/vz/private/$VEID"
> OSTEMPLATE="centos-6-x86_64"
> ORIGIN_SAMPLE="vswap-256m"
> FEATURES=" nfs:on"
>
>
> --
> kkeller@wombat.san-francisco.ca.us
>
>
|
|
|
|
| Re: disk use/empty files question [message #46658 is a reply to message #46657] |
Thu, 31 May 2012 21:41 |
Keith Keller
Messages: 5
Registered: May 2012
|
Junior Member |
|
|
Hello all, thanks for the quick responses!
On 2012-05-31, Kirill Kolyshkin <kolyshkin@gmail.com> wrote:
>
> Assuming you don't have DISK_QUOTA=no in global config (ie /etc/vz/vz.conf),
That's correct.
> the figures shown come from vzquota, and in order for vzquota to work correctly
> when you want to copy something to container you have to have it mounted (ie
> vzctl status 21 should show the word 'mounted' among others) and copy the
> data to VE_ROOT (ie /vz/root/21) but not to VE_PRIVATE (/vz/private/21).
>
> If you have already done it wrong (I assume you did *), you have to recalculate
> vzquota, the easiest way is to stop container, do vzquota drop 21 and
> start container
> again. This should fix your issue.
You are indeed correct that I originally copied data to /vz/private/21.
But when I attempted to drop the quota, it still reports 0 blocks used.
I wonder if Massimiliano's comment is relevant?
On 2012-05-31, Massimiliano
<massimiliano.sciabica@kiiama.com> wrote:
> Hi,
> I had a similar issue when I first tried to improve performance of VPS
> with high number of small files.
> When a VPS reports 0% usage it is usually due to a not ext2 family
> filesystem. What fs where you using?
I am using XFS. The FAQ mentions that disk quotas do not work with XFS,
so perhaps that's why it isn't displaying quite right (see below).
> I believe this is because of file system crash and the fsck (or journal replay)
> which truncated your files. In other words, this is not directly
> related to what you have described above.
Perhaps--on boot, I didn't notice any unusual messages from fsck, though
I admit I wasn't paying an enormous amount of attention, and the logs
don't have anything interesting to report either. Does OpenVZ do a lot
of caching of disk writes from within a container? (It's obviously too
late now to see what xfs_repair thinks of the filesystem, but FWIW it
didn't find anything unusual.)
> Speaking of kernel crashes, it's nice to have some console logger installed,
> such as netconsole so whenever you have an oops you can report the bug.
> See http://wiki.openvz.org/Remote_console_setup
Yes, I just set this up after the first crash--silly oversight not to
have done it right away. :)
>> # Disk quota parameters (in form of softlimit:hardlimit)
>> DISKSPACE="1000G:2000G"
>
> It looks like you have set disk quota values to more than your really
> have. Since this doesn't make sense
> my question is -- did you meant to disable disk space limit entirely?
> If yes, you can just have
> DISK_QUOTA=no in this config.
Well, I am not entirely sure what I want, to be honest. If it's true
that having VE_ROOT and VE_PRIVATE on an XFS filesystem means disk
quotas don't work right, then perhaps I should either use ext3 (or
ext4?) on that filesystem, or disable disk quotas for all containers.
As an experiment on the latter, I set DISK_QUOTA=no in vz.conf, and now
I get:
# vzctl exec 21 df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 1.0T 332G 693G 33% /
none 16G 4.0K 16G 1% /dev
But it would be convenient to have disk quotas. Is there a preference
for ext3 or ext4 for the host filesystem?
--keith
--
kkeller@wombat.san-francisco.ca.us
|
|
|
|
| Re: Re: disk use/empty files question [message #46660 is a reply to message #46658] |
Fri, 01 June 2012 03:24 |
|
|
On 06/01/2012 01:41 AM, Keith Keller wrote:
> Hello all, thanks for the quick responses!
>
> On 2012-05-31, Kirill Kolyshkin<kolyshkin@gmail.com> wrote:
>> Assuming you don't have DISK_QUOTA=no in global config (ie /etc/vz/vz.conf),
> That's correct.
>
>> the figures shown come from vzquota, and in order for vzquota to work correctly
>> when you want to copy something to container you have to have it mounted (ie
>> vzctl status 21 should show the word 'mounted' among others) and copy the
>> data to VE_ROOT (ie /vz/root/21) but not to VE_PRIVATE (/vz/private/21).
>>
>> If you have already done it wrong (I assume you did *), you have to recalculate
>> vzquota, the easiest way is to stop container, do vzquota drop 21 and
>> start container
>> again. This should fix your issue.
> You are indeed correct that I originally copied data to /vz/private/21.
> But when I attempted to drop the quota, it still reports 0 blocks used.
> I wonder if Massimiliano's comment is relevant?
>
> On 2012-05-31, Massimiliano
> <massimiliano.sciabica@kiiama.com> wrote:
>> Hi,
>> I had a similar issue when I first tried to improve performance of VPS
>> with high number of small files.
>> When a VPS reports 0% usage it is usually due to a not ext2 family
>> filesystem. What fs where you using?
> I am using XFS. The FAQ mentions that disk quotas do not work with XFS,
> so perhaps that's why it isn't displaying quite right (see below).
Right. I am not sure why it behaves this way, but yes indeed, vzquota
doesn't work with XFS.
>
>> I believe this is because of file system crash and the fsck (or journal replay)
>> which truncated your files. In other words, this is not directly
>> related to what you have described above.
> Perhaps--on boot, I didn't notice any unusual messages from fsck, though
> I admit I wasn't paying an enormous amount of attention, and the logs
> don't have anything interesting to report either. Does OpenVZ do a lot
> of caching of disk writes from within a container? (It's obviously too
> late now to see what xfs_repair thinks of the filesystem, but FWIW it
> didn't find anything unusual.)
>
>> Speaking of kernel crashes, it's nice to have some console logger installed,
>> such as netconsole so whenever you have an oops you can report the bug.
>> See http://wiki.openvz.org/Remote_console_setup
> Yes, I just set this up after the first crash--silly oversight not to
> have done it right away. :)
>
>>> # Disk quota parameters (in form of softlimit:hardlimit)
>>> DISKSPACE="1000G:2000G"
>> It looks like you have set disk quota values to more than your really
>> have. Since this doesn't make sense
>> my question is -- did you meant to disable disk space limit entirely?
>> If yes, you can just have
>> DISK_QUOTA=no in this config.
> Well, I am not entirely sure what I want, to be honest. If it's true
> that having VE_ROOT and VE_PRIVATE on an XFS filesystem means disk
> quotas don't work right, then perhaps I should either use ext3 (or
> ext4?) on that filesystem, or disable disk quotas for all containers.
>
> As an experiment on the latter, I set DISK_QUOTA=no in vz.conf, and now
> I get:
>
> # vzctl exec 21 df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/simfs 1.0T 332G 693G 33% /
> none 16G 4.0K 16G 1% /dev
>
> But it would be convenient to have disk quotas. Is there a preference
> for ext3 or ext4 for the host filesystem?
Ext4 of course.
And then I recommend to try using ploop layout not simfs one.
http://wiki.openvz.org/Ploop/Getting_started
>
> --keith
>
>
Kir Kolyshkin
|
|
|
|
| Re: Re: disk use/empty files question [message #46661 is a reply to message #46658] |
Fri, 01 June 2012 06:09 |
massimiliano.sciabica
Messages: 11
Registered: March 2012
|
Junior Member |
|
|
Hi Keith,
I'm quite sure XFS is the "problem".
Kirill response is techincally perfect and his knowledge is far ahead of
mine, I would have not even imagined that disk quota might be implied.
But I suggest you to have a try with ext4 or ext3, the both work fine,
even with any tuning option you may need.
On 31/05/2012 23:41, Keith Keller wrote:
> Hello all, thanks for the quick responses!
>
> On 2012-05-31, Kirill Kolyshkin<kolyshkin@gmail.com> wrote:
>
>> Assuming you don't have DISK_QUOTA=no in global config (ie /etc/vz/vz.conf),
>>
> That's correct.
>
>
>> the figures shown come from vzquota, and in order for vzquota to work correctly
>> when you want to copy something to container you have to have it mounted (ie
>> vzctl status 21 should show the word 'mounted' among others) and copy the
>> data to VE_ROOT (ie /vz/root/21) but not to VE_PRIVATE (/vz/private/21).
>>
>> If you have already done it wrong (I assume you did *), you have to recalculate
>> vzquota, the easiest way is to stop container, do vzquota drop 21 and
>> start container
>> again. This should fix your issue.
>>
> You are indeed correct that I originally copied data to /vz/private/21.
> But when I attempted to drop the quota, it still reports 0 blocks used.
> I wonder if Massimiliano's comment is relevant?
>
> On 2012-05-31, Massimiliano
> <massimiliano.sciabica@kiiama.com> wrote:
>
>> Hi,
>> I had a similar issue when I first tried to improve performance of VPS
>> with high number of small files.
>> When a VPS reports 0% usage it is usually due to a not ext2 family
>> filesystem. What fs where you using?
>>
> I am using XFS. The FAQ mentions that disk quotas do not work with XFS,
> so perhaps that's why it isn't displaying quite right (see below).
>
>
>> I believe this is because of file system crash and the fsck (or journal replay)
>> which truncated your files. In other words, this is not directly
>> related to what you have described above.
>>
> Perhaps--on boot, I didn't notice any unusual messages from fsck, though
> I admit I wasn't paying an enormous amount of attention, and the logs
> don't have anything interesting to report either. Does OpenVZ do a lot
> of caching of disk writes from within a container? (It's obviously too
> late now to see what xfs_repair thinks of the filesystem, but FWIW it
> didn't find anything unusual.)
>
>
>> Speaking of kernel crashes, it's nice to have some console logger installed,
>> such as netconsole so whenever you have an oops you can report the bug.
>> See http://wiki.openvz.org/Remote_console_setup
>>
> Yes, I just set this up after the first crash--silly oversight not to
> have done it right away. :)
>
>
>>> # Disk quota parameters (in form of softlimit:hardlimit)
>>> DISKSPACE="1000G:2000G"
>>>
>> It looks like you have set disk quota values to more than your really
>> have. Since this doesn't make sense
>> my question is -- did you meant to disable disk space limit entirely?
>> If yes, you can just have
>> DISK_QUOTA=no in this config.
>>
> Well, I am not entirely sure what I want, to be honest. If it's true
> that having VE_ROOT and VE_PRIVATE on an XFS filesystem means disk
> quotas don't work right, then perhaps I should either use ext3 (or
> ext4?) on that filesystem, or disable disk quotas for all containers.
>
> As an experiment on the latter, I set DISK_QUOTA=no in vz.conf, and now
> I get:
>
> # vzctl exec 21 df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/simfs 1.0T 332G 693G 33% /
> none 16G 4.0K 16G 1% /dev
>
> But it would be convenient to have disk quotas. Is there a preference
> for ext3 or ext4 for the host filesystem?
>
> --keith
>
>
>
|
|
|
|
| Re: Re: disk use/empty files question [message #46662 is a reply to message #46661] |
Fri, 01 June 2012 06:45 |
Kirill Kolyshkin
Messages: 9
Registered: October 2006
|
Junior Member |
|
|
01.06.2012 10:13 пользователь "Massimiliano" <
massimiliano.sciabica@kiiama.com> написал:
>
> Hi Keith,
> I'm quite sure XFS is the "problem".
> Kirill response is techincally perfect and his knowledge is far ahead of
mine, I would have not even imagined that disk quota might be implied. But
I suggest you to have a try with ext4 or ext3, the both work fine, even
with any tuning option you may need.
Ext4 (since you will be able to use ploop)
>
>
> On 31/05/2012 23:41, Keith Keller wrote:
>>
>> Hello all, thanks for the quick responses!
>>
>> On 2012-05-31, Kirill Kolyshkin<kolyshkin@gmail.com> wrote:
>>
>>>
>>> Assuming you don't have DISK_QUOTA=no in global config (ie
/etc/vz/vz.conf),
>>>
>>
>> That's correct.
>>
>>
>>>
>>> the figures shown come from vzquota, and in order for vzquota to work
correctly
>>> when you want to copy something to container you have to have it
mounted (ie
>>> vzctl status 21 should show the word 'mounted' among others) and copy
the
>>> data to VE_ROOT (ie /vz/root/21) but not to VE_PRIVATE (/vz/private/21).
>>>
>>> If you have already done it wrong (I assume you did *), you have to
recalculate
>>> vzquota, the easiest way is to stop container, do vzquota drop 21 and
>>> start container
>>> again. This should fix your issue.
>>>
>>
>> You are indeed correct that I originally copied data to /vz/private/21.
>> But when I attempted to drop the quota, it still reports 0 blocks used.
>> I wonder if Massimiliano's comment is relevant?
>>
>> On 2012-05-31, Massimiliano
>> <massimiliano.sciabica@kiiama.com> wrote:
>>
>>>
>>> Hi,
>>> I had a similar issue when I first tried to improve performance of VPS
>>> with high number of small files.
>>> When a VPS reports 0% usage it is usually due to a not ext2 family
>>> filesystem. What fs where you using?
>>>
>>
>> I am using XFS. The FAQ mentions that disk quotas do not work with XFS,
>> so perhaps that's why it isn't displaying quite right (see below).
>>
>>
>>>
>>> I believe this is because of file system crash and the fsck (or journal
replay)
>>> which truncated your files. In other words, this is not directly
>>> related to what you have described above.
>>>
>>
>> Perhaps--on boot, I didn't notice any unusual messages from fsck, though
>> I admit I wasn't paying an enormous amount of attention, and the logs
>> don't have anything interesting to report either. Does OpenVZ do a lot
>> of caching of disk writes from within a container? (It's obviously too
>> late now to see what xfs_repair thinks of the filesystem, but FWIW it
>> didn't find anything unusual.)
>>
>>
>>>
>>> Speaking of kernel crashes, it's nice to have some console logger
installed,
>>> such as netconsole so whenever you have an oops you can report the bug.
>>> See http://wiki.openvz.org/Remote_console_setup
>>>
>>
>> Yes, I just set this up after the first crash--silly oversight not to
>> have done it right away. :)
>>
>>
>>>>
>>>> # Disk quota parameters (in form of softlimit:hardlimit)
>>>> DISKSPACE="1000G:2000G"
>>>>
>>>
>>> It looks like you have set disk quota values to more than your really
>>> have. Since this doesn't make sense
>>> my question is -- did you meant to disable disk space limit entirely?
>>> If yes, you can just have
>>> DISK_QUOTA=no in this config.
>>>
>>
>> Well, I am not entirely sure what I want, to be honest. If it's true
>> that having VE_ROOT and VE_PRIVATE on an XFS filesystem means disk
>> quotas don't work right, then perhaps I should either use ext3 (or
>> ext4?) on that filesystem, or disable disk quotas for all containers.
>>
>> As an experiment on the latter, I set DISK_QUOTA=no in vz.conf, and now
>> I get:
>>
>> # vzctl exec 21 df -h
>> Filesystem Size Used Avail Use% Mounted on
>> /dev/simfs 1.0T 332G 693G 33% /
>> none 16G 4.0K 16G 1% /dev
>>
>> But it would be convenient to have disk quotas. Is there a preference
>> for ext3 or ext4 for the host filesystem?
>>
>> --keith
>>
>>
>>
>
|
|
|
|
| Re: disk use/empty files question [message #46723 is a reply to message #46660] |
Tue, 05 June 2012 18:31 |
Keith Keller
Messages: 5
Registered: May 2012
|
Junior Member |
|
|
On 2012-06-01, Kir Kolyshkin <kir@openvz.org> wrote:
> Ext4 of course.
Sounds great, I am working with it now.
> And then I recommend to try using ploop layout not simfs one.
> http://wiki.openvz.org/Ploop/Getting_started
So, I found in this article:
http://wiki.openvz.org/Ploop
that ploop is still new. Is that still true? I'm already new to
OpenVZ, and am not quite ready to also take on a new feature that's
still somewhat experimental. (Perhaps on a different server that I'll
be staging soon, which will not be as much of a production machine.)
It looks like the "empty files" issue may not be an OpenVZ issue, as I
found empty files after a crash in which I was not running any
containers (though it was still the OpenVZ kernel). But right now I'm
guessing hardware, so will pursue that first.
--keith
--
kkeller@wombat.san-francisco.ca.us
|
|
|
|
Goto Forum:
Current Time: Tue May 14 06:37:16 GMT 2024
Total time taken to generate the page: 0.01370 seconds
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
