From d3ad63a4ec406494d0efc220a8e4deb3ea2a1fda Mon Sep 17 00:00:00 2001 From: Mike Lissner Date: Mon, 23 Jul 2018 11:48:59 -0700 Subject: [PATCH] b2 bucket names need to be unique Adds a small warning indicating that b2 bucket names need to be unique. It's an easy mistake to make, and it's surprising to get the following error if you're not accustomed to the way B2 works: Fatal: create repository at b2:postgres failed: NewBucket: b2_create_bucket: 400: Bucket name is already in use --- doc/030_preparing_a_new_repo.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/030_preparing_a_new_repo.rst b/doc/030_preparing_a_new_repo.rst index afa83f6c9..5c3eea321 100644 --- a/doc/030_preparing_a_new_repo.rst +++ b/doc/030_preparing_a_new_repo.rst @@ -313,6 +313,8 @@ bucket does not exist yet, it will be created: Please note that knowledge of your password is required to access the repository. Losing your password means that your data is irrecoverably lost. +Note that the bucket name must be unique across all of B2. + The number of concurrent connections to the B2 service can be set with the ``-o b2.connections=10`` switch. By default, at most five parallel connections are established.