- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: lvm error
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2005 01:12 AM
тАО05-15-2005 01:12 AM
lvm error
Device name cannot determine name of device major number minor number
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2005 01:39 AM
тАО05-15-2005 01:39 AM
Re: lvm error
Can you check the device file in /dev/
Try to see whether the lvol is shown in vgdisplay.
vgdisplay -v /dev/
Sudeesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2005 06:28 AM
тАО05-15-2005 06:28 AM
Re: lvm error
check if patches PHCO_7817 and PHCO_20330 are relevant to your situation.
regards,
John K.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2005 08:41 AM
тАО05-15-2005 08:41 AM
Re: lvm error
try insf -e
try rebooting..
just try this ..many funny problems of mine have got resolved after a reboot.
Also pls Cross check the commands that you have given.
regards,
Syam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2005 04:28 PM
тАО05-15-2005 04:28 PM
Re: lvm error
#pvcreate /dev/rdsk/cxdxtx
#mkdir /dev/vg01
#cd /dev/vg01
#mknod group c 64 0x010000
#vgcreate /dev/vg01 /dev/dsk/cxdxtx
#lvcreate -L
#newfs -F vxfs /dev/vg01/rvol1
#mount /dev/vg01/vol1 /
case vg00
#lvcreate -L
#newfs -F vxfs /dev/vg00/r
#mount /dev/vg01/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2005 04:40 PM
тАО05-15-2005 04:40 PM
Re: lvm error
What is the o/p of "ll /dev/vgxx". (Use your vg name).
The output should be similar to:
ll /dev/vg00
total 0
crw-r----- 1 root sys 64 0x000000 Jan 29 08:21 group
brw-r----- 1 root sys 64 0x000001 Jan 29 08:21 lvol1
brw-r----- 1 root sys 64 0x000002 Jan 29 08:21 lvol2
brw-r----- 1 root sys 64 0x000003 Jan 29 08:21 lvol3
brw-r----- 1 root sys 64 0x000004 Jan 29 08:21 lvol4
brw-r----- 1 root sys 64 0x000005 Jan 29 08:21 lvol5
brw-r----- 1 root sys 64 0x000006 Jan 29 08:21 lvol6
brw-r----- 1 root sys 64 0x000007 Jan 29 08:21 lvol7
brw-r----- 1 root sys 64 0x000008 Jan 29 08:21 lvol8
crw-r----- 1 root sys 64 0x000001 Jan 29 08:21 rlvol1
crw-r----- 1 root sys 64 0x000002 Jan 29 08:21 rlvol2
crw-r----- 1 root sys 64 0x000003 Jan 29 08:21 rlvol3
crw-r----- 1 root sys 64 0x000004 Jan 29 08:21 rlvol4
crw-r----- 1 root sys 64 0x000005 Jan 29 08:21 rlvol5
crw-r----- 1 root sys 64 0x000006 Jan 29 08:21 rlvol6
crw-r----- 1 root sys 64 0x000007 Jan 29 08:21 rlvol7
crw-r----- 1 root sys 64 0x000008 Jan 29 08:21 rlvol8
If some discrepancy is noticed, than check whether you can display CG and LV (vgdisplay and lvdisplay).
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2005 05:38 PM
тАО05-15-2005 05:38 PM
Re: lvm error
The ll of /dev/vg* directory would have helped us understand this issue more better. But never the less, I guess the files meant for LV's in the concerned /dev/vg* dir in your box is a regular file and not a Block or Character file. May be thats the reason why the error message says.."failed to get major and minor" number.. Please be aware i was racking my grey matter about this from my residence and had no access to a HPUX box. So i couldn't simulate the error.
Anyway...i think , you need to check the /dev/vg* dir as others have suggested...
Kind regards
Senthil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2005 06:46 PM
тАО05-15-2005 06:46 PM
Re: lvm error
See if you r able to see the information of newly created lv.
# lvdisplay /dev/vgxx/lvname
It shoudl display somethign like this:
LV Name /dev/vg00/lvol3
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 5096
Current LE 637
Allocated PE 637
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default
See the LV Status here which should be available.
In case it is unavailable for any reasons try doing:
# lvchange -a y /dev/vgxx/lvname
Hope that works.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2005 09:52 PM
тАО05-15-2005 09:52 PM
Re: lvm error
Check the output of ll /dev/vg* it shud give the major and minor no. for all logical volumes.
also check :- pvdisplay -v /dev/vgxx/
lvstatus in the above o/p shud give available
make sure that you r creating the file system on the new lvol by using the below command-
newfs -F vxfs /dev/vg00/rlvolx
hope this will help u.
bye
Sumit