Strange problems (ro fs in vm, vm stops)

M

miles

New Member
Mar 4, 2009
6
0
1
Hi everybody,

I am encountering strange problems with my install of proxmox. v1.1 was installed from cd, apt-get update & dist-upgrade, so newest versions run.

In a KVM host when copying many files via scp over network suddenly the vm hangs, in proxmox interface it is listed as "stopped". When restarting, everything is fine.

Sometimes the vm suddenly has read only filesystem.

The following lines are in dmesg. On the host there are no failures in the logs, all other VMs are not affected by the problem of one.

Here the logs:

Code: 
 3283.972014] Buffer I/O error on device vda1, logical block 4605434                                                                          
[ 3283.972014] lost page write due to I/O error on vda1                                                                                        
[ 3283.972014] Buffer I/O error on device vda1, logical block 4605435                                                                          
[ 3283.972014] lost page write due to I/O error on vda1                                                                                        
[ 3283.972014] end_request: I/O error, dev vda, sector 36843223                                                                                
[ 4590.683834] end_request: I/O error, dev vda, sector 58769359                                                                                
[ 4590.684408] __ratelimit: 52 messages suppressed

when it is read only, the following messages occur:

Code: 
52758.430425] end_request: I/O error, dev vda, sector 58770095
[52758.696019] end_request: I/O error, dev vda, sector 58769655
[52759.157652] EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in directory #1835057: rec_len % 4 != 0 - offset=0, inode=1872459720, rec_len=32627, name_len=0
[52759.159162] Aborting journal on device vda1.
[52759.177970] ext3_abort called.
[52759.178375] EXT3-fs error (device vda1): ext3_journal_start_sb: Detected aborted journal
[52759.179391] Remounting filesystem read-only
[52759.192016] Remounting filesystem read-only
[52759.318328] EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in directory #1835061: rec_len % 4 != 0 - offset=0, inode=1872459720, rec_len=32627, name_len=0
[52759.759656] EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in directory #1835054: rec_len % 4 != 0 - offset=0, inode=1872459720, rec_len=32627, name_len=0
[52759.777309] EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in directory #1835065: rec_len % 4 != 0 - offset=0, inode=1872459720, rec_len=32627, name_len=0
[52760.780705] end_request: I/O error, dev vda, sector 58770295
[52761.877625] end_request: I/O error, dev vda, sector 58769871
[52762.231628] EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in directory #1835104: rec_len % 4 != 0 - offset=0, inode=1872459720, rec_len=32627, name_len=0


any suggestions? :(


Thank you!
 
miles said:
Hi everybody,

I am encountering strange problems with my install of proxmox. v1.1 was installed from cd, apt-get update & dist-upgrade, so newest versions run.

In a KVM host when copying many files via scp over network suddenly the vm hangs, in proxmox interface it is listed as "stopped". When restarting, everything is fine.

Sometimes the vm suddenly has read only filesystem.

The following lines are in dmesg. On the host there are no failures in the logs, all other VMs are not affected by the problem of one.

Here the logs:

Code: 
 3283.972014] Buffer I/O error on device vda1, logical block 4605434                                                                          
[ 3283.972014] lost page write due to I/O error on vda1                                                                                        
[ 3283.972014] Buffer I/O error on device vda1, logical block 4605435                                                                          
[ 3283.972014] lost page write due to I/O error on vda1                                                                                        
[ 3283.972014] end_request: I/O error, dev vda, sector 36843223                                                                                
[ 4590.683834] end_request: I/O error, dev vda, sector 58769359                                                                                
[ 4590.684408] __ratelimit: 52 messages suppressed
when it is read only, the following messages occur:

Code: 
52758.430425] end_request: I/O error, dev vda, sector 58770095
[52758.696019] end_request: I/O error, dev vda, sector 58769655
[52759.157652] EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in directory #1835057: rec_len % 4 != 0 - offset=0, inode=1872459720, rec_len=32627, name_len=0
[52759.159162] Aborting journal on device vda1.
[52759.177970] ext3_abort called.
[52759.178375] EXT3-fs error (device vda1): ext3_journal_start_sb: Detected aborted journal
[52759.179391] Remounting filesystem read-only
[52759.192016] Remounting filesystem read-only
[52759.318328] EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in directory #1835061: rec_len % 4 != 0 - offset=0, inode=1872459720, rec_len=32627, name_len=0
[52759.759656] EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in directory #1835054: rec_len % 4 != 0 - offset=0, inode=1872459720, rec_len=32627, name_len=0
[52759.777309] EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in directory #1835065: rec_len % 4 != 0 - offset=0, inode=1872459720, rec_len=32627, name_len=0
[52760.780705] end_request: I/O error, dev vda, sector 58770295
[52761.877625] end_request: I/O error, dev vda, sector 58769871
[52762.231628] EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in directory #1835104: rec_len % 4 != 0 - offset=0, inode=1872459720, rec_len=32627, name_len=0
any suggestions? :(


Thank you!
Click to expand...

pls post your vm config file (/etc/qemu-server/VMID.conf) and your hardware setup (especially disks and controller).
 
Hey, thanks for your help; here we go:

Code: 
vbase1:~# tail -100 /etc/qemu-server/205.conf
name: vm205
ide2: debian-501-amd64-CD-1.iso,media=cdrom
smp: 1
vlan0: virtio=92:82:B4:AA:C0:62
bootdisk: virtio0
virtio0: vm-205-disk.qcow2
ostype: l26
memory: 512
onboot: 1

Hardware is the following:

Intel Core2 Quad Q9300, 6GB Ram
Asus P5E-VM DO Board with ICH9

00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller (rev 02)

/dev/sda: WDC WD1001FALS-00J7B0: 34°C
1000 GB WD HDD


All used hardware is onboard, there is no external raid controller or something. Just this one drive and an identical at sdb for backup. (no raid, just mounted to /backup).

Some VMs are online since 10 days, no errors


Best Regards
 
miles said:
Hey, thanks for your help; here we go:

Code: 
vbase1:~# tail -100 /etc/qemu-server/205.conf
name: vm205
ide2: debian-501-amd64-CD-1.iso,media=cdrom
smp: 1
vlan0: virtio=92:82:B4:AA:C0:62
bootdisk: virtio0
virtio0: vm-205-disk.qcow2
ostype: l26
memory: 512
onboot: 1
Hardware is the following:

Intel Core2 Quad Q9300, 6GB Ram
Asus P5E-VM DO Board with ICH9

00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller (rev 02)

/dev/sda: WDC WD1001FALS-00J7B0: 34°C
1000 GB WD HDD


All used hardware is onboard, there is no external raid controller or something. Just this one drive and an identical at sdb for backup. (no raid, just mounted to /backup).

Some VMs are online since 10 days, no errors


Best Regards
Click to expand...

can you try without virtio?
(for the network use e1000, for the disk use scsi)

some users reported same issues with virtio network enabled.

depending on your grub config maybe you need to adapt the menu.lst.
 
Hey Tom,

without virtio it seems to work. Strange :-/ Thought of using virtio for better performance.

Any suggestions? :)


Thanks for your great work!
 
miles said:
Hey Tom,

without virtio it seems to work. Strange :-/ Thought of using virtio for better performance.

Any suggestions? :)


Thanks for your great work!
Click to expand...

yes, the idea is that virtio should be faster but there is still some stability missing in some situations. we are already testing KVM-85 here and virtio should be also improved so we will see.

the plan is to release Proxmox VE 1.2, based on Lenny and with KVM-85 or KVM-86 (not released yet).
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom