On 03/17/2015 11:52 AM, Kir Kolyshkin wrote:
On 03/17/2015 05:57 AM, linuxthefish wrote:
Hello,
Please set OpenVZ to use simfs not buggy ploop, there are no end of
issues with ploop...
Hello Edmund,
I am very sorry to hear you have issues with OpenVZ. I hope you will
find the following
information helpful.
1. There are two ways to "set OpenVZ to use simfs".
1.1 Default layout (simfs or ploop) for future CTs is set by VE_LAYOUT
variable in /etc/vz/vz.conf.
1.2 For vzctl create, you can specify --layout option.
For more info on this, please see vzctl(8) and vz.conf(5) man pages.
2. The error you see is not related to ploop in any way, it's pretty
clear.
It could be something wrong with either files in container (like init
can't find
configuration and dies) or with CT config (say, resource limits are
way too tight).
You can try using vzctl console to see the boot process, and check the
in-CT files
for obvious problems (I'd run rpm -Va in a chroot, for example).
3. Let me assure you that ploop is pretty stable and is used by lots
of users
on many installations big and small without any major problems. It was
not set
as a default until proven stable. As you reported you are having no
end of issues
with ploop, let me suggest you to use https://bugzilla.openvz.org/ to
report those
(or, if you did, please kindly let me know IDs of bugs you filed).
4. The obvious mistake is you run fsck on the whole device rather than
a partition,
this is why it can't find the superblock. Also, fsck is run during
mount so it would
tell you if something is wrong.
5. Please don't use any personal emails for it, it's a bad practice, as
5.1. developers to users ratio is very far from being 1:1 -- it's not
scalable
5.2. Other users might know answers to your question, help with your
problem
5.3. Other users might benefit from the discussion now or in the future
6. If you need help, possible options are listed at
http://openvz.org/Support.
I would start with users@ mailing list (which I Cc this reply to).
One more thing I forgot to add -- replying to an irrelevant email is not a
good email practice. It's even worse if you don't change the email subject
(I have to admit I fell for the last one, too -- fixing it now).
Kir.
Finally, thank you for using OpenVZ!
Regards,
Kir.
[root@tx1v2 ~]# vzctl start 14082
Starting container...
Unmounting file system at /vz/root/14082
Unmounting device /dev/ploop39756
Container is unmounted
Opening delta /vz/private/14082/root.hdd/root.hdd
Adding delta dev=/dev/ploop39756
img=/vz/private/14082/root.hdd/root.hdd (rw)
Mounting /dev/ploop39756p1 at /vz/root/14082 fstype=ext4
data='balloon_ino=12,'
Container is mounted
Adding IP address(es): 23.95.108.76 23.95.108.77 23.95.108.80
23.95.108.81
Setting CPU limit: 400
Setting CPU units: 1000
Setting CPUs: 4
Container start failed (try to check kernel messages, e.g. "dmesg |
tail")
Killing container ...
Container was stopped
Unmounting file system at /vz/root/14082
Unmounting device /dev/ploop39756
Container is unmounted
[root@tx1v2 ~]# dmesg | tail
[5939781.955260] CT: 14082: started
[5939782.521456] CT: 14082: stopped
[5939925.659518] CT: 14082: started
[5939930.024759] CT: 14082: stopped
[5939972.917881] ploop39756: p1
[5939973.128541] ploop39756: p1
[5939973.557214] EXT4-fs (ploop39756p1): mounted filesystem with
ordered data mode. Opts:
[5939973.574258] EXT4-fs (ploop39756p1): loaded balloon from 12 (0
blocks)
[5939973.581336] CT: 14082: started
[5939978.004668] CT: 14082: stopped
[root@tx1v2 ~]# ploop mount
/vz/private/14082/root.hdd/DiskDescriptor.xml
Opening delta /vz/private/14082/root.hdd/root.hdd
Adding delta dev=/dev/ploop39756
img=/vz/private/14082/root.hdd/root.hdd (rw)
[root@tx1v2 ~]# fdisk -l /dev/ploop39756
WARNING: GPT (GUID Partition Table) detected on '/dev/ploop39756'! The
util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/ploop39756: 161.1 GB, 161061273600 bytes
255 heads, 63 sectors/track, 19581 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/ploop39756p1 1 19582 157286399+ ee GPT
Partition 1 does not start on physical sector boundary.
[root@tx1v2 ~]# e2fsck /dev/ploop39756
e2fsck 1.41.12 (17-May-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open
/dev/ploop39756
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate
superblock:
e2fsck -b 8193 <device>
[root@tx1v2 ~]#
[root@tx1v2 ~]# e2fsck /dev/ploop39756
e2fsck 1.41.12 (17-May-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open
/dev/ploop39756
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate
superblock:
e2fsck -b 8193 <device>
Thanks,
Edmund
On 11 March 2015 at 22:08, Kir Kolyshkin <k...@openvz.org> wrote:
OpenVZ project released an updated RHEL6 based testing kernel.
Read below for more information.
NOTE: it is recommended to test this kernel on some of your servers
as it (or its successor) will appear in rhel6 (stable) branch
some time later.
Changes and Download
====================
* Stability and Docker related fixes
For detailed changelog and downloads, see:
https://openvz.org/Download/kernel/rhel6-testing/042stab105.13
Bug reporting
=============
Use http://bugzilla.openvz.org/ to report any bugs found.
Other sources of info on updates
================================
See http://wiki.openvz.org/News to view all the news (including
updates)
online. There you can also find RSS/Atom feed links.
Regards,
OpenVZ team
_______________________________________________
Announce mailing list
annou...@openvz.org
https://lists.openvz.org/mailman/listinfo/announce
_______________________________________________
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users
