- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: fstyp returns no filesystem type and errors wh...
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
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
тАО11-17-2009 09:39 AM
тАО11-17-2009 09:39 AM
fstyp returns no filesystem type and errors when mounting filesystem after Ignite Clone
vpar 5.04.
Took a production system. make_net_recovery
Built two new systems based on this image.
Everything works.
filesystems mount. But we have some strange issues that must be resolved.
root@mngp01:/root # fstyp /dev/vg00/rlvol6
unknown_fstyp (no matches)
Same deal on the disk or lvol versus rlvol.
There is no fstyp patch in the patch database as far as I can tell. Command works properly on the source system.
root@mngp01:/root # umount /extra
root@mngp01:/root # mount /extra
vxfs mount: V-3-22168: Cannot open portal device: No such file or directory
The search on the vsfs mount issue produces threads when you can't mount. In this case, you CAN mount.
root@mngp01:/root # swlist -l product | grep -i vx
JFS B.11.31 Base VxFS File System 4.1 for HP-UX
OnlineJFS B.11.31 Online features of the VxFS File System
PHCO_37394 1.0 VxFS mkfs(1M) cumulative patch
PHKL_36797 1.0 VxFS4.1 kernel module patch
root@mngp01:/root # swlist -l fileset | grep -i vx
HPOvAcc.HPOVXALANA 1.10.040 HP Software XalanA XSLT Processor -V1.10.0- Package Version 01.10.040
HPOvAcc.HPOVXERCESA 2.07.040 HP Software XercesA XML Parser -V2.7.0- Package Version 02.07.040
HPOvLcore.HPOVXPL 6.00.099 HP Software Cross Platform Component
# JFS B.11.31 Base VxFS File System 4.1 for HP-UX
JFS.VXFS-BASE-KRN B.11.31 The Base VxFS File System Kernel files
JFS.VXFS-BASE-RUN B.11.31 Utilities for JFS management
JFS.VXFS-ENG-A-MAN B.11.31 VXFS Manual Pages for HP-UX
JFS.VXFS-JPN-E-MAN B.11.31 VXFS Manual Pages for HP-UX
JFS.VXFS-JPN-S-MAN B.11.31 VXFS Manual Pages for HP-UX
# OnlineJFS B.11.31 Online features of the VxFS File System
OnlineJFS.VXFS41-AD-RN B.11.31 Utilities for JFS management
# PHCO_37394 1.0 VxFS mkfs(1M) cumulative patch
PHCO_37394.VXFS-BASE-RUN 1.0 JFS.VXFS-BASE-RUN
# PHKL_36797 1.0 VxFS4.1 kernel module patch
PHKL_36797.VXFS-BASE-KRN 1.0 JFS.VXFS-BASE-KRN
On a working system:
root@htgep1:/root # fstyp -v /dev/vg00/lvol4
vxfs
version: 6
f_bsize: 8192
f_frsize: 8192
f_blocks: 272896
f_bfree: 98554
f_bavail: 97785
f_files: 60480
f_ffree: 24608
f_favail: 24608
f_fsid: 1073741828
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 9
f_size: 272896
Everything works, but we can't leave the system in this condition.
Ran swverity \* swconfigure \*
No errors related to vxfs.
root@mngp01:/root # vxupgrade -n 6 /tmp
vxfs vxupgrade: V-3-25236: /dev/vg00/rlvol6: already at disk layout version 6.
Clearly Ignite ate my homework here, but I am mystified as to how to correct this and move on.
Ignite-UX C.7.7.93 HP-UX System Installation Services
root@mngp01:/root # uname -a
HP-UX mngp01 B.11.31 U ia64 0493111981 unlimited-user license
So what do you think?
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Tags:
- fstyp
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 09:45 AM
тАО11-17-2009 09:45 AM
Re: fstyp returns no filesystem type and errors when mounting filesystem after Ignite Clone
This is a complete, shot-in-the-dark, clueless guess, but have you tried running fsck?
I realize that, if it mounts without errors, this is a really stupid suggestion so nobody needs to remind me of my stupidity, thanks anyway.
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 09:47 AM
тАО11-17-2009 09:47 AM
Re: fstyp returns no filesystem type and errors when mounting filesystem after Ignite Clone
Just finished running fsck. Great minds thinks alike.
No joy.
It has to be some stupid Online JFS license file or something.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 09:49 AM
тАО11-17-2009 09:49 AM
Re: fstyp returns no filesystem type and errors when mounting filesystem after Ignite Clone
OnlineJFS.VXFS41-AD-RN B.11.31 Utilities for JFS management
root@mngp01:/root # vxlicrep
Symantec License Manager vxlicrep utility version 3.02.24.0
Copyright (C) 1996-2006 Symantec Corporation. All rights reserved.
Creating a report on all VERITAS products installed on this system
-----------------***********************-----------------
License Key = 3JZU-WDP6-PP6C-P4O4-HS38-NPPO-P
Product Name = VERITAS File System
Serial Number = 1
License Type = PERMANENT
OEM ID = 4095
Features :=
HP_OnlineJFS = Enabled
CPU Count = Not Restricted
Platform = HP-UX
Version = 4.1
File Change Log = Enabled
Maximum number of file systems = Not Restricted
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 09:54 AM
тАО11-17-2009 09:54 AM
Re: fstyp returns no filesystem type and errors when mounting filesystem after Ignite Clone
mismatch : command version 41 - kernel version 35
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 10:00 AM
тАО11-17-2009 10:00 AM
Re: fstyp returns no filesystem type and errors when mounting filesystem after Ignite Clone
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 10:02 AM
тАО11-17-2009 10:02 AM
Re: fstyp returns no filesystem type and errors when mounting filesystem after Ignite Clone
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 10:51 AM
тАО11-17-2009 10:51 AM
Re: fstyp returns no filesystem type and errors when mounting filesystem after Ignite Clone
ll /stand/vmunix*
-rwxr-xr-x 7 root sys 116016712 Oct 6 16:47 vmunix
-rwxr-xr-x 7 root sys 116016712 Oct 6 16:47 vmunix.prev
This is not normal.
Trying to dig up a manual kernel compile procedure. Everything I have used /stand/build which does not exist in 11.31.
This is officially annoying.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 12:02 PM
тАО11-17-2009 12:02 PM
Re: fstyp returns no filesystem type and errors when mounting filesystem after Ignite Clone
http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1311761
particularly Duncan's comments.
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 12:18 PM
тАО11-17-2009 12:18 PM
Re: fstyp returns no filesystem type and errors when mounting filesystem after Ignite Clone
The device was missing.
root@mngp01:/dev # lsdev | grep 97
97 97 vxportal pseudo
Fixed.
As expected. Ignite ate my homework.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com