# Changelog v1.11.1

**URL:** <https://forum.storj.io/t/changelog-v1-11-1/8773>\
**Category:** STORJLINGS\
**Tags:** official-changelog\
**Created:** [August 26, 2020, 2:58pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773 "2020-08-26T14:58:06Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [September 3, 2020, 1:53pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/21 "2020-09-03T13:53:57Z")

</div>

That’s caused by the writes still happening. Reads only are no different between SMR and CMR.

---

<div class="post-metadata">

**Author:** ![bovcan](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bovcan/32/70_2.png) [@bovcan](https://forum.storj.io/u/bovcan)\
**Post date:** [September 3, 2020, 4:12pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/22 "2020-09-03T16:12:41Z")

</div>

I had to transfer all SN files from seagate drive(smr) to wd, because it was causing me problems at 4TB and it took more than 24h just to calculate 3.5TB of files than it took close to 2 days to copy all that stuff to other disk.

---

<div class="post-metadata">

**Author:** ![sorry2xs](https://storj.bcdn.literatehosting.com/letter_avatar/sorry2xs/32/6_449c533f586939b6e5f246632a46421f.png) [@sorry2xs](https://forum.storj.io/u/sorry2xs)\
**Post date:** [September 3, 2020, 4:36pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/23 "2020-09-03T16:36:33Z")

</div>

how are smr drives identified

---

<div class="post-metadata">

**Author:** ![twl](https://storj.bcdn.literatehosting.com/letter_avatar/twl/32/6_449c533f586939b6e5f246632a46421f.png) [@twl](https://forum.storj.io/u/twl)\
**Post date:** [September 3, 2020, 5:28pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/24 "2020-09-03T17:28:04Z")

</div>

> [@BrightSilence](#):
>
> That’s caused by the writes still happening.

The node was offline while copying. Do you mean data being written from the CMR cache to the SMR sections?

---

<div class="post-metadata">

**Author:** ![twl](https://storj.bcdn.literatehosting.com/letter_avatar/twl/32/6_449c533f586939b6e5f246632a46421f.png) [@twl](https://forum.storj.io/u/twl)\
**Post date:** [September 3, 2020, 5:28pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/25 "2020-09-03T17:28:43Z")

</div>

> [@sorry2xs](#):
>
> how are smr drives identified

Most of the time: just google the drive’s model number for a data sheet.

---

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [September 3, 2020, 6:28pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/26 "2020-09-03T18:28:51Z")

</div>

There’s a pretty comprehensive list here too:

> [@PSA: Beware of HDD manufacturers submarining SMR technology in HDD's without any public mention](https://forum.storj.io/t/psa-beware-of-hdd-manufacturers-submarining-smr-technology-in-hdds-without-any-public-mention/6003):
>
> Recently there have been several reports of SNOs running into massive CPU wait issues. It seems the common thread has been the use of HDD’s in which manufacturers have quietly started using SMR technology. [2003549104] Because of these overlapping tracks, when data is written to the disk, the drive has to rewrite several additional tracks. This obviously leads to much slower writes. These HDD’s usually deal with that using large caches and rewriting the shingles tracks during quiet times. How…

> [@twl](#):
>
> The node was offline while copying. Do you mean data being written from the CMR cache to the SMR sections?

If it was stopped right before you started the copy, then yes. This can take many hours since a lot of data has to be overwritten and rewritten in the SMR sections of the drive. Just because you stopped writing to it doesn’t mean it stops doing its own house keeping.

---

<div class="post-metadata">

**Author:** ![sorry2xs](https://storj.bcdn.literatehosting.com/letter_avatar/sorry2xs/32/6_449c533f586939b6e5f246632a46421f.png) [@sorry2xs](https://forum.storj.io/u/sorry2xs)\
**Post date:** [September 3, 2020, 7:32pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/27 "2020-09-03T19:32:28Z")

</div>

hope manufacturers are not submarining enterprise class hdds

---

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [September 5, 2020, 8:15am UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/28 "2020-09-05T08:15:23Z")

</div>

I just received this update and I have 2 observations to share.

First off some good news. The rounding issue people have seen who set 1.93TB as a node size seem to be fixed with this release. This used to round down to 1.9TB, but now it seems to be exact. So this will give some users a bit more accurate control of how much space to assign. Additionally the CLI dashboard now shows an extra decimal point for all numbers, so we can see a bit more precisely how much data is used. That’s really appreciated!

The second observation is that on nodes that have set a separate db location, the new orders folder with files for orders instead of a db seems to be stored in the ~~data~~ config location rather than the database location. While it’s technically no longer a database, it’s still a set of additional IO that SNOs who moved the db’s would most likely rather have happen on the IO optimized db location. I know I sure would prefer that. @littleskunk was there a specific reason for this I’m overlooking?

---

<div class="post-metadata">

**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_449c533f586939b6e5f246632a46421f.png) [@Vadim](https://forum.storj.io/u/Vadim)\
**Post date:** [September 5, 2020, 9:58am UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/29 "2020-09-05T09:58:20Z")

</div>

in my case it is store in node instalation folder

 ![orders location](https://storj-s3.bcdn.literatehosting.net/original/2X/c/c43047e65c8633b43a22535a125662e44e58cce6.jpeg)

---

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [September 5, 2020, 10:07am UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/30 "2020-09-05T10:07:22Z")

</div>

You’re right, it’s technically in the config location, not the storage location. On docker installs that’s on the same HDD though as the storage location is a sub folder of the config location.

---

<div class="post-metadata">

**Author:** ![kevink](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kevink/32/6077_2.png) [@kevink](https://forum.storj.io/u/kevink)\
**Post date:** [September 5, 2020, 10:47am UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/32 "2020-09-05T10:47:54Z")

</div>

Since it is a completely separate folder, you can just make another mountpoint in docker -v /somewhere:/app/config/orders [well use the mount option, not -v]  
or do I miss something?

---

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [September 5, 2020, 10:54am UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/33 "2020-09-05T10:54:35Z")

</div>

Oh sure I can find a workaround. But I’m not too worried about just my own node. I was just giving some feedback on what I would consider a better implementation.

But let me add some extra arguments to that while I’m at it. On windows, reinstallation and removal of the install directory didn’t used to impact the storage or databases. But removal of that directory would now also throw out orders, including unpaid ones. In my opinion either data or metadata shouldn’t live in that location. Obviously this wouldn’t be a vital issue, you’d be missing out on just a fraction of payout should that occur. But it’s just about keeping stuff in the right places.

---

<div class="post-metadata">

**Author:** ![sorry2xs](https://storj.bcdn.literatehosting.com/letter_avatar/sorry2xs/32/6_449c533f586939b6e5f246632a46421f.png) [@sorry2xs](https://forum.storj.io/u/sorry2xs)\
**Post date:** [September 5, 2020, 12:49pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/34 "2020-09-05T12:49:32Z")

</div>

why is it that if I allocate 13.5 TB in the docker run cmd. the config shows the following # total allocated disk space in bytes  
storage.allocated-disk-space: 1.0 TB

---

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [September 5, 2020, 2:42pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/35 "2020-09-05T14:42:48Z")

</div>

Because the docker run command takes precedence over the config file.

---

<div class="post-metadata">

**Author:** ![sorry2xs](https://storj.bcdn.literatehosting.com/letter_avatar/sorry2xs/32/6_449c533f586939b6e5f246632a46421f.png) [@sorry2xs](https://forum.storj.io/u/sorry2xs)\
**Post date:** [September 5, 2020, 3:32pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/36 "2020-09-05T15:32:26Z")

</div>

I know about docker run cmd precedence, I guess I should have asked why are those four items uncommented instead of # if I was not the user who uncommented the items.

---

<div class="post-metadata">

**Author:** ![Mark](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mark/32/1128_2.png) [@Mark](https://forum.storj.io/u/Mark)\
**Post date:** [September 6, 2020, 2:01am UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/37 "2020-09-06T02:01:02Z")

</div>

> [@BrightSilence](#):
>
> The rounding issue people have seen who set 1.93TB as a node size seem to be fixed with this release.

This is good news. Since it’s not in the change log, I’m wondering if this issue was intentionally fixed or if it’s just a convenient side effect of something else they modified, perhaps that extra decimal place they added.

---

<div class="post-metadata">

**Author:** ![Pac](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pac/32/6053_2.png) [@Pac](https://forum.storj.io/u/Pac)\
**Post date:** [September 6, 2020, 1:05pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/38 "2020-09-06T13:05:20Z")

</div>

> [@BrightSilence](#):
>
> The rounding issue people have seen who set 1.93TB as a node size seem to be fixed with this release. This used to round down to 1.9TB, but now it seems to be exact

I’m observing an improvement here too myself, but it’s still rounding to the closest ten in my case. It’s way more precise than before, but still rounding 😉

I think it’s a great enhancement though 🙂

---

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [September 6, 2020, 1:39pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/39 "2020-09-06T13:39:42Z")

</div>

> [@Mark](#):
>
> Since it’s not in the change log

There’s lots of smaller improvements with every release that aren’t always part of the change log. I would probably have included this one since several people have complained about the rounding issues on the forum, but overall it’s a very minor thing.

> [@Pac](#):
>
> it’s still rounding to the closest ten in my case

Yes it still seems to be rounding. But honestly if you care about being more precise than 10GB intervals, you’re probably either planning to significantly overfill your HDD or have way too little space to share to be profitable.

---

<div class="post-metadata">

**Author:** ![Pac](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pac/32/6053_2.png) [@Pac](https://forum.storj.io/u/Pac)\
**Post date:** [September 6, 2020, 3:04pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/40 "2020-09-06T15:04:49Z")

</div>

> [@BrightSilence](#):
>
> But honestly if you care about being more precise than 10GB intervals, you’re probably either planning to significantly overfill your HDD or have way too little space to share to be profitable.

And I agree with you. I was just nitpicking because you said “it seems to be exact” 😁

I think it’s now perfect as it is 👍

By the way, the only reasons I configured my node with 894GB are:

- my disk is a 984GB disk (Initially 1TB, but some corrupted sectors were isolated long ago, and no new corrupted sectors appeared so far…).
- because of the way I calculate the 10% overhead to leave on disks as suggested by StorjLabs: I did 984/1.1 which gives 894: that’s what I allocated to the Node.
- I did not know it was getting rounded up at the time.

That’s it 🙂  
I could probably safely go back to 900GB.

---

<div class="post-metadata">

**Author:** ![sorry2xs](https://storj.bcdn.literatehosting.com/letter_avatar/sorry2xs/32/6_449c533f586939b6e5f246632a46421f.png) [@sorry2xs](https://forum.storj.io/u/sorry2xs)\
**Post date:** [September 6, 2020, 3:11pm UTC](https://forum.storj.io/t/changelog-v1-11-1/8773/41 "2020-09-06T15:11:51Z")

</div>

I have noticed that since the current release bandwidth roll ups time to finished has increased from five minutes to 20 minutes and I have noticed a error; it self corrected, but as to the extended time I’m curious.

[Previous page](https://forum.storj.io/t/changelog-v1-11-1/8773.md?page=1)

[Next page](https://forum.storj.io/t/changelog-v1-11-1/8773.md?page=3)
