Skip to content

Commit 0232a10

Browse files
SamyOubouazizSamyOubouaziz
authored
docs(blk): update block doc MTA-6162 (#5644)
* docs(blk): update block doc MTA-6182 * docs(blk): update * docs(blk): update * docs(blk): update * docs(blk): update * docs(blk): update * docs(blk): update
1 parent 572e5df commit 0232a10

22 files changed

+289
-321
lines changed

‎macros/block-storage/block-storage-volume-types.mdx‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,6 @@ macro: block-storage-volume-types
44

55
| Volume type | IOPS | Underlying hardware | Latency | Max volume size | Recommended use cases | Availability & resilience |
66
|-----------------------------------|----------|--------------------------------|---------------------|----------------------|-------------------------|----------------------------|
7-
| `b_ssd` (Block Storage 5K legacy) | 5,000 | Legacy SSDs | High | Up to 10 TB | General-purpose workloads that do not demand high IOPS or low latency | Data is replicated three times across multiple disks for high availability and integrity |
8-
| `sbs_5k` (Block Low Latency 5K) | 5,000 | Modern NVMe disks | Low | 5 GB to 10 TB | Development environments, web servers, and applications needing consistent performance | 99.99% SLA, triple-replicated data to safeguard against hardware failures |
9-
| `sbs_15k` (Block Low Latency 15K) | 15,000 | Modern NVMe disks | Very low | 5 GB to 10 TB | High-performance databases, transactional applications, and I/O-intensive workloads | 99.99% SLA, triple-replicated data to safeguard against hardware failures |
7+
| `b_ssd` (Block Storage legacy) | 5,000 | Legacy SSDs | High | Up to 10 TB | General-purpose workloads that do not demand high IOPS or | Data is replicated three times across multiple disks for high availability and integrity |
8+
| `sbs_5k` (Block 5K) | 5,000 | Modern NVMe disks | Low | 5 GB to 10 TB | Development environments, web servers, and applications needing consistent performance | 99.99% SLA, triple-replicated data to safeguard against hardware failures |
9+
| `sbs_15k` (Block 15K) | 15,000 | Modern NVMe disks | Very low | 5 GB to 10 TB | High-performance databases, transactional applications, and I/O-intensive workloads | 99.99% SLA, triple-replicated data to safeguard against hardware failures |

‎pages/block-storage/api-cli/increasing-partition-size.mdx‎

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
title: Increasing the size of a partition
3+
description: Learn how to increase the size of a partition within a Block Storage volume
4+
tags: volume block-storage block resize growpart increase size
5+
dates:
6+
validation: 2025-10-13
7+
posted: 2019-11-29
8+
---
9+
import Requirements from '@macros/iam/requirements.mdx'
10+
11+
The `growpart` utility allows you to resize partitions. If you have increased the size of the partition's underlying volume, for example, you can increase the size of the partition to make use of the additional space.
12+
13+
<Requirements />
14+
15+
- A Scaleway account logged into the [console](https://console.scaleway.com)
16+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
17+
- An [Instance](/instances/concepts/#instance)
18+
- [Attached](/block-storage/how-to/attach-a-volume/) an additional Block Storage volume to your Instance
19+
20+
<Message type="important">
21+
- Make sure to make a backup of your data using the [snapshot](/block-storage/how-to/create-a-snapshot/) feature beforehand to avoid any potential data loss
22+
- You must have partitioned your volume to follow the procedure below
23+
- If the partition you want to resize is mounted, you must [unmount it](/block-storage/api-cli/unmounting-a-volume/) beforehand
24+
</Message>
25+
26+
1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/).
27+
28+
2. Use the `lsblk` command to identify your volume partition. Ensure that the partition is **not mounted before you resize it**. In the following example, we are resizing `sdb1`:
29+
30+
```
31+
root@scw-festive-agnesi:~# lsblk
32+
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
33+
sda 8:0 0 23.3G 0 disk
34+
├─sda1 8:1 0 23.2G 0 part /
35+
├─sda14 8:14 0 4M 0 part
36+
└─sda15 8:15 0 106M 0 part /boot/efi
37+
sdb 8:16 0 38.6G 0 disk
38+
└─sdb1 8:17 0 18.6G 0 part
39+
```
40+
41+
3. Use `growpart` to increase the partition size of your Block Storage volume (here `sdb1`):
42+
43+
```
44+
# Replace /dev/sdX 1 with the name of your partition
45+
growpart /dev/sdX 1
46+
```
47+
48+
An output similar to the following displays:
49+
50+
```
51+
CHANGED: partition=1 start=0 old: size=39061504 end=39061504 new: size=58490880 end=58490880
52+
```
53+
54+
4. Use `lsblk` to check that the partition was correctly resized. In the following output, you can see that our partition `sbd1` went from `18.6G` (step 2) to `27.9G`.
55+
```
56+
root@scw-festive-agnesi:~# lsblk
57+
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
58+
sda 8:0 0 18.6G 0 disk
59+
├─sda1 8:1 0 18.5G 0 part /
60+
├─sda14 8:14 0 4M 0 part
61+
└─sda15 8:15 0 106M 0 part /boot/efi
62+
sdb 8:16 0 27.9G 0 disk
63+
└─sdb1 8:17 0 27.9G 0 part

‎pages/block-storage/api-cli/increasing-volume-size.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Increasing the size of Block Storage volumes via the Scaleway API
33
description: This page explains how to increase the size of a Block Storage volume using the Scaleway API.
44
tags: increase expand increment raise storage volume block
55
dates:
6-
validation: 2025-09-17
6+
validation: 2025-10-13
77
posted: 2025-03-04
88
---
99
import Requirements from '@macros/iam/requirements.mdx'

‎pages/block-storage/api-cli/managing-a-volume.mdx‎

Lines changed: 0 additions & 236 deletions
This file was deleted.

‎pages/block-storage/api-cli/transfer-local-data-to-volume.mdx‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: Transferring local data to a Block Storage volume
3+
description: This page explains how to transfer local data to a Block Storage volume mounted to a Scaleway Instance.
4+
tags: copy transfer upload rsync ftp send data file local fylesystem
5+
dates:
6+
validation: 2025-10-10
7+
posted: 2025-10-10
8+
---
9+
import Requirements from '@macros/iam/requirements.mdx'
10+
11+
You can transfer files from your local machine to your Instance's remote Block volume with [rsync](https://en.wikipedia.org/wiki/Rsync), a tool for efficiently transferring and copying files. The rsync utility is pre-installed on most Linux distributions and macOS.
12+
13+
<Requirements />
14+
15+
- A Scaleway account logged into the [console](https://console.scaleway.com)
16+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
17+
- An [Instance](/instances/concepts/#instance)
18+
- [Attached](/block-storage/how-to/attach-a-volume/) a Block Storage volume to your Instance
19+
- Installed [Rsync](https://rsync.samba.org/)
20+
21+
1. Check that rsync is installed on your local machine with the following command:
22+
```
23+
rsync --version
24+
```
25+
26+
An output similar to the following displays:
27+
28+
```sh no-copy
29+
rsync version 3.1.3 protocol version 31
30+
```
31+
32+
2. Run the following command to transfer the file to your Instance's mounted block volume. Ensure that you use your own Instance's IP address:
33+
34+
```
35+
rsync -a path/to/file.txt root@<your_instance_ip>:/mnt/block-volume
36+
```
37+
38+
3. The file is now transferred. Connect to your Instance again, then run the command below to check that your file is present in your Block Storage volume:
39+
40+
```bash
41+
ls /mnt/block-volume
42+
```
43+
44+
Refer to the [official Rsync documentation](https://download.samba.org/pub/rsync/rsync.1#OPTION_SUMMARY) for more information on the different options available.

‎pages/block-storage/api-cli/unmounting-a-volume.mdx‎

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,14 +3,11 @@ title: Unmounting a Block Storage volume
33
description: Learn how to safely unmount a Block Storage volume from your Instance, and ensure data integrity.
44
tags: volume block-storage block unmount
55
dates:
6-
validation: 2025-06-09
6+
validation: 2025-10-10
77
posted: 2023-11-23
88
---
99
import Requirements from '@macros/iam/requirements.mdx'
1010

11-
12-
## Unmounting a Block Storage volume
13-
1411
Unmounting a volume means detaching it from the operating system so it is no longer accessible. You can do this if you want to stop using it, prevent data corruption, or plan to [detach it](/block-storage/how-to/detach-a-volume/) from your Instance and attach it to another. This page shows you how to unmount a volume from the operating system using the `umount` command.
1512

1613
<Requirements />

‎pages/block-storage/concepts.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ import StorageBootOnBlock from '@macros/storage/boot-on-block.mdx'
3030

3131
IOPS or Input/Ouptut Operations Per Second, is a unit of measurement that indicates how many read/write operations a storage device is performing per second.
3232

33-
Scaleway Block Storage Low Latency offers two IOPS limits:
33+
Scaleway Block Storage offers two IOPS limits:
3434

3535
- 5000 IOPS (5K IOPS)
3636
- 15 000 IOPS (15K IOPS)

0 commit comments

Comments
 (0)