[MDEV-26042] Atomic write capability is not detected correctly Created: 2021-06-29  Updated: 2021-10-26  Resolved: 2021-06-29

Status: Closed
Project: MariaDB Server
Component/s: Embedded Server, Server, Storage Engine - InnoDB
Affects Version/s: 10.2, 10.3, 10.4, 10.5, 10.6
Fix Version/s: 10.5.12, 10.6.3

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: compression
Environment:

Linux


Issue Links:
Blocks
blocks MDEV-26029 Sparse files are inefficient on thinl... Closed
Relates
relates to MDEV-11203 Test with atomic_writes (FusionIO, sh... Stalled

 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().


Generated at Thu Feb 08 09:42:18 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.