diff --git a/macros/block-storage/block-storage-volume-types.mdx b/macros/block-storage/block-storage-volume-types.mdx
index 69fba89a66..732293b9e3 100644
--- a/macros/block-storage/block-storage-volume-types.mdx
+++ b/macros/block-storage/block-storage-volume-types.mdx
@@ -4,6 +4,6 @@ macro: block-storage-volume-types
| Volume type | IOPS | Underlying hardware | Latency | Max volume size | Recommended use cases | Availability & resilience |
|-----------------------------------|----------|--------------------------------|---------------------|----------------------|-------------------------|----------------------------|
-| `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 |
-| `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 |
-| `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 |
\ No newline at end of file
+| `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 |
+| `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 |
+| `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 |
\ No newline at end of file
diff --git a/pages/block-storage/api-cli/increasing-partition-size.mdx b/pages/block-storage/api-cli/increasing-partition-size.mdx
new file mode 100644
index 0000000000..fb2c3c15fc
--- /dev/null
+++ b/pages/block-storage/api-cli/increasing-partition-size.mdx
@@ -0,0 +1,63 @@
+---
+title: Increasing the size of a partition
+description: Learn how to increase the size of a partition within a Block Storage volume
+tags: volume block-storage block resize growpart increase size
+dates:
+ validation: 2025-10-13
+ posted: 2019-11-29
+---
+import Requirements from '@macros/iam/requirements.mdx'
+
+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.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- An [Instance](/instances/concepts/#instance)
+- [Attached](/block-storage/how-to/attach-a-volume/) an additional Block Storage volume to your Instance
+
+
+ - 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
+ - You must have partitioned your volume to follow the procedure below
+ - If the partition you want to resize is mounted, you must [unmount it](/block-storage/api-cli/unmounting-a-volume/) beforehand
+
+
+1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/).
+
+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`:
+
+ ```
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
+ sda 8:0 0 23.3G 0 disk
+ ├─sda1 8:1 0 23.2G 0 part /
+ ├─sda14 8:14 0 4M 0 part
+ └─sda15 8:15 0 106M 0 part /boot/efi
+ sdb 8:16 0 38.6G 0 disk
+ └─sdb1 8:17 0 18.6G 0 part
+ ```
+
+3. Use `growpart` to increase the partition size of your Block Storage volume (here `sdb1`):
+
+ ```
+ # Replace /dev/sdX 1 with the name of your partition
+ growpart /dev/sdX 1
+ ```
+
+ An output similar to the following displays:
+
+ ```
+ CHANGED: partition=1 start=0 old: size=39061504 end=39061504 new: size=58490880 end=58490880
+ ```
+
+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`.
+ ```
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
+ sda 8:0 0 18.6G 0 disk
+ ├─sda1 8:1 0 18.5G 0 part /
+ ├─sda14 8:14 0 4M 0 part
+ └─sda15 8:15 0 106M 0 part /boot/efi
+ sdb 8:16 0 27.9G 0 disk
+ └─sdb1 8:17 0 27.9G 0 part
\ No newline at end of file
diff --git a/pages/block-storage/api-cli/increasing-volume-size.mdx b/pages/block-storage/api-cli/increasing-volume-size.mdx
index d7de7f32a3..9b513f42ad 100644
--- a/pages/block-storage/api-cli/increasing-volume-size.mdx
+++ b/pages/block-storage/api-cli/increasing-volume-size.mdx
@@ -3,7 +3,7 @@ title: Increasing the size of Block Storage volumes via the Scaleway API
description: This page explains how to increase the size of a Block Storage volume using the Scaleway API.
tags: increase expand increment raise storage volume block
dates:
- validation: 2025-09-17
+ validation: 2025-10-13
posted: 2025-03-04
---
import Requirements from '@macros/iam/requirements.mdx'
diff --git a/pages/block-storage/api-cli/managing-a-volume.mdx b/pages/block-storage/api-cli/managing-a-volume.mdx
deleted file mode 100644
index 5a4183c65d..0000000000
--- a/pages/block-storage/api-cli/managing-a-volume.mdx
+++ /dev/null
@@ -1,236 +0,0 @@
----
-title: Managing a Block Storage volume
-description: Master Block Storage with our comprehensive guide. Learn to format, mount, transfer data, and expand partitions efficiently. Perfect for all skill levels.
-tags: volume block-storage block mount format use
-dates:
- validation: 2025-06-09
- posted: 2019-11-29
----
-import Requirements from '@macros/iam/requirements.mdx'
-
-
-This documentation only explains how to mount **additional block volumes to your Instance**, as the root volume of your Instance is already mounted at creation. The volume where your OS is running cannot be mounted.
-
-
-
-- A Scaleway account logged into the [console](https://console.scaleway.com)
-- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
-- An [Instance](/instances/concepts/#instance)
-- [Attached](/block-storage/how-to/attach-a-volume/) an additional Block Storage volume to your Instance
-
-## Mounting and using a Block Storage volume
-
-In order to mount and use your Block Storage volume, you need to connect to the Instance it is attached to, via SSH.
-Then, check that the volume is available, format it, and mount it following the instructions below.
-
-### Verifying device availability
-
-1. Connect to your Instance with `ssh`.
- ```
- ssh root@
- ```
-2. Use the `lsblk` command to confirm that your block volume is available:
- ```
- lsblk
- ```
-
- You should see an output similar to the following. The root Block volume `sda`, contains your OS. The Block volume named `sdb` is the one we will be mounting to the Instance.
-
- ```sh no-copy
- root@scw-festive-agnesi:~# lsblk
- NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
- sda 8:0 0 18.6G 0 disk
- ├─sda1 8:1 0 18.5G 0 part /
- ├─sda14 8:14 0 4M 0 part
- └─sda15 8:15 0 106M 0 part /boot/efi
- sdb 8:16 0 27.9G 0 disk
- ```
-
-
- The Scaleway ecosystem uses [GB](https://en.wikipedia.org/wiki/Gigabyte) to define storage sizes and not [GiB](https://en.wikipedia.org/wiki/Gibibyte) as the default on linux.
-
-
-### Formatting the Block volume
-
-Formatting your volume prepares it for storing files.
-
-
- The procedure below describes how to format your volume using the `mkfs` command, which will **erase all data on the volume**.
-
-
-1. Create a file system with the following command. This command uses the `ext4` file system, though you can choose another if you prefer.
- ```
- # Make sure that you replace `/dev/sdX` with the name of your volume
- mkfs.ext4 /dev/sdX
- ```
-2. Run the following command to check if your file system was correctly created.
- ```
- lsblk -f
- ```
-
- You should see an output like the following. Check that the `FSTYPE` field matches `ext4` for your Block volume. In this example, we have formatted the `sdb` volume.
-
- ```sh no-copy
- root@scw-festive-agnesi:~# lsblk -f
- NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
- sda
- ├─sda1
- │ ext4 1.0 cloudimg-rootfs
- │ cf5b092b-9a8b-49e9-980c-b44b5e3ed197 14.5G 18% /
- ├─sda14
- │
- └─sda15
- vfat FAT32 UEFI D590-3FD4 98.3M 6% /boot/efi
- sdb ext4 1.0 d36bdf8b-b2ff-4e2b-9736-cc05940aea35
- ```
-
----
-
-### Creating the mount point and mounting the Block volume
-
-Once you have created your file system, you need to define where you want to mount your volume, and create a mount point (directory) for it.
-
-1. Create the mount point. You can replace `block-volume` with another name for your mount point.
- ```
- mkdir /mnt/block-volume
- ```
-2. Mount the volume. We recommend that you use the `defaults` option, as in the command below.
- ```
- # Replace sdX with the name of your volume
- mount -o defaults /dev/sdX /mnt/block-volume
- ```
-
- If you want to see all available options, you can run `man mount` on your Instance.
-
-3. Run the following command to check if your volume was properly mounted:
- ```
- lsblk
- ```
-
- You should see an output like the following. Check the `MOUNTPOINT` field.
-
- ```sh no-copy
- root@scw-festive-agnesi:~# lsblk
- NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
- sda 8:0 0 18.6G 0 disk
- ├─sda1 8:1 0 18.5G 0 part /
- ├─sda14 8:14 0 4M 0 part
- └─sda15 8:15 0 106M 0 part /boot/efi
- sdb 8:16 0 27.9G 0 disk /mnt/block-volume
- ```
-
-The `sdb` volume is mounted at `/mnt/block-volume`.
-
----
-
-### Using fstab for Persistent Mounting
-
-With the current configuration, your volume will not be mounted automatically upon reboot. Use the `/etc/fstab` file to ensure the reboot does not impact your file system.
-
-Run the following command to make sure your volume is automatically mounted to your Instance upon reboot. You must replace `sdX` with your volume.
-
-```
-echo "UUID=$(blkid --output value /dev/sdX | head -n1) /mnt/block-volume ext4 defaults 0 0" >> /etc/fstab
-```
-
----
-
-### Transferring data from your local machine to the remote Block volume
-
-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.
-
-1. Check that rsync is installed on your local machine with the following command:
- ```
- rsync --version
- ```
-
- An output similar to the following displays:
-
- ```sh no-copy
- rsync version 3.1.3 protocol version 31
- Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others.
- Web site: http://rsync.samba.org/
- Capabilities:
- 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
- socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
- append, ACLs, xattrs, iconv, symtimes, prealloc
-
- rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you
- are welcome to redistribute it under certain conditions. See the GNU
- General Public Licence for details.
- ```
-
-
- If you get a `command not found` output (or similar), you need to install `rsync`:
- - On Linux Ubuntu and Debian systems, you can do this with the APT package tool using the `sudo apt install rsync` command.
- - For Linux CentOS/ Fedora, you can use the YUM package manager: `sudo yum install rsync`.
- - On Mac OSX with the Homebrew package manager, you can use `brew install rsync`.
-
-
-2. On your local machine, open a new terminal and use the following command to create a file called `hello-world.txt`:
- ```
- nano hello-world.txt
- ```
-
-3. Enter the text `Hello World!`.
-
-4. Press `Ctrl+O`, then `Enter`, then `Ctrl+X` to save and exit the file.
-
-5. Enter the following command to transfer the file to your Instance's mounted block volume. Ensure that you use your own Instance's IP address:
-
- ```
- rsync -a hello-world.txt root@:/mnt/block-volume
- ```
-
-The file is now transferred. You can connect to your Instance again, and use the command `cd /mnt/block-volume ; ls` to check that the file appears in the directory.
-
----
-
-## Increasing the partition size of the volume with growpart
-
-`growpart` 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.
-
-
- - 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
- - You must have partitioned your volume to follow the procedure below
- - If the partition you want to resize is mounted, you must [unmount it](/block-storage/api-cli/unmounting-a-volume/) beforehand
-
-
-1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/).
-
-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`:
-
- ```
- root@scw-festive-agnesi:~# lsblk
- NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
- sda 8:0 0 23.3G 0 disk
- ├─sda1 8:1 0 23.2G 0 part /
- ├─sda14 8:14 0 4M 0 part
- └─sda15 8:15 0 106M 0 part /boot/efi
- sdb 8:16 0 38.6G 0 disk
- └─sdb1 8:17 0 18.6G 0 part
- ```
-
-3. Use `growpart` to increase the partition size of your Block Storage volume (here `sdb1`):
-
- ```
- # Replace /dev/sdX 1 with the name of your partition
- growpart /dev/sdX 1
- ```
-
- An output similar to the following displays:
-
- ```
- CHANGED: partition=1 start=0 old: size=39061504 end=39061504 new: size=58490880 end=58490880
- ```
-
-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`.
- ```
- root@scw-festive-agnesi:~# lsblk
- NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
- sda 8:0 0 18.6G 0 disk
- ├─sda1 8:1 0 18.5G 0 part /
- ├─sda14 8:14 0 4M 0 part
- └─sda15 8:15 0 106M 0 part /boot/efi
- sdb 8:16 0 27.9G 0 disk
- └─sdb1 8:17 0 27.9G 0 part
\ No newline at end of file
diff --git a/pages/block-storage/api-cli/transfer-local-data-to-volume.mdx b/pages/block-storage/api-cli/transfer-local-data-to-volume.mdx
new file mode 100644
index 0000000000..4f686477b9
--- /dev/null
+++ b/pages/block-storage/api-cli/transfer-local-data-to-volume.mdx
@@ -0,0 +1,44 @@
+---
+title: Transferring local data to a Block Storage volume
+description: This page explains how to transfer local data to a Block Storage volume mounted to a Scaleway Instance.
+tags: copy transfer upload rsync ftp send data file local fylesystem
+dates:
+ validation: 2025-10-10
+ posted: 2025-10-10
+---
+import Requirements from '@macros/iam/requirements.mdx'
+
+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.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- An [Instance](/instances/concepts/#instance)
+- [Attached](/block-storage/how-to/attach-a-volume/) a Block Storage volume to your Instance
+- Installed [Rsync](https://rsync.samba.org/)
+
+1. Check that rsync is installed on your local machine with the following command:
+ ```
+ rsync --version
+ ```
+
+ An output similar to the following displays:
+
+ ```sh no-copy
+ rsync version 3.1.3 protocol version 31
+ ```
+
+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:
+
+ ```
+ rsync -a path/to/file.txt root@:/mnt/block-volume
+ ```
+
+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:
+
+ ```bash
+ ls /mnt/block-volume
+ ```
+
+Refer to the [official Rsync documentation](https://download.samba.org/pub/rsync/rsync.1#OPTION_SUMMARY) for more information on the different options available.
\ No newline at end of file
diff --git a/pages/block-storage/api-cli/unmounting-a-volume.mdx b/pages/block-storage/api-cli/unmounting-a-volume.mdx
index 1949e5474c..c89e6d13bf 100644
--- a/pages/block-storage/api-cli/unmounting-a-volume.mdx
+++ b/pages/block-storage/api-cli/unmounting-a-volume.mdx
@@ -3,14 +3,11 @@ title: Unmounting a Block Storage volume
description: Learn how to safely unmount a Block Storage volume from your Instance, and ensure data integrity.
tags: volume block-storage block unmount
dates:
- validation: 2025-06-09
+ validation: 2025-10-10
posted: 2023-11-23
---
import Requirements from '@macros/iam/requirements.mdx'
-
-## Unmounting a Block Storage volume
-
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.
diff --git a/pages/block-storage/concepts.mdx b/pages/block-storage/concepts.mdx
index 78f9dc97bc..d72f091512 100644
--- a/pages/block-storage/concepts.mdx
+++ b/pages/block-storage/concepts.mdx
@@ -30,7 +30,7 @@ import StorageBootOnBlock from '@macros/storage/boot-on-block.mdx'
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.
-Scaleway Block Storage Low Latency offers two IOPS limits:
+Scaleway Block Storage offers two IOPS limits:
- 5000 IOPS (5K IOPS)
- 15 000 IOPS (15K IOPS)
diff --git a/pages/block-storage/faq.mdx b/pages/block-storage/faq.mdx
index 1daa065d11..6f08faea0c 100644
--- a/pages/block-storage/faq.mdx
+++ b/pages/block-storage/faq.mdx
@@ -34,7 +34,7 @@ Block Storage allows you to create bigger volumes and those volumes are persiste
You can attach a maximum of 16 volumes (including the mandatory boot volume) to a single Instance.
- Refer to the [dedicated documentation](/block-storage/reference-content/differences-between-5kiops-volumes/) for more information on the differences between Block Storage 5K legacy volumes and Block Storage Low Latency 5K volumes.
+ Refer to the [dedicated documentation](/block-storage/reference-content/differences-between-5kiops-volumes/) for more information on the differences between Block Storage 5K legacy volumes and Block Storage 5K volumes.
### What level of performance is expected from a block volume?
@@ -66,18 +66,18 @@ The Block Storage billing scheme is not the same as for Object Storage. You are
## Usage and management
-### How can I convert a Block Storage legacy volume into a Block Storage Low Latency volume?
+### How can I convert a Block Storage legacy volume into a Block Storage volume?
-Although there is no direct way to change the storage class of a volume while preserving its ID, you can still convert a Block Storage legacy volume (along with its data) into a Block Storage Low Latency volume using the snapshot export/import features as a temporary solution. This allows you to transition a Block Storage legacy (`b_ssd`) snapshot into a Block Storage Low Latency (`sbs_5k` or `sbs_15k`) snapshot and then turn the snapshot into a Block Storage Low Latency volume.
+Although there is no direct way to change the storage class of a volume while preserving its ID, you can still convert a Block Storage legacy volume (along with its data) into a Block Storage volume using the snapshot export/import features as a temporary solution. This allows you to transition a Block Storage legacy (`b_ssd`) snapshot into a Block Storage (`sbs_5k` or `sbs_15k`) snapshot and then turn the snapshot into a Block Storage volume.
The process below requires manual intervention and **does not preserve the original volume's ID**.
- While this approach allows you to transition to a Block Storage Low Latency volume, it is only a workaround.
+ While this approach allows you to transition to a Block Storage volume, it is only a workaround.
1. [Create a snapshot of your Block Storage legacy volume](/block-storage/how-to/create-a-snapshot/).
2. [Export the snapshot](/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots).
-3. [Import the snapshot into a new Low Latency volume](https://www.scaleway.com/en/developers/api/block-storage/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket).
+3. [Import the snapshot into a new volume](https://www.scaleway.com/en/developers/api/block-storage/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket).
## Can I manage my Block Storage volumes using the Scaleway Instances API?
diff --git a/pages/block-storage/how-to/attach-a-volume.mdx b/pages/block-storage/how-to/attach-a-volume.mdx
index d55c615322..0fd8bc277c 100644
--- a/pages/block-storage/how-to/attach-a-volume.mdx
+++ b/pages/block-storage/how-to/attach-a-volume.mdx
@@ -3,12 +3,12 @@ title: How to attach a Block Storage volume to an Instance
description: This guide explains how to attach a Block Storage volume to a Scaleway Instance. Follow simple steps to manage your storage efficiently.
tags: attach block storage volume
dates:
- validation: 2025-03-24
+ validation: 2025-10-13
posted: 2023-11-23
---
import Requirements from '@macros/iam/requirements.mdx'
-You can attach up to **15 volumes** at a time to a single Instance. You can attach a Block Storage volume to your Instance at any time, as long as they are both in the same [Availability Zone](/instances/concepts/#availability-zone).
+Scaleway Block Storage volumes must be attached to an Instance before being used. You can attach up to **15 volumes** at a time to a single Instance. You can attach a Block Storage volume to your Instance at any time, as long as they are both in the same [Availability Zone](/instances/concepts/#availability-zone).
@@ -38,7 +38,7 @@ You can also attach a Block storage to an Instance the following way:
6. Click **Attach volume to Instance**.
- To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**.
+ To use **[Block Storage](/block-storage/) 15k** volumes, your Instance must have at least **3 GiB/s of block bandwidth**.
You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation.
Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`.
diff --git a/pages/block-storage/how-to/create-a-snapshot.mdx b/pages/block-storage/how-to/create-a-snapshot.mdx
index b2c2bf193f..3adb6710ed 100644
--- a/pages/block-storage/how-to/create-a-snapshot.mdx
+++ b/pages/block-storage/how-to/create-a-snapshot.mdx
@@ -3,11 +3,12 @@ title: How to create a snapshot of a Block Storage volume
description: Discover how to easily create a snapshot of a Block Storage volume. Follow our step-by-step guide to efficiently manage your storage resources.
tags: create snapshot block storage volume
dates:
- validation: 2025-03-24
+ validation: 2025-10-13
posted: 2023-11-23
---
import Requirements from '@macros/iam/requirements.mdx'
+Scaleway Block Storage allows you to create [snapshots](/block-storage/concepts/#snapshot) of your volumes to easily back up and restore data across your Instances.
diff --git a/pages/block-storage/how-to/create-a-volume.mdx b/pages/block-storage/how-to/create-a-volume.mdx
index ff1101175f..5f5467df35 100644
--- a/pages/block-storage/how-to/create-a-volume.mdx
+++ b/pages/block-storage/how-to/create-a-volume.mdx
@@ -1,13 +1,14 @@
---
-title: How to create a Block Storage low latency volume
+title: How to create a Block Storage volume
description: Learn how to efficiently create a low-latency Block Storage volume with our detailed step-by-step guide. Enhance your storage performance seamlessly.
tags: create block storage volume add
dates:
- validation: 2025-09-25
+ validation: 2025-10-13
posted: 2023-11-23
---
import Requirements from '@macros/iam/requirements.mdx'
+Scaleway Block Storage allows you to easily create volumes to attach to your Instances. Volumes are storage spaces that you can attach to one or several Instances.
@@ -22,11 +23,10 @@ import Requirements from '@macros/iam/requirements.mdx'
- Enter a name for your volume or leave the automatically generated name.
- Select an [IOPS](/block-storage/concepts/#iops) option. You cannot edit the IOPS of a volume after its creation.
- To use **Block Storage Low Latency 15k**, your Instance must have at least **3 GiB/s of block bandwidth**.
+ To use **Block Storage 15k**, your Instance must have at least **3 GiB/s of block bandwidth**.
You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/block-storage/reference-content/block-instances-bandwidth-overview/) documentation.
- Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`.
- This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage.
+ Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`.
- Define a volume size of at least 5 GB.
- Optionally, select an Instance from the drop-down to attach your volume.
diff --git a/pages/block-storage/how-to/create-volume-from-snapshot.mdx b/pages/block-storage/how-to/create-volume-from-snapshot.mdx
index 9c7cd8d336..dabc5acedb 100644
--- a/pages/block-storage/how-to/create-volume-from-snapshot.mdx
+++ b/pages/block-storage/how-to/create-volume-from-snapshot.mdx
@@ -3,12 +3,14 @@ title: How to create a Block Storage volume from a snapshot
description: Discover how to efficiently create a Block Storage volume from a snapshot with our comprehensive step-by-step guide. Optimize your storage workflow effortlessly.
tags: create snapshot block storage volume
dates:
- validation: 2025-03-24
+ validation: 2025-10-13
posted: 2023-11-23
---
import Requirements from '@macros/iam/requirements.mdx'
+Creating a volume from a snapshot allows you to quickly restore data to a previous state. It also enables duplication of storage environments for testing or development purposes.
+
- A Scaleway account logged into the [console](https://console.scaleway.com)
diff --git a/pages/block-storage/how-to/delete-a-snapshot.mdx b/pages/block-storage/how-to/delete-a-snapshot.mdx
index 023df54ce4..e6f93633e9 100644
--- a/pages/block-storage/how-to/delete-a-snapshot.mdx
+++ b/pages/block-storage/how-to/delete-a-snapshot.mdx
@@ -3,7 +3,7 @@ title: How to delete a volume snapshot
description: This guide explains the steps to safely delete a volume snapshot from your Scaleway account.
tags: delete snapshot block volume storage
dates:
- validation: 2025-03-24
+ validation: 2025-10-13
posted: 2023-11-23
---
import Requirements from '@macros/iam/requirements.mdx'
diff --git a/pages/block-storage/how-to/delete-a-volume.mdx b/pages/block-storage/how-to/delete-a-volume.mdx
index 91172c4b4e..6b4cc8981d 100644
--- a/pages/block-storage/how-to/delete-a-volume.mdx
+++ b/pages/block-storage/how-to/delete-a-volume.mdx
@@ -3,7 +3,7 @@ title: How to delete a Block Storage volume
description: This guide explains the steps to safely delete a Block Storage volume from your Scaleway account.
tags: delete cancel terminate block volume storage
dates:
- validation: 2025-03-24
+ validation: 2025-10-13
posted: 2023-11-23
---
import Requirements from '@macros/iam/requirements.mdx'
diff --git a/pages/block-storage/how-to/detach-a-volume.mdx b/pages/block-storage/how-to/detach-a-volume.mdx
index b2cc6fe4c3..68603d520c 100644
--- a/pages/block-storage/how-to/detach-a-volume.mdx
+++ b/pages/block-storage/how-to/detach-a-volume.mdx
@@ -18,6 +18,7 @@ You can detach a Block Storage volume from your Instance at any time.
- A Scaleway account logged into the [console](https://console.scaleway.com)
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
- Created a [Block Storage volume](/block-storage/how-to/create-a-volume/) that is [attached](/block-storage/how-to/attach-a-volume/) to an Instance
+- [Unmounted the volume](/block-storage/api-cli/unmounting-a-volume/) from your Instance
1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. The Block Storage page displays.
2. Click > **Detach from Instance** next to the volume of your choice. A pop-up displays.
diff --git a/pages/block-storage/how-to/increase-block-volume.mdx b/pages/block-storage/how-to/increase-block-volume.mdx
index deb79c933a..8f11c67e68 100644
--- a/pages/block-storage/how-to/increase-block-volume.mdx
+++ b/pages/block-storage/how-to/increase-block-volume.mdx
@@ -8,6 +8,7 @@ dates:
---
import Requirements from '@macros/iam/requirements.mdx'
+Increasing the size of your Block Storage volume allows you to store more data without having to create a new volume.
diff --git a/pages/block-storage/how-to/mount-a-volume.mdx b/pages/block-storage/how-to/mount-a-volume.mdx
new file mode 100644
index 0000000000..caaa8e1f02
--- /dev/null
+++ b/pages/block-storage/how-to/mount-a-volume.mdx
@@ -0,0 +1,128 @@
+---
+title: How to mount a Block Storage volume to an Instance
+description: This guide explains how to mount a Block Storage volume to your Scaleway Instance before being able to use it.
+tags: mount link volume disk instance
+dates:
+ validation: 2025-10-10
+ posted: 2025-10-10
+---
+import Requirements from '@macros/iam/requirements.mdx'
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- An [Instance](/instances/concepts/#instance)
+- [Attached](/block-storage/how-to/attach-a-volume/) an additional Block Storage volume to your Instance
+
+## Mounting and using a Block Storage volume
+
+In order to mount and use your Block Storage volume, you need to connect to the Instance it is attached to, via SSH.
+Then, check that the volume is available, format it, and mount it following the instructions below.
+
+### Verifying device availability
+
+1. Connect to your Instance with `ssh`.
+ ```
+ ssh root@
+ ```
+2. Use the `lsblk` command to confirm that your block volume is available:
+ ```
+ lsblk
+ ```
+
+ You should see an output similar to the following. The root Block volume `sda`, contains your OS. The Block volume named `sdb` is the one we will be mounting to the Instance.
+
+ ```sh no-copy
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
+ sda 8:0 0 18.6G 0 disk
+ ├─sda1 8:1 0 18.5G 0 part /
+ ├─sda14 8:14 0 4M 0 part
+ └─sda15 8:15 0 106M 0 part /boot/efi
+ sdb 8:16 0 27.9G 0 disk
+ ```
+
+
+ The Scaleway ecosystem uses [GB](https://en.wikipedia.org/wiki/Gigabyte) to define storage sizes and not [GiB](https://en.wikipedia.org/wiki/Gibibyte) as the default on linux.
+
+
+### Formatting the Block volume
+
+Formatting your volume prepares it for storing files.
+
+
+ The procedure below describes how to format your volume using the `mkfs` command, which will **erase all data on the volume**.
+
+
+1. Create a file system with the following command. This command uses the `ext4` file system, though you can choose another if you prefer.
+ ```
+ # Make sure that you replace `/dev/sdX` with the name of your volume
+ mkfs.ext4 /dev/sdX
+ ```
+2. Run the following command to check that your file system was correctly created.
+ ```
+ lsblk -f
+ ```
+
+ You should see an output like the following. Check that the `FSTYPE` field matches `ext4` for your Block volume. In this example, we have formatted the `sdb` volume.
+
+ ```sh no-copy
+ root@scw-festive-agnesi:~# lsblk -f
+ NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
+ sda
+ ├─sda1
+ │ ext4 1.0 cloudimg-rootfs
+ │ cf5b092b-9a8b-49e9-980c-b44b5e3ed197 14.5G 18% /
+ ├─sda14
+ │
+ └─sda15
+ vfat FAT32 UEFI D590-3FD4 98.3M 6% /boot/efi
+ sdb ext4 1.0 d36bdf8b-b2ff-4e2b-9736-cc05940aea35
+ ```
+
+---
+
+### Creating the mount point and mounting the Block volume
+
+Once you have created your file system, you need to define where you want to mount your volume, and create a mount point (directory) for it.
+
+1. Create the mount point. You can replace `block-volume` with another name for your mount point.
+ ```
+ mkdir /mnt/block-volume
+ ```
+2. Mount the volume. We recommend that you use the `defaults` option, as in the command below.
+ ```
+ # Replace sdX with the name of your volume
+ mount -o defaults /dev/sdX /mnt/block-volume
+ ```
+
+ If you want to see all available options, you can run `man mount` on your Instance.
+
+3. Run the following command to check if your volume was properly mounted:
+ ```
+ lsblk
+ ```
+
+ You should see an output like the following. Check the `MOUNTPOINT` field.
+
+ ```
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
+ sda 8:0 0 18.6G 0 disk
+ ├─sda1 8:1 0 18.5G 0 part /
+ ├─sda14 8:14 0 4M 0 part
+ └─sda15 8:15 0 106M 0 part /boot/efi
+ sdb 8:16 0 27.9G 0 disk /mnt/block-volume
+ ```
+
+The `sdb` volume is mounted at `/mnt/block-volume`.
+
+### Using fstab for persistent mounting
+
+With the current configuration, your volume will not be mounted automatically upon reboot. Use the `/etc/fstab` file to ensure the reboot does not impact your file system.
+
+Run the following command to make sure your volume is automatically mounted to your Instance upon reboot. You must replace `sdX` with your volume.
+
+```bash
+echo "UUID=$(blkid --output value /dev/sdX | head -n1) /mnt/block-volume ext4 defaults 0 0" >> /etc/fstab
+```
+
diff --git a/pages/block-storage/how-to/unmount-a-volume.mdx b/pages/block-storage/how-to/unmount-a-volume.mdx
index 8f003afbef..2e1b7533d8 100644
--- a/pages/block-storage/how-to/unmount-a-volume.mdx
+++ b/pages/block-storage/how-to/unmount-a-volume.mdx
@@ -8,7 +8,6 @@ dates:
---
import Requirements from '@macros/iam/requirements.mdx'
-
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.
@@ -16,7 +15,7 @@ Unmounting a volume means detaching it from the operating system so it is no lon
- A Scaleway account logged into the [console](https://console.scaleway.com)
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
- Created an [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
-- Created an [Instance](/instances/how-to/create-an-instance/) with an additional Block Storage volume
+- Created an [Instance](/instances/how-to/create-an-instance/) with a Block Storage volume [attached](/block-storage/how-to/attach-a-volume/) and [mounted](/block-storage/how-to/mount-a-volume/) to it
1. Open a terminal and use the following command to connect to your Instance. Make sure that you replace `` with your Instance's IP. You can also find the SSH command in your Instance's **Overview** tab in the Scaleway console.
diff --git a/pages/block-storage/index.mdx b/pages/block-storage/index.mdx
index 0104c48c7f..02fdc7fc0a 100644
--- a/pages/block-storage/index.mdx
+++ b/pages/block-storage/index.mdx
@@ -1,13 +1,13 @@
---
-title: Block Storage Low Latency Documentation
-description: Explore Scaleway Block Storage Low Latency with quickstart guides, how-tos, and more.
+title: Block Storage Documentation
+description: Explore Scaleway Block Storage with quickstart guides, how-tos, and more.
---
@@ -25,21 +25,21 @@ description: Explore Scaleway Block Storage Low Latency with quickstart guides,
diff --git a/pages/block-storage/menu.ts b/pages/block-storage/menu.ts
index 12fa8d12c1..c1fbd969b0 100644
--- a/pages/block-storage/menu.ts
+++ b/pages/block-storage/menu.ts
@@ -69,8 +69,8 @@ export const blockStorageMenu = {
slug: 'https://www.scaleway.com/en/developers/api/block-storage/',
},
{
- label: 'Managing a volume',
- slug: 'managing-a-volume',
+ label: 'Increasing the size of a partition',
+ slug: 'increasing-partition-size',
},
{
label: 'Increasing volume size via the API',
@@ -88,7 +88,7 @@ export const blockStorageMenu = {
items: [
{
label:
- 'Differences between Block Storage volumes and Block Storage Low Latency volumes',
+ 'Differences between Block Storage volumes',
slug: 'differences-between-5kiops-volumes',
},
{
diff --git a/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx b/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx
index d10b2eee98..125c8598bb 100644
--- a/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx
+++ b/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx
@@ -27,7 +27,7 @@ Bandwidth impacts how your applications perform and interact with other systems.
- To maximize compatibility with [Block Storage Low Latency 15k](/block-storage/), select an Instance with **at least 3 GiB/s** of Block bandwidth.
+ To maximize compatibility with [Block Storage 15k](/block-storage/), select an Instance with **at least 3 GiB/s** of Block bandwidth.
## COPARM1 range
diff --git a/pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx b/pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx
index 156c12e86a..1a411dd542 100644
--- a/pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx
+++ b/pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx
@@ -1,65 +1,33 @@
---
-title: Understand the difference between Block Storage volumes and Block Storage Low Latency volumes
-description: Learn the key differences between Block Storage and Block Storage Low Latency 5K IOPS volumes to choose the optimal storage solution for your needs.
+title: Understand the difference between Block Storage volumes
+description: Learn the key differences between Block Storage legacy, Block Storage 5K IOPS, and Block Storage 15K IOPS volumes to choose the optimal storage solution for your needs.
tags: differences-5kiops volumes block-storage 5kiops
dates:
- validation: 2025-09-17
+ validation: 2025-10-14
posted: 2024-09-05
---
import BlockStorageVolumeTypes from '@macros/block-storage/block-storage-volume-types.mdx'
-When creating volumes from the Scaleway console, you are prompted to choose between [Block Storage Low Latency](/block-storage/) volumes, [block volumes (Block Storage)](/instances/concepts/#block-volumes), and [local volumes (Local Storage)](/instances/concepts/#volumes).
-
-This page provides information about the differences between Block Storage and Block Storage Low Latency 5K [IOPS](/block-storage/concepts/#iops) volumes.
+This page provides information about the differences between Block Storage legacy, Block Storage 5K IOPS, and Block Storage 15K IOPS volumes.
Refer to the [dedicated documentation](/instances/concepts/#volumes) to learn about the differences between Block Storage and Local Storage volumes.
-## Overview
+## Block Storage volume types overview
-## Underlying hardware
-
- - **Block Storage 5K IOPS volumes**:
-
- - They are built using older-generation SSDs. This means that the hardware is slower, as it uses older SSD technology.
- - The 5K IOPS is split between read and write operations, resulting in a total of 10K IOPS (5K for reads and 5K for writes).
-
- - **Block Storage Low Latency 5K IOPS volumes**:
-
- - They are powered by modern NVMe (Non-Volatile Memory Express) disks.
- - NVMe technology provides better performance and is optimized for high-speed storage operations.
-
-## Performance
-
- - **Block Storage 5K IOPS volumes**:
-
- - Their performance is limited by the older SSD hardware, which can result in slower data access and higher latency.
- - The older technology may impact overall speed and responsiveness.
-
- - **Block Storage Low Latency 5K IOPS volumes**:
-
- - Delivers better performance thanks to NVMe disks, which handle 5K IOPS for both read and write operations combined.
- - This provides a significant boost in data processing speed and efficiency.
-
-## Latency
-
- - **Block Storage 5K IOPS volumes**:
-
- - Higher latency due to the use of older SSDs.
- - This can lead to slower application response times, especially in scenarios requiring rapid data access.
-
- - **Block Storage Low Latency 5K IOPS volumes**:
-
- - Offers lower latency and faster access times, making it ideal for applications that require quick data retrieval.
- - The use of NVMe technology ensures a smoother and more responsive experience.
+## Block Storage 5K and Block Storage legacy comparison
+| | Block Storage legacy volumes | Block Storage 5K IOPS volumes |
+|--------------|-----------------------------|-------------------------------|
+| **Underlying hardware** | Built using older-generation SSDs. 5K IOPS split between read and write (total 10K IOPS). | Powered by modern NVMe disks. NVMe provides better performance and is optimized for high-speed operations. |
+| **Performance** | Limited by older SSD hardware, slower data access, higher latency. | Better performance with NVMe disks, 5K IOPS for both read and write combined, faster and more efficient. |
+| **Latency** | Higher latency due to older SSDs, slower application response times. | Lower latency, faster access times, ideal for quick data retrieval, smoother experience with NVMe. |
## Summary
-- **Block Storage 5K IOPS volumes** rely on older, slower SSD technology, leading to higher latency and lower overall performance.
-
-- **Block Storage Low Latency 5K IOPS volumes** use advanced NVMe disks, offering improved performance, lower latency, and faster data access.
+- **Block Storage legacy volumes** rely on older, slower SSD technology, leading to higher latency and lower overall performance.
+- **Block Storage 5K IOPS volumes** use advanced NVMe disks, offering improved performance, lower latency, and faster data access.
-For tasks where performance and low latency are crucial, Block Storage Low Latency volumes provide a more effective solution due to the modern hardware and technological improvements.
\ No newline at end of file
+For tasks where performance and low latency are crucial, Block Storage 5K and 15K IOPS volumes provide a more effective solution due to the modern hardware and technological improvements.