Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6
-
Linux
Description
MariaDB Server 10.2.4 introduced detection of Shannon SSD cards. Later, in MariaDB Server 10.5.5, the detection of ScaleFlux SSD was introduced.
The detection probably works, but only if the file system is created directly on the block device (without any partition table). Error reporting is somewhat obscure:
perror("open() failed!"); |
The user would only see a message like
open() failed!: Permission denied
|
without knowing which file this is referring to, and what the impact of the failure is.
(The code requires read access to the block device, to determine some of its capabilities. Maybe vendors should try to provide the information via the /sys file system.)
Finally, should a user have multiple types of SSD installed in the same server, not all subsystems would be initialized in my_init_atomic_write().
Attachments
Issue Links
- blocks
-
MDEV-26029 Sparse files are inefficient on thinly provisioned storage
- Closed
- relates to
-
MDEV-11203 Test with atomic_writes (FusionIO, shannon ssd)
- Stalled