- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- How does LHN Thin provisioning handle disk defragm...
StoreVirtual Storage
1753475
Members
4820
Online
108794
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
Go to solution
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
тАО07-08-2009 11:39 PM
тАО07-08-2009 11:39 PM
Hi, NetApps claim that LHN thin provisioning will cause disk to be fragmented, and the defragmentation for LHN is not efficient. I could not find related documents that explain on defragmentation of disks for LHN. Please advise, thanks.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2009 08:29 AM
тАО07-09-2009 08:29 AM
Re: How does LHN Thin provisioning handle disk defragmentation
Generally speaking disk fragmentation should not be a significant issue in a LeftHand topology.
Since your entire cluster is one large array, all disks are distributing I/O load for multiple iSCSI sessions, so the drives are already moving around "thrashing" to serve up multiple data streams, so weather the data is fragmented or sequential, the drive arms are still moving all over the place anyway. You are typically overcoming this by having more physical spindles to distribute the IO over more and more drives. So as your load increases, you add more modules.
I suspect you could show performance degredation from fragmentation if you compared single (read:dedicated) iSCSI session performing a large sequential data operation. AFAIK the Lefthand design is optimized more for random IO (than sequential/streaming IO) and you may see lower I/O due to the "fragmentation" for sequential/streaming type applications...
I'd like to hear the answer to this from the HP/LeftHand engineers, as this is just my outside observations...
Since your entire cluster is one large array, all disks are distributing I/O load for multiple iSCSI sessions, so the drives are already moving around "thrashing" to serve up multiple data streams, so weather the data is fragmented or sequential, the drive arms are still moving all over the place anyway. You are typically overcoming this by having more physical spindles to distribute the IO over more and more drives. So as your load increases, you add more modules.
I suspect you could show performance degredation from fragmentation if you compared single (read:dedicated) iSCSI session performing a large sequential data operation. AFAIK the Lefthand design is optimized more for random IO (than sequential/streaming IO) and you may see lower I/O due to the "fragmentation" for sequential/streaming type applications...
I'd like to hear the answer to this from the HP/LeftHand engineers, as this is just my outside observations...
http://www.tdonline.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2009 09:20 AM
тАО07-09-2009 09:20 AM
Solution
They'll say anything :)
The HP LeftHand P4000 Thin Provisioning does not have any negative effect on disk fragmentation. Either from a host / OS / File system perspective nor internal to the SAN itself.
Entirely separate from thin provisioning the LeftHand SANs use a method internally to lay out volumes sequentially in what we call "strides" for optimal performance. Additionally there is a background task that will optimize these "strides" *if* they could be laid out better as needed. This background process is only really needed if a SAN is very full, so has less options to lay out strides optimally in the first place.
All of this is done automatically by the system and needs no administrator input or intervention.
The HP LeftHand P4000 Thin Provisioning does not have any negative effect on disk fragmentation. Either from a host / OS / File system perspective nor internal to the SAN itself.
Entirely separate from thin provisioning the LeftHand SANs use a method internally to lay out volumes sequentially in what we call "strides" for optimal performance. Additionally there is a background task that will optimize these "strides" *if* they could be laid out better as needed. This background process is only really needed if a SAN is very full, so has less options to lay out strides optimally in the first place.
All of this is done automatically by the system and needs no administrator input or intervention.
Adam C, LeftHand Product Manger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2009 03:00 AM
тАО07-11-2009 03:00 AM
Re: How does LHN Thin provisioning handle disk defragmentation
The other thing to remember is that if you do create a thin provisioned volume DO NOT defragment the volume as this will have the effect of turning it into a fully provisioned volume.
Mike.
Mike.
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