Hi list,

this is using systemimager 4.0.0-1, 3.9.6-1 and 3.8.0-1
installing SLES9 SP3, 2.6.5-7.287-smp

creation of logical volumes errors out with a device-mapper message:

lvcreate -L1G -n opt data0
 device-mapper: table ioctl failed: No such device or address
 Failed to activate new LV


The LV gets created, but the system can not find it via the /dev filesystem:
# lvs
  LV    VG      Attr    LSize   Origin  Snap%   Move    Log     Copy%
  opt   data0   -wi-d-  1.00G

# lvchange -a y data0/opt
 device-mapper: table ioctl failed: No such device or address
  deps: task run failed for (253:4)
 Failed to add device (253:4) to dtree


lvdisplay shows the LV as expected (/dev/data0/opt) including its UUID, but
divice-mapper doesn't know how to access it.  dm-mod is loaded.

I can see entry for the new LV under /dev/mapper/data0-opt, but nothing under
/dev/data0/opt, which would usually be a symlink to the above.  /dev/data0
never gets created.  And there is nothing in /proc/partitions either.

# ls -l /dev/mapper/data0-opt
brw-------      1 root  root    253,    4 Nov  8 00:40 /dev/mapper/data0-opt

# ls -l /dev/data0
ls: /dev/data0: No such file of directory


I do not get this error when installing a SLES10 image.  I suspect this is
because boel lvm is expecting devices via udev, but SLES9 uses a static /dev?
This is a wild guess.  The other thought is my goldenclient kernel version
doesn't like boel lvm.  I tried with systemimager-3.9.6.-1 and 3.8.0-1 also
(goldenclient and server), but got the same error.



-- 

-ashley

Did you try poking at it with a stick?


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to