Storage device and operation method of electronic system
A storage device includes a memory device including user memory blocks providing a user data region; and a controller configured to: map logical addresses used in a host to a portion of the user data region, and use a remaining portion of the user data region as an over-provisioning region, wherein the controller is further configured to control the memory device to: erase the user memory blocks based on a sanitize command from the host, provide, to the host, block address information of the user memory blocks based on a block address request from the host, access the user memory blocks based on block state check requests from the host, and provide, to the host, state information indicating whether the user memory blocks are erased according to access results.
1. A storage device comprising:
a memory device comprising user memory blocks providing a user data region; and
a controller configured to:
map logical addresses used in a host to a portion of the user data region, and
use a remaining portion of the user data region as an over-provisioning region,
wherein the controller is further configured to control the memory device to:
erase the user memory blocks based on a sanitize command from the host,
provide, to the host, block address information of the user memory blocks based on a block address request from the host,
access the user memory blocks based on block state check requests from the host, and
provide, to the host, state information indicating whether the user memory blocks are erased according to access results,
wherein the memory device further comprises bad memory blocks,
wherein the user memory blocks have non-contiguous physical block addresses by the bad memory blocks, and
wherein the controller is further configured to map the non-contiguous physical block addresses of the user memory blocks to contiguous virtual block addresses.
2. The storage device of claim 1 , wherein the block address information comprises number information of the user memory blocks, and
the controller is further configured to sequentially provide, to the host, state information of each of the user memory blocks, based on the block state check requests provided from the host and the number information.
3. The storage device of claim 1 , wherein the controller is further configured to:
map physical block addresses of the user memory blocks to virtual block addresses, and
provide, to the host, the virtual block addresses as the block address information.
4. The storage device of claim 3 , wherein the controller is further configured to map the physical block addresses to the virtual block addresses in a random order.
5. The storage device of claim 1 , wherein the controller is further configured to sequentially provide, to the host, state information of each of the user memory blocks, based on block state check requests provided in an order of virtual block addresses provided by the host.
6. The storage device of claim 5 , wherein the controller is not configured to map the over-provisioning region to a logical address, and to perform a garbage collection operation or a wear-leveling operation of a region mapped to the logical address using the over-provisioning region.
7. A storage device comprising:
a memory device comprising user memory blocks providing a user data region; and
a controller,
wherein the controller is configured to control the memory device to:
erase the user memory blocks based on a sanitize command from a host,
map physical block addresses of the user memory blocks to virtual block addresses,
provide, to the host, block address information based on: i) the virtual block addresses, and ii) a block address request from the host,
access the user memory blocks based on block state check requests from the host, and
provide, to the host, state information indicating whether the user memory blocks are erased according to access results,
wherein the memory device further comprises bad memory blocks,
wherein the user memory blocks have non-contiguous physical block addresses by the bad memory blocks, and
wherein the controller is further configured to map the non-contiguous physical block addresses of the user memory blocks to contiguous virtual block addresses.
8. The storage device of claim 7 , wherein the user data region comprises a region mapped to logical addresses of the host, and an over-provisioning region not mapped to the logical addresses of the host.
9. The storage device of claim 7 , wherein the block address information comprises number information of the user memory blocks, and
the controller is further configured to sequentially provide, to the host, state information of each of the user memory blocks, based on the block state check requests provided from the host and the number information.
10. The storage device of claim 9 , wherein the controller is further configured to map the physical block addresses to the virtual block addresses in a random order.
11. The storage device of claim 7 , wherein the controller is further configured to:
convert a virtual block address, received together with each block state check request from the host, into a physical block address,
provide, to the memory device, a state check command together with the physical block address, and
provide, to the host, state information indicating whether the user memory blocks, corresponding to the physical block address from the memory device, are erased.
12. A method of operating an electronic system including a host and a storage device, the method comprising:
providing, by the host, a sanitize command to the storage device;
providing, by the storage device, a completion response after the storage device performs an erase operation of user memory blocks included in the storage device based on the sanitize command;
requesting, by the host, block address information of the user memory blocks to the storage device;
providing, by the storage device, the block address information to the host based on the request;
providing, by the host, a state check request of a first user memory block, among the user memory blocks, with reference to the block address information;
providing, by the storage device, state information indicating whether the first user memory block is erased, based on the state check request from the host; and
repeating, by the host, an operation of providing the state check request, until the host obtains state information of all of the user memory blocks,
wherein the memory device further comprises bad memory blocks,
wherein the user memory blocks have non-contiguous physical block addresses by the bad memory blocks, and
wherein the method further comprises mapping the non-contiguous physical block addresses of the user memory blocks to contiguous virtual block addresses.
13. The method of claim 12 , further comprising:
mapping, by the storage device, logical addresses used in the host to a portion of user data regions provided by the user memory blocks; and
performing a garbage collection operation or a wear-leveling operation using a remaining portion of a user data region by the storage device.
14. The method of claim 12 , wherein the providing the block address information to the host comprises providing number information of the user memory blocks.
15. The method of claim 12 , further comprising:
randomly mapping, by the storage device, physical block addresses of the user memory blocks to virtual block addresses; and
generating, by the storage device, the block address information based on the virtual block addresses.
16. The method of claim 15 , further comprising providing, by the storage device, state information of each of the user memory blocks in an order of the virtual block addresses in response to state check requests repeatedly provided from the host.