OpenVZ Forum


Home » General » Support » Mounts--bind, issue or limitation?
Re: Mounts--bind, issue or limitation? [message #12671 is a reply to message #12665] Mon, 07 May 2007 07:07 Go to previous messageGo to previous message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Hello,

I want to clear up some ambiguities:

1. You wrote, that you had two 500GB disk drives, but df on HN outputs:
hardwarenode:~# df -h
/dev/mapper/dataone 250M 97M 140M 41% /data1
/dev/mapper/datatwo 250M 97M 140M 41% /data2
So, what are dataone and datatwo? Partions of the same drive or different drives? Or do I miss something? Wink

2. Why in VE df outputs other size (other then 250M) of filesystems on /dataone /datatwo partions:
somevps:/# df -h
...
ext3 459G 29G 407G 7% /site/dataone
ext3 459G 8.2G 428G 2% /site/datatwo
...

3. In VE mount command outputs:
....
ext3 on /site/dataone type ext3 (rw,data=ordered)
ext3 on /site/datatwo type ext3 (rw,data=ordered)
ext3 on /site/dataone/ftpd/ftp/site/1 type ext3 (rw,data=ordered)
ext3 on /site/dataone/ftpd/ftp/site/2 type ext3 (rw,data=ordered)
ext3 on /site/dataone/ftpd/ftp/site/3 type ext3 (rw,data=ordered)
ext3 on /site/dataone/ftpd/ftp/site/4 type ext3 (rw,data=ordered)
ext3 on /site/dataone/ftpd/ftp/site/5 type ext3 (rw,data=ordered)
ext3 on /site/dataone/ftpd/ftp/site/6 type ext3 (rw,data=ordered)
Bind mount points /site/dataone/ftpd/ftp/site/1, /site/dataone/ftpd/ftp/site/2, ... are mount points from what locations? I want to know that in order to probably reproduce the situation here on our local node.

4. The last but probably the most important. Wink You wrote, that "This resulted in me not being able to use the disks at all on the hardware node". What does that mean? How exactly you can't use your drives? Can you post here exact commands that fail to work?

Thank you,
Vasily
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Failed to suspend VE
Next Topic: *SOLVED* Warning: meminfo feature is not supported by kernel. skipped meminfo configure
Goto Forum:
  


Current Time: Mon Sep 09 07:17:57 GMT 2024

Total time taken to generate the page: 0.05067 seconds