Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I can remember creating this file but it disapeard. But not completely:

root@XXX:/etc/vz/conf# ls -al
total 0
drwxr-x--- 2 root www-data 0 Okt  1 16:04 .
drwxr-x--- 2 root www-data 0 Okt  1 16:04 ..

root@XXX:/etc/vz/conf# touch 1030.conf
touch: cannot touch `1030.conf': File exists

root@warp1:/etc/vz/conf# echo blah > 1030.conf
-bash: 1030.conf: File exists

root@warp1:/etc/vz/conf# rm 1030.conf
rm: cannot remove `1030.conf': No such file or directory

System is Debian7 / Proxmox:

Linux warp1 2.6.32-24-pve #1 SMP Fri Sep 13 07:29:30 CEST 2013 x86_64 GNU/Linux

What is causing this and how can I get my file back / get rid of it and how do I debug sth. like this? Thanks!

share|improve this question
    
Try a quick fsck to have it cleared up. –  Nathan C Oct 1 '13 at 14:52
    
Does lsattr -d . output anything else than - before the .? –  ott-- Oct 1 '13 at 14:59
    
root@warp1:/etc/vz/conf# lsattr -d . lsattr: Inappropriate ioctl for device While reading flags on . –  Scheintod Oct 1 '13 at 15:33
    
root@warp1:/etc/vz/conf# fsck.ext4 -n /dev/sdb2 e2fsck 1.42.5 (29-Jul-2012) Warning! /dev/sdb2 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. /dev/sdb2: clean, 62405/34643968 files, 2990165/138561792 blocks –  Scheintod Oct 1 '13 at 15:37
    
it may be opened by another program, try searching with lsof | grep 1030.conf –  Andrei Mikhaltsov Oct 1 '13 at 15:44

1 Answer 1

up vote 2 down vote accepted

The file exists on another node in your cluster and Proxmox checks for that. You need to do something like:

mv /etc/pve/nodes/[node1]/openvz/whatever.conf /etc/pve/nodes/[node2]/openvz 

to move the config to a different node.

share|improve this answer
    
Brilliant. I wasn't event aware that I'm running a cluster. Just wantet to use the proxmox kernel because debian 7 doesn't include openvz kernels anymore. –  Scheintod Oct 1 '13 at 16:27
    
Looking at the directory you mentioned I see that the root of the problem seems to be that I've renamed my host and this was recognised as new node. –  Scheintod Oct 1 '13 at 16:28
    
Do you know what to do if I don't want this feature or what exactly is doing this? –  Scheintod Oct 1 '13 at 16:30
    
I'm not sure there's anything you can do to make it more like a single machine. But perhaps it's worthy of a separate question; I'm not really a proxmox expert! –  seumasmac Oct 1 '13 at 16:34

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.