HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- about bad block =off
Operating System - HP-UX
1826797
Members
3110
Online
109703
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
02-28-2006 12:13 PM
02-28-2006 12:13 PM
about bad block =off
Hi everyone,
HP said in root,swap and dump devce, the option bad block should be off, I think there is problem exist, if system read a bad block of root device, because bad block=off, so system will not mark the bad block ,and try to read the block continually,this will consume all CPU time and system has no any other CPU time to handle the request come from client! although we have mirror disk, system will not swith to another system disk!!! I think this is a big problem. how can us sovle it ?
thanks
HP said in root,swap and dump devce, the option bad block should be off, I think there is problem exist, if system read a bad block of root device, because bad block=off, so system will not mark the bad block ,and try to read the block continually,this will consume all CPU time and system has no any other CPU time to handle the request come from client! although we have mirror disk, system will not swith to another system disk!!! I think this is a big problem. how can us sovle it ?
thanks
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2006 06:26 PM
02-28-2006 06:26 PM
Re: about bad block =off
HI,
who can tell me how to understand it ?
Thanks.
Rayche
who can tell me how to understand it ?
Thanks.
Rayche
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2006 09:14 PM
02-28-2006 09:14 PM
Re: about bad block =off
Interesting question.
Actually "the system will mark the block BAD, and will not try to read it again".
Bad block relocation policy has two switch "n,N":
[n]: Prevent bad block relocation.
Upon media failure, LVM will mark the failed block as bad in the Bad Block Directory, but will NOT attempt to relocate the bad block to a new location on disk. Future I/O requests which contain the bad block will return with an I/O error. No attempt will be made to access the bad block.
[N]: Disable bad block relocation and the Bad Block Directory.
Upon a media failure, LVM will NOT attempt to relocate the bad block. In addition it will NOT enter the block in the Bad Block Directory. LVM will have no record of the block being bad, and will attempt to access it on future I/O requests.
Maybe this is intended to let you know if critical LVs have bad blocks.
As for mirror copy switching it is triggered by a failed PV.
Actually "the system will mark the block BAD, and will not try to read it again".
Bad block relocation policy has two switch "n,N":
[n]: Prevent bad block relocation.
Upon media failure, LVM will mark the failed block as bad in the Bad Block Directory, but will NOT attempt to relocate the bad block to a new location on disk. Future I/O requests which contain the bad block will return with an I/O error. No attempt will be made to access the bad block.
[N]: Disable bad block relocation and the Bad Block Directory.
Upon a media failure, LVM will NOT attempt to relocate the bad block. In addition it will NOT enter the block in the Bad Block Directory. LVM will have no record of the block being bad, and will attempt to access it on future I/O requests.
Maybe this is intended to let you know if critical LVs have bad blocks.
As for mirror copy switching it is triggered by a failed PV.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2006 12:31 PM
03-01-2006 12:31 PM
Re: about bad block =off
thanks for Vanadio's help. In fact,I met the problem last time, I used RP8400 machine, and at that time, when I try to telnet to the machine, there was no response, so I went to DC room to check using console, I found it was very slowly when I typed command, then I use sar command to check,I found disk wio is 100%, I used mstm command to find there was bad block error. I do not understand why system try to read a bad block error ? in that system, root,swap and dump's bad block option is off, other is on.
Thanks.
Thanks.
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP