Search results

@sumsum - Thanks for the information, however when I try to do the above, I get: update-initramfs: /boot/initrd.img-2.6.18-2-pve has been altered. update-initramfs: Cannot update. Override with -t option. I am not sure if I should force the update, or if there is some specific reason my...

Has this specific problem been addressed in those kernels? I can't afford to try it on a whim, these are production servers with a lot of traffic... I'm running a mix of OpenVZ & KVM machines (90% / 10%) and using snapshot backups if that matters. What is the recommended way of trying...

server01:~# pveversion -v pve-manager: 1.6-2 (pve-manager/1.6/5087) running kernel: 2.6.18-2-pve proxmox-ve-2.6.18: 1.5-5 pve-kernel-2.6.18-2-pve: 2.6.18-5 qemu-server: 1.1-18 pve-firmware: 1.0-8 libpve-storage-perl: 1.0-14 vncterm: 0.9-2 vzctl: 3.0.24-1pve4 vzdump: 1.2-7 vzprocps...

See this post for usage details Motherboard is a Gigabyte MA78GM-S2HP which claims to have an RTL8111C On-Board Gigabit Ethernet. We are running 50 MiB to 100 MiB/sec on average over this interface and we are constantly getting kernel panics. I don't know the exact message because it...

Here is the hardware I'm reviewing: Server 1 & 2: ============= AMD Phenom 9850 Quad Core CPU Gigabyte Motherboard w/8GB RAM Highpoint 2640x4 RAID Controller Card 1 x Seagate 7,200 SATA 2 Boot Drive (500GB) 1 x Western Digital Black 7,200 SATA 2 Backup Drive (2TB)...

As I stated above... So... Any ideas?

I've noticed that the format for the backup filenames has changed in order to allow you to have multiple backups, however by default the system appears to only keep the most recent. Is there some way to tell it to keep the 3 most recent, for example? Or better yet, keep the past 7 days, and...

For what it's worth, I temporarily switched the backup type to SUSPEND and all of these errors went away and everything is backing up fine now... With the exception that each machine is down for ~1-2 hours per night now... Any ideas on how I can get snapshots to work properly? I've left 16GB...

Nobody has any idea on this? It's happening on two machines, it can't just be a coincidence...

# pveversion -v pve-manager: 1.5-8 (pve-manager/1.5/4674) running kernel: 2.6.18-2-pve proxmox-ve-2.6.18: 1.5-5 pve-kernel-2.6.18-2-pve: 2.6.18-5 qemu-server: 1.1-11 pve-firmware: 1.0-3 libpve-storage-perl: 1.0-10 vncterm: 0.9-2 vzctl: 3.0.23-1pve8 vzdump: 1.2-5 vzprocps: 2.0.11-1dso2 vzquota...

I just built 2 brand new machines, fresh everything: Gigabyte Motherboards AMD Phenom(tm) 9850 Quad-Core Processors Highpoint 2640x4 RAID controller w/4 seagate drives in RAID-10 configuration 1x500GB Hitachi drive for booting 1x2TB Hitachi drive for backups I get tons of these: EXT4-fs error...

I'm not sure if my problem is related or not, but I too have been getting bus reset errors on 2 brand new server builds using the Highpoint 2640x4 RAID controller in a RAID-10 setup with 4 brand new seagate hard drives...

What I do personally is number my VM's with the last 2 octets of that machines IP address which may or may not work for you depending on how static your network is... Say for example, you have a webserver at 101.102.103.104, I would make it's VMID 103104...

If I'm not mistaken, that's EXACTLY what it is - a bind-mount.... So it's not using any additional disk space, even though it looks like it.

I suppose if I was running 50 KVM's that might work, but I'm not.. I'm just running regular VM's, and grepping a process out just shows the process, not which VM it belongs to... # ps aux | grep 8440 root 8440 0.0 0.0 1980 696 ? Ss Mar09 0:01 init [2] *** DING ****...

Umm.... I'm not sure what this message is in response to... But as you can see in post #5 above, I did do an apt-get update before I tried the apt-get install and it's a no-go... But then in post #6 I just downloaded the package manually from debian and did a dpkg -i, which got it to work, but...

I found it here: http://packages.debian.org/lenny/amd64/atop/download downloaded, and installed it.. I don't quite understand it yet, but this is what I get. # atop -d ATOP - server01 2010/03/11 18:35:39 208034 seconds elapsed PRC | sys 92m14s | user 81m21s | #proc...

# apt-get update # apt-get install atop Reading package lists... Done Building dependency tree Reading state information... Done E: Couldn't find package atop (default v1.5 installation) # cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian lenny main contrib deb...

Well, that output is actually invalid because the system is overloaded... ;) Before we went live, I did do some testing and this is what I had. Bonnie++ was reporting 130MB/sec sequential writes and 265MB/sec sequential reads and Dbench with 10 threads reported 207MB/sec throughput...

So I have a machine (Quad core w/8GB RAM, VM's on a RAID-10 w/4 7200 RPM drives formatted as EXT4) running ProxMox v1.5 and about 30 VM's. Top shows: top - 10:19:35 up 2 days, 1:31, 4 users, load average: 18.07, 18.91, 18.25 Tasks: 792 total, 4 running, 788 sleeping, 0 stopped, 0...