- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Inode errors ???
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
Forums
Discussions
Discussions
Discussions
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
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
01-13-2003 01:19 AM
01-13-2003 01:19 AM
Inode errors ???
I??ve got installed 3 new C3750 Workstations with HPUX 11.00
Since the systems are up and running I receive the following error message:
2 error 6
msgcnt 59011 vxfs: mesg 016: vx_ilisterr - / file system error reading inode 44056
msgcnt 59012 vxfs: mesg 008: vx_direrr: vx_dirlook_4 - / file system inode 35455 block 696382 error 6
thanks for help
Carsten
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2003 01:25 AM
01-13-2003 01:25 AM
Re: Inode errors ???
do full fsck on filesystem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2003 01:26 AM
01-13-2003 01:26 AM
Re: Inode errors ???
#fsck -F vxfs -y -o full /dev/vgxx/lvol...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2003 01:28 AM
01-13-2003 01:28 AM
Re: Inode errors ???
please find the disk or lvol where the inode is located on:
# find / -inum 44056
Then umount the filesystem and run an fsck:
# fsck -o full /dev/rdsk/c...
or
# fsck -o full /dev/vgXY/rlvolX
Regards ...
Armin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2003 01:30 AM
01-13-2003 01:30 AM
Re: Inode errors ???
check your files/dirs
do dd if=your_file/dir of=/dev/null bs=1k
check for errors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2003 05:04 AM
01-13-2003 05:04 AM
Re: Inode errors ???
ENXIO 6 /* No such device or address
Since this is the root filesystem, we can rule out the "no such device" part of the error message, but the "address" is likely the problem. It would appear that the filesystem is trying to access an area beyond the end of the logical volume. Did someone (as root) run the lvreduce command? If so, it will always work but it will also destroy filesystems since LVM commands know nothing about filesystems. LVM simply carves the disk into logical sections and some of these sections may contain a filesystem.
If you've been using lv commands to 'adjust' the size of lvol1, lvol2 or lvol3 (/stand, primary swap and / respectively), you may have some fairly serious problems with the filesystems. If possible, use lvextend to put back the original definitions. Then (download if necessary) use Ignite/UX to backup vg00 and restore interactively so you can adjust all the lvol sizes.
Bill Hassell, sysadmin