IP Library Granted Patent US 12,632,173
Granted Patent B2
US 12,632,173 · App. 18/774,531 · Granted May 19, 2026

Logical block address level data protection scheme

Inventors: Sridhar Sabesan (Bangalore, IN); Pavan Gururaj (Bangalore, IN); Dinesh Babu (Bangalore, IN)
Assignee: Sandisk Technologies, Inc.
G06F3/0604G06F3/0655G06F3/0679G06F11/1417
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,632,173
App. No.
18/774,531
Granted
May 19, 2026
Kind
B2
Abstract

A data storage device includes a data protection system that protects data on a logical block address (LBA) level. In one implementation, the data protection system populates and maintains a global parity mesh table. The global parity mesh table includes parity information associated with a group of two LBAs. If data associated with one of the LBAs in the group becomes corrupted, the parity information in the global parity mesh table is used, in conjunction with data stored in the non-corrupted LBA, to recover the data associated with the corrupted LBA. In another implementation, the data protection system stores multiple copies of parity information in different sections or portions of two or more associated LBAs. If data associated with one LBA becomes corrupted, the data is recoverable using one of the copies of parity information stored in at least one or more of the associated LBAs.

Claims (60)

1 . A method, comprising:

receiving first data from a host device;

associating a first logical block address (LBA) with the first data;

storing the first data at a first physical location in a data storage device associated with the first LBA;

receiving second data from the host device;

associating a second LBA with the second data;

storing the second data at a second physical location in the data storage device associated with the second LBA;

associating the first LBA with the second LBA to create a first LBA group, wherein at least one of the first LBA and the second LBA are part of a second LBA group that is separate from the first LBA group and wherein the second LBA group includes a third LBA that is different from the first LBA and the second LBA;

based, at least in part, on associating the first LBA with the second LBA, determining first data recovery information associated with the first LBA group, the first data recovery information being based, at least in part, on the first data and the second data;

determining second data recovery information associated with the second LBA group, wherein the second data recovery information is different from the first data recovery information and is based, at least in part, on third data associated with the third LBA and data associated with the at least one of the first LBA and the second LBA;

storing the first data recovery information with the first LBA group; and

storing the second data recovery information with the second LBA group.

2 . The method of claim 1 , wherein the first data recovery information and the first LBA group is stored in the data storage device.

3 . The method of claim 1 , wherein the first data recovery information and the first LBA group is stored by the host device.

4 . The method of claim 1 , wherein at least one of the first data recovery information and the second data recovery information is parity information.

5 . The method of claim 1 , wherein at least one of the first data recovery information and the second data recovery information is a combination of hashing information and parity information.

6 . The method of claim 1 , further comprising:

detecting a failure associated with the first LBA;

based, at least in part, on detecting the failure, accessing the first data recovery information associated with the first LBA group; and

addressing the failure using the first data recovery information and the second data associated with the second LBA.

7 . The method of claim 1 , further comprising:

receiving updated data associated with the first LBA; and

based, at least in part, on receiving the updated data, updating the first data recovery information associated with the first LBA group.

8 . The method of claim 1 , further comprising:

determining an operating state of the data storage device; and

storing the first data recovery information and the first LBA group at a particular time associated with the determined operating state of the data storage device.

9 . The method of claim 1 , wherein the first data recovery information is stored at a time period associated with a schedule.

10 . A method, comprising:

receiving data from a host device;

associating a first logical block address (LBA) with the data;

storing the data at a first physical location in a data storage device associated with the first LBA, the first physical location being divided into a data section, a first data recovery section and a second data recovery section;

determining data recovery information associated with the data;

identifying a second LBA associated with the first LBA, the second LBA being associated with a second physical location in the data storage device and being divided into a data section, a first data recovery section and a second data recovery section; and

storing a first copy of the data recovery information associated with the data in at least one of the first data recovery section and the second data recovery section associated with the second LBA.

11 . The method of claim 10 , further comprising:

identifying a third LBA associated with the first LBA, the third LBA being associated with a third physical location in the data storage device and being divided into a data section, a first data recovery section and a second data recovery section; and

storing a second copy of the data recovery information associated with the data in at least one of the first data recovery section and the second data recovery section associated with the third LBA.

12 . The method of claim 11 , further comprising:

detecting a failure associated with the first LBA;

based, at least in part, on detecting the failure, accessing at least one of the first copy of data recovery information associated with the second LBA and the second copy of data recovery information associated with the third LBA; and

addressing the failure using the at least one of the first copy of data recovery information associated with the second LBA and the second copy of data recovery information associated with the third LBA.

13 . The method of claim 10 , wherein the first LBA is logically adjacent to the second LBA.

14 . The method of claim 10 , wherein the data recovery information is parity information.

15 . The method of claim 10 , wherein the data recovery information is a combination of hashing information and parity information.

16 . The method of claim 10 , wherein the data recovery information associated with the data is determined based, at least in part, on the data being written to the data section of the first physical location in the data storage device.

17 . A data storage device, comprising:

means for storing data at a first physical location associated with a first logical block address (LBA), the first physical location including a data section, a first data recovery section and a second data recovery section;

means for determining data recovery information associated with the data;

means for identifying a second LBA associated with the first LBA, the second LBA being associated with a second physical location and including a data section, a first data recovery section and a second data recovery section; and

means for storing a first copy of the data recovery information associated with the data in at least one of the first data recovery section and the second data recovery section associated with the second LBA.

18 . The data storage device of claim 17 , further comprising:

means for identifying a third LBA associated with the first LBA, the third LBA being associated with a third physical location and including a data section, a first data recovery section and a second data recovery section; and

means for storing a second copy of the data recovery information associated with the data in at least one of the first data recovery section and the second data recovery section associated with the third LBA.

19 . The data storage device of claim 18 , further comprising:

means for detecting a failure associated with the first LBA;

means accessing at least one of the first copy of data recovery information associated with the second LBA and the second copy of data recovery information associated with the third LBA; and

means for addressing the failure using the at least one of the first copy of data recovery information associated with the second LBA and the second copy of data recovery information associated with the third LBA.

20 . The data storage device of claim 17 , wherein the data recovery information is at least one of:

parity information associated with the data; and

a combination of hashing information and parity information associated with the data.

Assignments (4)
SECURITY AGREEMENT Recorded Apr 25, 2025
From: SANDISK TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 071050/0001 →
PARTIAL RELEASE OF SECURITY INTERESTS Recorded Apr 25, 2025
From: JPMORGAN CHASE BANK, N.A., AS AGENT
To: SANDISK TECHNOLOGIES, INC.
Reel/Frame 071382/0001 →
PATENT COLLATERAL AGREEMENT Recorded Aug 23, 2024
From: SANDISK TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A., AS THE AGENT
Reel/Frame 068762/0494 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 18, 2024
From: SABESAN, SRIDHAR; GURURAJ, PAVAN; BABU, DINESH
To: SANDISK TECHNOLOGIES, INC.
Reel/Frame 068016/0911 →
Continuity (1)
Related Publication 20260023481A1 · Jan 22, 2026
References Cited (20)
US 6425052B1 · Hashemi · 2002 [cited by examiner]
US 7340581B2 · Gorobets et al. · 2008 [cited by applicant]
US 10565051B2 · Li · 2020 [cited by applicant]
US 10884857B2 · Kumar et al. · 2021 [cited by applicant]
US 10942654B2 · Meiri et al. · 2021 [cited by applicant]
US 11023388B2 · Novogran et al. · 2021 [cited by applicant]
US 11132256B2 · Roberts · 2021 [cited by applicant]
US 11221958B2 · Choi et al. · 2022 [cited by applicant]
US 11237977B2 · Choi et al. · 2022 [cited by applicant]
US 11789873B2 · Choi et al. · 2023 [cited by applicant]
US 20190065389A1 · Choi · 2019 [cited by examiner]
US 20190087605A1 · Jensen · 2019 [cited by examiner]
US 20230052161A1 · Seok · 2023 [cited by examiner]
US 20230350752A1 · Alkalay · 2023 [cited by examiner]
US 20240069751A1 · Eun · 2024 [cited by examiner]
US 20240232009A1 · Rai · 2024 [cited by examiner]
US 20240248793A1 · Xu · 2024 [cited by examiner]
US 20240256123A1 · Moore · 2024 [cited by examiner]
US 20240345734A1 · Hiwada · 2024 [cited by examiner]
EP 1168173A2 · 2002 [cited by examiner]