3 ms·

This seems at the same time reasonable (no files larger than 1TB sounds fair, I don’t think anyone reads ‘no file size restrictions’ and imagines a one terabyte

by Aeolun 2y ago

This seems at the same time reasonable (no files larger than 1TB sounds fair, I don’t think anyone reads ‘no file size restrictions’ and imagines a one terabyte file), and not, because support should realize that that might have something to do with the issue and get someone technical involved.

swiftcoder 2y ago
Undocumented limits are a classic way to blow up traffic to your support centre. Please folks, if your service has limits, document them!
- OtherShrezzing 2y ago
  Documenting also helps your own engineers understand that there are limitations. The back-end team might understand that there's a 1TB limit. If the front-end team doesn't, they could cost you a tonne of bandwidth uploading 99% of a 1.001TB file to the server before it gets rejected.
- michaelt 2y ago
  Documenting wouldn't hurt, I'll agree. But I doubt they're getting much support burden from this; the product targets home users, providing fixed-price single computer backups. This isn't their B3 blob storage offering. The most bloated triple-A games out there are only ~100GB. The entirety of OpenStreetMap's data, in XML format, only reaches 147 GB [1]. The latest and greatest 670-billion-parameter LLM is only 600 GB... and they ship it as 163 x 4.3GB files [2]. Among PC gamers [3] about 45% of people have less than 1TB of hard drive space, total. IMHO it's very unlikely they have a big support burden from this undocumented limitation. It's clearly a bug though - trying to upload the same file in every single backup, failing every time? There's no way that's the intended behaviour. [1] https://planet.openstreetmap.org/ https://planet.openstreetmap.org/ [2] https://huggingface.co/deepseek-ai/DeepSeek-R1/tree/main https://huggingface.co/deepseek-ai/DeepSeek-R1/tree/main [3] https://store.steampowered.com/hwsurvey https://store.steampowered.com/hwsurvey
  - birdman3131 2y ago
    You have never played Ark I take it. I am sitting at ~700gb between Ark: Survival Evolved and Survival Ascended.
madeofpalk 2y ago
If it actually wasn't supported, surely the client would know this and wouldn't attempt to continiously upload it. Seems like there is a bug somewhere - whether artificially imposing a file size limit, or in not imposing the limit correctly.
- jagged-chisel 2y ago
  > … surely the client would know this ”Should” most certainly. However, often client teams don’t work so closely with backend teams. Or the client team is working from incorrect documentation. Or the client team rightfully assumes that when it reports a file size before uploading, the backend will produce an acceptable error to notify the client.
  - baobabKoodaa 2y ago
    Oh my, this almost sounds like it just might have unintended bad effects when you lie in your marketing about what limits your service has.
davidt84 2y ago
I read "no file size restrictions" and assume I can create a file as large as the storage space I can afford. What else would I assume? If there's a 1TB limit I would expect that to be described as "create files up to 1TB in size".
- eterevsky 2y ago
  I would assume some limit no higher than 2^64, since all common file systems have file size limits: https://en.wikipedia.org/wiki/Comparison_of_file_systems https://en.wikipedia.org/wiki/Comparison_of_file_systems
  - 8organicbits 2y ago
    When common file systems like NTFS have limits like "16 TiB (17.59 TB) to 8 PiB (9.007 PB)", a 1TB limit seems below what is advertised.
dpacmittal 2y ago
Why couldn't they just say 1tb limit?
- baobabKoodaa 2y ago
  This is what bothers me as well. I don't think you would find a single customer who would go "what, only 1TB files?" I guess different kinds of people are drawn to different careers, and people with loose morals, hubris, and a propensity to lie are drawn to marketing. Don't even need an incentive to lie, it's just who they are.
  - pbalau 2y ago
    > I don't think you would find a single customer who would go "what, only 1TB files?" I think you will find that there are people that see "limit <humongous>" and pick the "no limit" or no limit stated option. > people with loose morals, hubris, and a propensity to lie are drawn to marketing You are jumping the gun here.
mort96 2y ago
It's a back-up service, not a cloud storage service. If I have a 1TB file on my machine, and I want to back up my machine, I want that 1TB file to be backed up.
- londons_explore 2y ago
  And a 1tb file is pretty common if you take a backup of a 1tb disk drive into a disk image.
  - mort96 2y ago
    Certainly, I've regularly had single image files and tar.gz files of that magnitude on my machines which are precisely back-ups of old laptops when I get a new one etc.
  - joseda-hg 2y ago
    Not arguing your main point, but why wouldn't you compress a backup?
    - londons_explore 2y ago
      My disk's tend to be full of films that barely compress.
kaivi 2y ago
These limits are not reasonable at all. You are going to curse the Backblaze or AWS S3 before you learn to never pipe the output of pg_dump into an object store like that.
atYevP 2y ago
Yev here -> we're actively looking into it, we can upload files >1TB so it's a bit tough to chase down.

by Aeolun 2y ago

swiftcoder 2y ago

Undocumented limits are a classic way to blow up traffic to your support centre. Please folks, if your service has limits, document them!

OtherShrezzing 2y ago
Documenting also helps your own engineers understand that there are limitations. The back-end team might understand that there's a 1TB limit. If the front-end team doesn't, they could cost you a tonne of bandwidth uploading 99% of a 1.001TB file to the server before it gets rejected.
michaelt 2y ago
Documenting wouldn't hurt, I'll agree. But I doubt they're getting much support burden from this; the product targets home users, providing fixed-price single computer backups. This isn't their B3 blob storage offering. The most bloated triple-A games out there are only ~100GB. The entirety of OpenStreetMap's data, in XML format, only reaches 147 GB [1]. The latest and greatest 670-billion-parameter LLM is only 600 GB... and they ship it as 163 x 4.3GB files [2]. Among PC gamers [3] about 45% of people have less than 1TB of hard drive space, total. IMHO it's very unlikely they have a big support burden from this undocumented limitation. It's clearly a bug though - trying to upload the same file in every single backup, failing every time? There's no way that's the intended behaviour. [1] https://planet.openstreetmap.org/ https://planet.openstreetmap.org/ [2] https://huggingface.co/deepseek-ai/DeepSeek-R1/tree/main https://huggingface.co/deepseek-ai/DeepSeek-R1/tree/main [3] https://store.steampowered.com/hwsurvey https://store.steampowered.com/hwsurvey
- birdman3131 2y ago
  You have never played Ark I take it. I am sitting at ~700gb between Ark: Survival Evolved and Survival Ascended.

madeofpalk 2y ago

If it actually wasn't supported, surely the client would know this and wouldn't attempt to continiously upload it. Seems like there is a bug somewhere - whether artificially imposing a file size limit, or in not imposing the limit correctly.

jagged-chisel 2y ago
> … surely the client would know this ”Should” most certainly. However, often client teams don’t work so closely with backend teams. Or the client team is working from incorrect documentation. Or the client team rightfully assumes that when it reports a file size before uploading, the backend will produce an acceptable error to notify the client.
- baobabKoodaa 2y ago
  Oh my, this almost sounds like it just might have unintended bad effects when you lie in your marketing about what limits your service has.

davidt84 2y ago

I read "no file size restrictions" and assume I can create a file as large as the storage space I can afford. What else would I assume? If there's a 1TB limit I would expect that to be described as "create files up to 1TB in size".

eterevsky 2y ago
I would assume some limit no higher than 2^64, since all common file systems have file size limits: https://en.wikipedia.org/wiki/Comparison_of_file_systems https://en.wikipedia.org/wiki/Comparison_of_file_systems
- 8organicbits 2y ago
  When common file systems like NTFS have limits like "16 TiB (17.59 TB) to 8 PiB (9.007 PB)", a 1TB limit seems below what is advertised.

dpacmittal 2y ago

Why couldn't they just say 1tb limit?

baobabKoodaa 2y ago
This is what bothers me as well. I don't think you would find a single customer who would go "what, only 1TB files?" I guess different kinds of people are drawn to different careers, and people with loose morals, hubris, and a propensity to lie are drawn to marketing. Don't even need an incentive to lie, it's just who they are.
- pbalau 2y ago
  > I don't think you would find a single customer who would go "what, only 1TB files?" I think you will find that there are people that see "limit <humongous>" and pick the "no limit" or no limit stated option. > people with loose morals, hubris, and a propensity to lie are drawn to marketing You are jumping the gun here.

mort96 2y ago

It's a back-up service, not a cloud storage service. If I have a 1TB file on my machine, and I want to back up my machine, I want that 1TB file to be backed up.

londons_explore 2y ago
And a 1tb file is pretty common if you take a backup of a 1tb disk drive into a disk image.
- mort96 2y ago
  Certainly, I've regularly had single image files and tar.gz files of that magnitude on my machines which are precisely back-ups of old laptops when I get a new one etc.
- joseda-hg 2y ago
  Not arguing your main point, but why wouldn't you compress a backup?
  - londons_explore 2y ago
    My disk's tend to be full of films that barely compress.

kaivi 2y ago

These limits are not reasonable at all. You are going to curse the Backblaze or AWS S3 before you learn to never pipe the output of pg_dump into an object store like that.

atYevP 2y ago

Yev here -> we're actively looking into it, we can upload files >1TB so it's a bit tough to chase down.