HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: fsck on disks fail
Operating System - HP-UX
1837222
Members
2377
Online
110115
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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-10-2003 06:32 PM
11-10-2003 06:32 PM
fsck on disks fail
Hi,
We have an XP256 array & we synchronized the BC vg's but when the BC vg's were in PAIRED status & we issued a split command, during the fsck phase the below error is prompted & the split fails:
Now we need to mount the new logical volumes on the BC mount points
log replay in progress
vxfs fsck: file system does not contain a valid log
vxfs fsck: cannot perform log replay
file system is not clean, full fsck required
full file system check required, exiting ...
vxfs mount: /dev/vg_name/lvol1 is corrupted. needs checking
ERROR: The command - mount /dev/vg_name/lvol1 /mount_pt failed.
Anyone have any ideas on resolution?
Thanks in advance.
We have an XP256 array & we synchronized the BC vg's but when the BC vg's were in PAIRED status & we issued a split command, during the fsck phase the below error is prompted & the split fails:
Now we need to mount the new logical volumes on the BC mount points
log replay in progress
vxfs fsck: file system does not contain a valid log
vxfs fsck: cannot perform log replay
file system is not clean, full fsck required
full file system check required, exiting ...
vxfs mount: /dev/vg_name/lvol1 is corrupted. needs checking
ERROR: The command - mount /dev/vg_name/lvol1 /mount_pt failed.
Anyone have any ideas on resolution?
Thanks in advance.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2003 06:47 PM
11-10-2003 06:47 PM
Re: fsck on disks fail
Hi!
fsck by default is checking only
intent.log. You must try to start
fsck again using "-o full"-option
for full scanning the file system.
Regards,Stan
fsck by default is checking only
intent.log. You must try to start
fsck again using "-o full"-option
for full scanning the file system.
Regards,Stan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2003 08:06 AM
11-13-2003 08:06 AM
Re: fsck on disks fail
Edgar,
If you're using the -full option, be prepared to spend a lot time (depending on the size of the filesystem) hitting the "y" key to correct any inconsistencies fsck finds.
You may want to add the -y option as well (automatically answers "yes" to all prompts generated by fsck). A word of caution, though: answering "yes" to everything can result in some problems (directory and/or inode linking/relinking are the usual suspects that I've come across, but fsck places the suspect files/directories in lost+found for you).
Since these are BCVs, you can always re-synch them with the primaries and try again. That's the beauty of BCVs :)
Hope this helps,
Brian
If you're using the -full option, be prepared to spend a lot time (depending on the size of the filesystem) hitting the "y" key to correct any inconsistencies fsck finds.
You may want to add the -y option as well (automatically answers "yes" to all prompts generated by fsck). A word of caution, though: answering "yes" to everything can result in some problems (directory and/or inode linking/relinking are the usual suspects that I've come across, but fsck places the suspect files/directories in lost+found for you).
Since these are BCVs, you can always re-synch them with the primaries and try again. That's the beauty of BCVs :)
Hope this helps,
Brian
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP