> If you made the record size something large, let's say 1MB, then it would mean that changing 1 byte of a duplicated or snapshotted 1GB file would cause an add

> If you made the record size something large, let's say 1MB, then it would mean that changing 1 byte of a duplicated or snapshotted 1GB file would cause an additional 1MB of storage. Very, very very inefficient. However, still better than a non-CoW system, where duplicates and snapshots would occupy an additional 1GB irrespective of modifications. 1MB recordsizes make a lot of sense for drives that primarily hold large files for archive or preservation. That lines up with the intended use of SMR drives. The problem here is that these were stealth-SMR drives, saving WD money at the customer's pain. For the small % of use cases where you have large files that are written sequentially, and never edited internally, labeled-SMR with large records can be a good solution that saves money.