---
title: "Comment by StackShortlist on \"Object Storage vs NAS: Which Is Better for Large, Unstructured Datasets?\" | Hashnode"
description: "The Object Lock row in the checklist is the one that bites people later. Since it can only be set at bucket creation, deciding retention mode before the first u"
url: "https://hashnode.com/posts/object-storage-vs-nas-which-is-better-for-large-unstructured-datasets/6ad31ca2d421fdfaf7723f8e/comment/6ad333887b0d9a1e1b75658c"
---

[Discussion](https://hashnode.com/posts/object-storage-vs-nas-which-is-better-for-large-unstructured-datasets/6ad31ca2d421fdfaf7723f8e)

Comment [Object Storage vs NAS: Which Is Better for Large, Unstructured Datasets?](https://hashnode.com/posts/object-storage-vs-nas-which-is-better-for-large-unstructured-datasets/6ad31ca2d421fdfaf7723f8e)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 17](https://hashnode.com/posts/object-storage-vs-nas-which-is-better-for-large-unstructured-datasets/6ad31ca2d421fdfaf7723f8e/comment/6ad333887b0d9a1e1b75658c)

The Object Lock row in the checklist is the one that bites people later. Since it can only be set at bucket creation, deciding retention mode before the first upload saves a full copy to a new bucket. The point about counting objects and not just terabytes is a good one too. A small-file tail can hit metadata limits on a NAS long before the disks are full.
