Dmesg doesn't give any new clues that I can tell. The underlying hardware is an EMC DMX2000 array, which is a RAID box of some type.
zlinuxhdxgwdev1:/etc/cron.daily # dmesg Linux version 2.6.16.60-0.27-default (ge...@buildhost) (gcc version 4.1.2 20070115 (SUSE Linux)) #1 SMP Mon Jul 28 13:08:09 UTC 2008 We are running under VM (64 bit mode) Detected 1 CPU's Boot cpu address 0 On node 0 totalpages: 65536 DMA zone: 65536 pages, LIFO batch:15 DMA32 zone: 0 pages, LIFO batch:0 Normal zone: 0 pages, LIFO batch:0 HighMem zone: 0 pages, LIFO batch:0 Built 1 zonelists Kernel command line: root=/dev/dasda1 dasd=100-101,300-301 vmpoff=LOGOFF TERM=dumb BOOT_IMAGE=0 PID hash table entries: 2048 (order: 11, 65536 bytes) Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Memory: 243260k/262144k available (4749k kernel code, 0k reserved, 2015k data, 212k init) Calibrating delay loop... 3643.80 BogoMIPS (lpj=18219008) Security Framework v1.0.0 initialized Mount-cache hash table entries: 256 checking if image is initramfs... it is Freeing initrd memory: 3115k freed cpu 0 phys_idx=0 vers=FF ident=09CD13 machine=2097 unused=8000 Brought up 1 CPUs migration_cost=1000 NET: Registered protocol family 16 debug: Initialization complete cio: Channel measurements not available, continuing. audit: initializing netlink socket (disabled) audit(1235057434.788:1): initialized Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered (default) io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 Channel measurement facility using extended format (autodetected) NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 3, 32768 bytes) TCP established hash table entries: 16384 (order: 6, 262144 bytes) TCP bind hash table entries: 16384 (order: 6, 262144 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered NET: Registered protocol family 1 Freeing unused kernel memory: 212k freed dasd(eckd): 0.0.0100: 3390/0C(CU:3990/01) Cyl:3338 Head:15 Sec:224 dasd(eckd): 0.0.0100: (4kB blks): 2403360kB at 48kB/trk compatible disk layout dasda:VOL1/ 0X0100: dasda1 dasda2 dasd(eckd): 0.0.0101: 3390/0C(CU:3990/01) Cyl:3338 Head:15 Sec:224 dasd(eckd): 0.0.0101: (4kB blks): 2403360kB at 48kB/trk compatible disk layout dasdb:VOL1/ 0X0101: dasdb1 dasd(fba): 0.0.0300: 9336/10(CU:6310/80) 32MB at(512 B/blk) dasdc:CMS1/ LXSWAP(MDSK): dasdc1 kjournald starting. Commit interval 5 seconds EXT3 FS on dasda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. Adding 32484k swap on /dev/dasdc1. Priority:-1 extents:1 across:32484k device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: [email protected] dm-netlink version 0.0.2 loaded vmur: z/VM virtual unit record device driver loaded. qdio: loading QDIO base support version 2 NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver qeth: loading qeth S/390 OSA-Express driver qeth: Device 0.0.0900/0.0.0901/0.0.0902 is a Guest LAN QDIO card (level: V532) with link type GuestLAN QDIO (portname: dontcare) qeth: Hardware IP fragmentation not supported on eth0 qeth: VLAN enabled qeth: Multicast enabled qeth: IPV6 enabled qeth: Broadcast enabled qeth: Using SW checksumming on eth0. qeth: Outbound TSO not supported on eth0 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. loop: loaded (max 8 devices) kjournald starting. Commit interval 5 seconds EXT3 FS on dm-0, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-3, internal journal EXT3-fs: mounted filesystem with ordered data mode. eth0: no IPv6 routers present device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table process `sitar' is using deprecated sysctl (syscall) net.ipv6.neigh.default.base_reachable_time; Use net.ipv6.neigh.default.base_reachable_time_ms instead. device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table SCSI subsystem initialized NET: Registered protocol family 17 device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Scott Rohling Sent: Thursday, February 26, 2009 6:22 PM To: [email protected] Subject: Re: Strange LVM Device Mapper messages does 'dmesg' provide any more clues? Scott On Thu, Feb 26, 2009 at 3:28 PM, Quay, Jonathan (IHG) <[email protected] > wrote: > I'm getting this message every few hours since installation of a > SLES10SP2 system: > > > > kernel: device-mapper: table: 253:4: mirror: Device lookup failure > > kernel: device-mapper: ioctl: error adding target to table > > > > I've looked through the device mapper stuff and I can't find any reason > for this system to think it's got a minor at 4, or a mirror. What might > be causing these messages, and what can I do beside the obvious LVM and > Device Mapper commands to troubleshoot? Or maybe the answer is staring > me in the face and I am missing it. > > > > > > # df -h > > Filesystem Size Used Avail Use% Mounted on > > /dev/dasda1 373M 111M 244M 32% / > > udev 121M 92K 121M 1% /dev > > /dev/mapper/system--vg-opt--lv > > 372M 37M 317M 11% /opt > > /dev/mapper/system--vg-tmp--lv > > 372M 17M 337M 5% /tmp > > /dev/mapper/system--vg-usr--lv > > 2.0G 807M 1.1G 43% /usr > > /dev/mapper/system--vg-var--lv > > 496M 117M 354M 25% /var > > > > zlinuxhdxgwdev1:/dev/mapper # ls -l > > total 0 > > lrwxrwxrwx 1 root root 16 Feb 19 10:30 control -> ../device-mapper > > brw------- 1 root root 253, 0 Feb 19 10:30 system--vg-opt--lv > > brw------- 1 root root 253, 1 Feb 19 10:30 system--vg-tmp--lv > > brw------- 1 root root 253, 2 Feb 19 10:31 system--vg-usr--lv > > brw------- 1 root root 253, 3 Feb 19 10:31 system--vg-var-lv > > > > zlinuxhdxgwdev1:/dev/disk/by-id # vgldisplay > > --- Volume group --- > > VG Name system-vg > > System ID > > Format lvm2 > > Metadata Areas 2 > > Metadata Sequence No 5 > > VG Access read/write > > VG Status resizable > > MAX LV 0 > > Cur LV 4 > > Open LV 4 > > Max PV 0 > > Cur PV 2 > > Act PV 2 > > VG Size 4.20 GB > > PE Size 4.00 MB > > Total PE 1076 > > Alloc PE / Size 832 / 3.25 GB > > Free PE / Size 244 / 976.00 MB > > VG UUID uatqaW-r3JL-zUn7-7hxw-gLIu-2WnW-uOYl5G > > > > zlinuxhdxgwdev1:/dev/disk/by-id # pvscan > > PV /dev/dasda2 VG system-vg lvm2 [1.91 GB / 976.00 MB free] > > PV /dev/dasdb1 VG system-vg lvm2 [2.29 GB / 0 free] > > Total: 2 [4.20 GB] / in use: 2 [4.20 GB] / in no VG: 0 [0 ] > > zlinuxhdxgwdev1:/dev/disk/by-id # lvdisplay > > --- Logical volume --- > > LV Name /dev/system-vg/opt-lv > > VG Name system-vg > > LV UUID pF6IWB-qBVD-0KIc-tFJR-YVsb-WcC6-coKce8 > > LV Write Access read/write > > LV Status available > > # open 1 > > LV Size 384.00 MB > > Current LE 96 > > Segments 1 > > Allocation inherit > > Read ahead sectors 0 > > Block device 253:0 > > > > --- Logical volume --- > > LV Name /dev/system-vg/tmp-lv > > VG Name system-vg > > LV UUID FhVfHT-lbda-9ZNp-Dyks-uXWI-0QNA-QUBFQq > > LV Write Access read/write > > LV Status available > > # open 1 > > LV Size 384.00 MB > > Current LE 96 > > Segments 1 > > Allocation inherit > > Read ahead sectors 0 > > Block device 253:1 > > > > --- Logical volume --- > > LV Name /dev/system-vg/usr-lv > > VG Name system-vg > > LV UUID 72dCIX-C0LC-Vkps-CwiD-oKLn-rNzq-1Q6m6i > > LV Write Access read/write > > LV Status available > > # open 1 > > LV Size 2.00 GB > > Current LE 512 > > Segments 2 > > Allocation inherit > > Read ahead sectors 0 > > Block device 253:2 > > > > --- Logical volume --- > > LV Name /dev/system-vg/var-lv > > VG Name system-vg > > LV UUID eBnq2p-L1Py-14wv-Y4Uq-mzJ3-CmXU-BF2ypb > > LV Write Access read/write > > LV Status available > > # open 1 > > LV Size 512.00 MB > > Current LE 128 > > Segments 1 > > Allocation inherit > > Read ahead sectors 0 > > Block device 253:3 > > > > zlinuxhdxgwdev1:/var/log # dmsetup info -c > > Name Maj Min Stat Open Targ Event UUID > > system--vg-opt--lv 253 0 L--w 1 1 0 > LVM-uatqaWr3JLzUn77hxwgLIu2WnWuOYl5GpF6IWBqBVD0KIctFJRYVsbWcC6coKce8 > > system--vg-tmp--lv 253 1 L--w 1 1 0 > LVM-uatqaWr3JLzUn77hxwgLIu2WnWuOYl5GFhVfHTlbda9ZNpDyksuXWI0QNAQUBFQq > > system--vg-var--lv 253 3 L--w 1 1 0 > LVM-uatqaWr3JLzUn77hxwgLIu2WnWuOYl5GeBnq2pL1Py14wvY4UqmzJ3CmXUBF2ypb > > system--vg-usr--lv 253 2 L--w 1 2 0 > LVM-uatqaWr3JLzUn77hxwgLIu2WnWuOYl5G72dCIXC0LCVkpsCwiDoKLnrNzq1Q6m6i > > > > zlinuxhdxgwdev1:/dev/mapper # dmsetup table > > system--vg-opt--lv: 0 786432 linear 94:5 384 > > system--vg-tmp--lv: 0 786432 linear 94:2 384 > > system--vg-var--lv: 0 1048576 linear 94:2 967040 > > system--vg-usr--lv: 0 4014080 linear 94:5 786816 > > system--vg-usr--lv: 4014080 180224 linear 94:2 786816 > > > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
