| mount ext3 file system inside VE [message #8697] |
Sun, 03 December 2006 01:55  |
hiro
Messages: 5
Registered: February 2006
|
Junior Member |
|
|
Hello list
I am trying to mount an additional disk which is ext3 file system
inside VE.
kernel version 2.6.9-023stab032.1
vzctl version 3.0.13
Hard ware node OS Centos4.3
but, I ve' got an error message like
develop(VE):/dev/vdisk # mkfs -j /dev/vdisk/disk1
develop(VE):/dev/vdisk # mount -t ext3 /dev/vdisk/disk1 /mnt/disk1
mount: wrong fs type, bad option, bad superblock on /dev/vdisk/disk1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
then ended up using -t ext2 option instead of ext3.
develop:/ # mount -t ext2 /dev/vdisk/disk1 /mnt/disk1
develop(VE):/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/simfs 874428 333940 335260 50% /
tmpfs 158732 0 158732 0% /dev/shm
/dev/vdisk/disk1 1007896 17672 939024 2% /mnt/disk1
this is kind of werard....
Are there any work around for this ?
Hiro
|
|
|
|
|
|
| Re: mount ext3 file system inside VE [message #8709 is a reply to message #8706] |
Mon, 04 December 2006 10:51  |
|
|
Well I would add that you can also bind mount anything to a VE from the
host system.
See OpenVZ User's Guide, around page 90.
Vasily Tarasov wrote:
> ext3 file system starts kernel thread for journal support.
> Starting kernel thread in VE is prohibited for security reasons.
> Consequently you have the problem.
> The only workaround is to mount disk using ext2.
>
> HTH,
> Vasily.
>
> Yukihiro Nomura wrote:
>
>> Hello list
>>
>> I am trying to mount an additional disk which is ext3 file system
>> inside VE.
>>
>> kernel version 2.6.9-023stab032.1
>> vzctl version 3.0.13
>> Hard ware node OS Centos4.3
>>
>> but, I ve' got an error message like
>>
>> develop(VE):/dev/vdisk # mkfs -j /dev/vdisk/disk1
>> develop(VE):/dev/vdisk # mount -t ext3 /dev/vdisk/disk1 /mnt/disk1
>> mount: wrong fs type, bad option, bad superblock on /dev/vdisk/disk1,
>> missing codepage or other error
>> In some cases useful info is found in syslog - try
>> dmesg | tail or so
>>
>> then ended up using -t ext2 option instead of ext3.
>>
>> develop:/ # mount -t ext2 /dev/vdisk/disk1 /mnt/disk1
>> develop(VE):/ # df
>> Filesystem 1K-blocks Used Available Use% Mounted on
>> /dev/simfs 874428 333940 335260 50% /
>> tmpfs 158732 0 158732 0% /dev/shm
>> /dev/vdisk/disk1 1007896 17672 939024 2% /mnt/disk1
>>
>> this is kind of werard....
>>
>> Are there any work around for this ?
>>
>> Hiro
>>
>>
>>
>>
>>
>>
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
