- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: VA7410 space reservation was desired, but the...
Disk Enclosures
1753774
Members
7180
Online
108799
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
Discussions
Discussions
Forums
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
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
тАО06-19-2006 10:32 PM
тАО06-19-2006 10:32 PM
VA7410 space reservation was desired, but the space left
Hi ALL,
We have RP5405*2(Serviceguard), VA7410, 15*74Gb.
One of 15 disks has yellow indication.
In syslog.log we have a lot of such errors:
vmunix: SCSI: Request Timeout; Abort -- lbolt: 1348018328, dev: bc032000, io_id: 303a05f
armdsp -a - see attachment.
All disks have status GOOD, but several from them has warning message :
" Space is reserved on this disk for subsystem metadata and
may be a map disk."
At the bottom of armdsp report we can see such message:
"WARNING: The host indicated that hot spare space reservation was desired, but the space left unallocated was insufficient to provide the reservation."
I read information about this error and
advice was - add more disks. :)
Any help would be very appreciated,
Igor.
We have RP5405*2(Serviceguard), VA7410, 15*74Gb.
One of 15 disks has yellow indication.
In syslog.log we have a lot of such errors:
vmunix: SCSI: Request Timeout; Abort -- lbolt: 1348018328, dev: bc032000, io_id: 303a05f
armdsp -a
All disks have status GOOD, but several from them has warning message :
" Space is reserved on this disk for subsystem metadata and
may be a map disk."
At the bottom of armdsp report we can see such message:
"WARNING: The host indicated that hot spare space reservation was desired, but the space left unallocated was insufficient to provide the reservation."
I read information about this error and
advice was - add more disks. :)
Any help would be very appreciated,
Igor.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2007 04:15 AM
тАО07-19-2007 04:15 AM
Re: VA7410 space reservation was desired, but the space left
Hi Igor,
You have an error with disk M/D15.
Disk at M/D15 is not included at the moment because it was previously used in another array. Did you replace this recently? If you did, you need to tell the array to include this disk and destroy whatever data is on it. This is probably the disk that is showing the amber light.
This will give 73gb back to RG1 and then the status of the array should change from warning to normal again, and the message should dissapear.
I would recommend that you leave some space in the unallocated pool next time you reconfigure the array. This leaves space for the array to perform it's house keeping tasks. I can see that you've got the array in RAID1+0 and that you just have single big luns in each RG, so it may not be possible for you to reduce the size of your luns. In that case, you just need to ensure you monitor the array and respond to any faults promptly.
Regards
Owen
You have an error with disk M/D15.
Disk at M/D15 is not included at the moment because it was previously used in another array. Did you replace this recently? If you did, you need to tell the array to include this disk and destroy whatever data is on it. This is probably the disk that is showing the amber light.
This will give 73gb back to RG1 and then the status of the array should change from warning to normal again, and the message should dissapear.
I would recommend that you leave some space in the unallocated pool next time you reconfigure the array. This leaves space for the array to perform it's house keeping tasks. I can see that you've got the array in RAID1+0 and that you just have single big luns in each RG, so it may not be possible for you to reduce the size of your luns. In that case, you just need to ensure you monitor the array and respond to any faults promptly.
Regards
Owen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2007 05:04 PM
тАО07-19-2007 05:04 PM
Re: VA7410 space reservation was desired, but the space left
The error in syslog "vmunix: SCSI: Request Timeout; Abort -- lbolt: 1348018328, dev: bc032000, io_id: 303a05f" was due to the VA7410 array slow in responding to I/O request and probably due to lesser space in the array. Putting back the disk to give back some space to the RG should improve the situation.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP