LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices

Reply
 
Search this Thread
Old 04-11-2013, 02:16 AM   #1
SukkoPera
LQ Newbie
 
Registered: Jan 2012
Location: Northern Italy
Distribution: Slackware, what else?
Posts: 15

Rep: Reputation: Disabled
dm-linear: Device lookup failed


Hi everybody,

here at work we have a few virtual servers, running on Proxmox. There are nightly backups scheduled for each of them, through Proxmox itself.

One day, backups on one physical node started failing with the following error:

Code:
command 'lvcreate --size 1024M --snapshot --name 'vzsnap-ve2-0' '/dev/ve2ds1-sync/vm-201-disk-1'' failed: exit code 5
Note: /dev/ve2ds1-sync is an LVM VG that is replicated on another machine through drbd for redundancy. vm-201-disk-1 is the LV that is used as virtual disk for one of the virtual machines, but the same happens for all VGs.

Some more info is available in the logs:

Code:
Mar 11 01:00:03 INFO:   device-mapper: create ioctl on ve2ds1--sync-vzsnap--ve2--0 failed: Device or resource busy
Mar 11 01:00:03 INFO:   Aborting. Failed to activate snapshot exception store.
So it seems LVM cannot create LVs anymore. dmesg reports a few errors:

Code:
device-mapper: ioctl: device doesn't appear to be in the dev hash table.
device-mapper: table: 253:9: linear: dm-linear: Device lookup failed
device-mapper: ioctl: error adding target to table
The LV shows up in dmsetup ls:

Code:
root@ve2:~# dmsetup ls
ve2ds1--sync-vzsnap--ve2--0     (253:9)
I can remove it with dmsetup remove but this doesn't solve anything. What can I do? I might try rebooting the server, but that is really the last resort, since these servers are production ones.

Any suggestions? Thanks in advance!

Last edited by SukkoPera; 04-11-2013 at 02:20 AM.
 
Old 04-12-2013, 12:56 PM   #2
smallpond
Senior Member
 
Registered: Feb 2011
Location: Massachusetts, USA
Distribution: Fedora
Posts: 1,459

Rep: Reputation: 355Reputation: 355Reputation: 355Reputation: 355
Exit code 5 probably means EIO - an I/O error occurred.
Check the status of your LVM with
Code:
lvdisplay /dev/ve2ds1-sync/vm-201-disk-1
Also check your log for disk errors.
 
Old 04-15-2013, 02:41 AM   #3
SukkoPera
LQ Newbie
 
Registered: Jan 2012
Location: Northern Italy
Distribution: Slackware, what else?
Posts: 15

Original Poster
Rep: Reputation: Disabled
Thanks for the help, smallpond. The LVM is ok, AFAIK:

Code:
root@ve2:~# lvdisplay /dev/ve2ds1-sync/vm-201-disk-1
  --- Logical volume ---
  LV Path                /dev/ve2ds1-sync/vm-201-disk-1
  LV Name                vm-201-disk-1
  VG Name                ve2ds1-sync
  LV UUID                v4HJgO-ce1E-uEtm-OlKH-149O-PsGK-TRnnTq
  LV Write Access        read/write
  LV Creation host, time ve2, 2012-12-02 17:28:10 +0100
  LV Status              available
  # open                 1
  LV Size                20.00 GiB
  Current LE             5120
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:5
Also, the disks are OK, as they are hardware RAID1 (MegaRAID) and we have no failures ATM.
 
Old 04-15-2013, 03:06 AM   #4
whizje
Member
 
Registered: Sep 2008
Location: The Netherlands
Distribution: Slackware64 current
Posts: 582

Rep: Reputation: 129Reputation: 129
test the disks with smartctl -t long /dev/sda
 
Old 04-15-2013, 06:58 AM   #5
SukkoPera
LQ Newbie
 
Registered: Jan 2012
Location: Northern Italy
Distribution: Slackware, what else?
Posts: 15

Original Poster
Rep: Reputation: Disabled
I can't use smartctl, as my disks are logical disks and the physical disks are hidden by the MegaRAID controller. Anyway I have started a RAID consistency check with MegaRAID's utility, and all my disks are OK.
 
Old 05-08-2013, 07:20 AM   #6
SukkoPera
LQ Newbie
 
Registered: Jan 2012
Location: Northern Italy
Distribution: Slackware, what else?
Posts: 15

Original Poster
Rep: Reputation: Disabled
Just for reference: we finally solved this rebooting everything.
 
  


Reply

Tags
lvm2


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
mkrescue Fatal: device-mapper: only linear boot device supported Molly Slackware 5 01-06-2009 04:35 PM
Lilo wont write to MBR, Fatal error: only linear boot device supported agentc0re Slackware 2 03-16-2008 02:23 PM
DNS lookup failed DropHit Linux - General 1 12-29-2007 03:25 AM
LXer: Linear Optimization with the GNU Linear Programming Kit LXer Syndicated Linux News 0 08-12-2006 04:21 AM
device-mapper: dm-linear: Device lookup failed tajo01 Linux - Kernel 1 05-18-2006 08:22 PM


All times are GMT -5. The time now is 11:53 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration