- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Message in syslog of bad dir - mangled entry
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
09-29-2000 08:20 AM
09-29-2000 08:20 AM
/stand: bad dir ino 3 at offset ####: mangled entry
The directory at inode 3 is /stand/lost+found. The lost+found directory is empty. I cannot find anything about this in the knowledge databases. Has anyone ever run across this? And if so can you please let me know what could have caused it and how to fix the problem. Thanks for your help. James
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2000 08:32 AM
09-29-2000 08:32 AM
SolutionI found three documents for you. Two are very old (ca. 1994) and apply to very early releases of 10.x -- #1653101584 & #1653107946. In part they suggest not to run "fsck -n" on mounted filesystems.
The third document applies to 11.0 (#1653277301) and again deals with fsck on HFS file systems.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2000 08:34 AM
09-29-2000 08:34 AM
Re: Message in syslog of bad dir - mangled entry
Ah, too fast on the submit button. I meant to add that you probably should have, if you don't, a relatively current set of LVM cumulative patches.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2000 10:37 AM
09-29-2000 10:37 AM
Re: Message in syslog of bad dir - mangled entry
To solve your problem, remove the 'lost+found' directory, and recreate it using the command mklost+found(1m).
Hope this helps,
Rik.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2000 06:36 PM
09-29-2000 06:36 PM