A caching method for a distributed storage system, comprising: Receiving (S302, S402), by the lock server node device from a lock client node, a lock notification on a data stripe, and determining the lock notification; when the lock notification is a read lock notification received for the first time or a write lock notification, recording, by the lock server node device, the lock client node as an owner of the data stripe, and returning to the lock client node a response message indicating that the owner of the data stripe is the lock client node, so that the lock client node caches the data stripe, wherein the read lock notification includes a read lock request, the write lock notification includes a write lock request, the returning to the lock client node a response message indicating that the owner of the data stripe is the lock client node further includes: returning to the lock client node a lock success response message; and when the lock notification is a read lock notification which is not received for the first time, returning, by the lock server node device to the lock client node, a response message that comprises owner information of the data stripe, so that the lock client node reads the data stripe from a cache of an owner, according to said owner information, of the data stripe, wherein the returning to the lock client node a response message which includes owner information of the data stripe further includes: returning to the lock client node a lock success response message; wherein the lock success response message indicates that the lock client node has obtained a read lock or a write lock on the data stripe, the lock client node that holds a read lock on a data stripe can read the data stripe, while a lock client node that holds a write lock on a data stripe can write or modify the data stripe. Receiving (S302, S402), by the lock server node device from a lock client node, a lock notification on a data stripe, and determining the lock notification; when the lock notification is a read lock notification received for the first time or a write lock notification, recording, by the lock server node device, the lock client node as an owner of the data stripe, and returning to the lock client node a response message indicating that the owner of the data stripe is the lock client node, so that the lock client node caches the data stripe, wherein the read lock notification includes a read lock request, the write lock notification includes a write lock request, the returning to the lock client node a response message indicating that the owner of the data stripe is the lock client node further includes: returning to the lock client node a lock success response message; and when the lock notification is a read lock notification which is not received for the first time, returning, by the lock server node device to the lock client node, a response message that comprises owner information of the data stripe, so that the lock client node reads the data stripe from a cache of an owner, according to said owner information, of the data stripe, wherein the returning to the lock client node a response message which includes owner information of the data stripe further includes: returning to the lock client node a lock success response message; wherein the lock success response message indicates that the lock client node has obtained a read lock or a write lock on the data stripe, the lock client node that holds a read lock on a data stripe can read the data stripe, while a lock client node that holds a write lock on a data stripe can write or modify the data stripe.