Project

General

Profile

Actions

Bug #13392

closed

mira074 has a bad root disk

Added by Zack Cerza over 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Category:
Test Node
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

http://pulpito.front.sepia.ceph.com/nodes/mira074.front.sepia.ceph.com/

[4113186.102659] sd 0:0:0:0: [sda] Unhandled sense code
[4113186.107656] sd 0:0:0:0: [sda]
[4113186.110989] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[4113186.116753] sd 0:0:0:0: [sda]
[4113186.120083] Sense Key : Medium Error [current]
[4113186.124843] Info fld=0x0
[4113186.127567] sd 0:0:0:0: [sda]
[4113186.130902] Add. Sense: Unrecovered read error
[4113186.135660] sd 0:0:0:0: [sda] CDB:
[4113186.139340] Read(10): 28 00 39 c0 08 20 00 00 08 00
[4113186.144636] end_request: I/O error, dev sda, sector 968886304
[4113186.150649] EXT4-fs error (device sda1): ext4_wait_block_bitmap:471: comm libvirtd: Cannot read block bitmap - block_group = 3700, block_bitmap = 121110532
[4113186.164927] Aborting journal on device sda1-8.
[4113186.169631] EXT4-fs (sda1): Remounting filesystem read-only
[4113186.175400] EXT4-fs error (device sda1) in ext4_free_blocks:4858: IO failure
[4113186.182762] ------------[ cut here ]------------
[4113186.187600] WARNING: CPU: 6 PID: 1674 at /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0()
[4113186.199894] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs vhost_net vhost macvtap macvlan ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi bridge stp llc coretemp gpio_ich kvm_intel kvm joydev i7core_edac edac_core dm_multipath serio_raw scsi_dh mac_hid lpc_ich scsi_transport_iscsi lp nfsd auth_rpcgss parport nfs_acl nfs lockd sunrpc fscache xfs btrfs xor raid6_pq libcrc32c hid_generic usbhid hid e1000e ahci ptp psmouse libahci pps_core arcmsr
[4113186.268281] CPU: 6 PID: 1674 Comm: libvirtd Not tainted 3.13.0-32-generic #57-Ubuntu
[4113186.276326] Hardware name: Supermicro X8SIL/X8SIL, BIOS 1.1 05/27/2010
[4113186.283147]  0000000000000009 ffff880427fd7b78 ffffffff8171bcb4 0000000000000000
[4113186.291027]  ffff880427fd7bb0 ffffffff810676cd ffff880122bfcc98 ffff8804266277d8
[4113186.299038]  ffff8804245f2a20 ffffffff81834f80 0000000000000a9f ffff880427fd7bc0
[4113186.306912] Call Trace:
[4113186.309556]  [<ffffffff8171bcb4>] dump_stack+0x45/0x56
[4113186.314986]  [<ffffffff810676cd>] warn_slowpath_common+0x7d/0xa0
[4113186.321275]  [<ffffffff810677aa>] warn_slowpath_null+0x1a/0x20
[4113186.327390]  [<ffffffff8126c7b2>] __ext4_handle_dirty_metadata+0x1a2/0x1c0
[4113186.334630]  [<ffffffff81265c2b>] __ext4_ext_dirty+0x4b/0x80
[4113186.340623]  [<ffffffff812663ee>] ext4_ext_rm_leaf+0x3ee/0x8f0
[4113186.346760]  [<ffffffff81268eac>] ext4_ext_remove_space+0x31c/0x7e0
[4113186.353317]  [<ffffffff8126b250>] ext4_ext_truncate+0xb0/0xe0
[4113186.359460]  [<ffffffff812438e9>] ext4_truncate+0x379/0x3c0
[4113186.365330]  [<ffffffff812444a1>] ext4_evict_inode+0x491/0x4f0
[4113186.371458]  [<ffffffff811d7d70>] evict+0xb0/0x1b0
[4113186.376545]  [<ffffffff811d8585>] iput+0xf5/0x180
[4113186.381610]  [<ffffffff811ccf8e>] do_unlinkat+0x18e/0x2b0
[4113186.387301]  [<ffffffff81020d45>] ? syscall_trace_enter+0x145/0x250
[4113186.393857]  [<ffffffff811cdee6>] SyS_unlink+0x16/0x20
[4113186.399340]  [<ffffffff8172c87f>] tracesys+0xe1/0xe6
[4113186.404584] ---[ end trace 9c9e121193c46ee6 ]---
[4113186.409494] EXT4-fs error (device sda1): ext4_ext_rm_leaf:2719: inode #49283113: block 121001984: comm libvirtd: journal_dirty_metadata failed: handle type 5 started at line 241, credits 551/11, errcode -30
[4113186.428256] EXT4-fs error (device sda1) in ext4_ext_remove_space:3006: Journal has aborted
[4113186.436796] EXT4-fs error (device sda1) in ext4_ext_truncate:4544: Journal has aborted
[4113186.445041] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4869: Journal has aborted
[4113186.453952] EXT4-fs error (device sda1) in ext4_truncate:3792: Journal has aborted
[4113186.461770] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4869: Journal has aborted
[4113186.470652] EXT4-fs error (device sda1) in ext4_orphan_del:2685: Journal has aborted
[4113186.478738] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4869: Journal has aborted
[4114110.122210] br-front: port 2(vnet0) entered disabled state
[4114110.128332] device vnet0 left promiscuous mode
[4114110.133122] br-front: port 2(vnet0) entered disabled state
[4114110.922643] type=1400 audit(1444035423.172:4873): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-7dcadeb1-0b37-4772-b1f0-952953776209" pid=7865 comm="apparmor_parser" 
[4114837.727046] br-front: port 8(vnet6) entered disabled state
[4114837.733294] device vnet6 left promiscuous mode
[4114837.738055] br-front: port 8(vnet6) entered disabled state
[4114838.354813] type=1400 audit(1444036150.981:4874): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-3243f6f9-2c1e-4b01-b24b-0dde2a83705c" pid=7967 comm="apparmor_parser" 
[4199769.091988] EXT4-fs (sda1): error count: 10
[4199769.096389] EXT4-fs (sda1): initial error at 1444034497: ext4_wait_block_bitmap:471
[4199769.104277] EXT4-fs (sda1): last error at 1444034498: ext4_reserve_inode_write:4869: inode 49283113: block 121001984

Related issues 1 (0 open1 closed)

Related to sepia - Bug #13394: "libvir: error : cannot create file" in vps runsDuplicate10/06/2015

Actions
Actions #1

Updated by Zack Cerza over 8 years ago

  • Description updated (diff)
Actions #2

Updated by David Galloway over 8 years ago

  • Assignee set to David Galloway
Actions #3

Updated by David Galloway about 8 years ago

  • Category set to Test Node
Actions #4

Updated by David Galloway about 8 years ago

  • Status changed from New to Resolved

Drive got replaced on 28JAN2016 and host was reimaged

Actions

Also available in: Atom PDF