diff options
| author | bgbhpe <brian.boylston@hpe.com> | 2016-07-08 11:43:56 -0400 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2016-07-08 17:43:56 +0200 |
| commit | f3bc4ccc2edf5ad2a99d6ba2795b9999fe76c3df (patch) | |
| tree | 987dd78ab706d260ae67aac2cf8abfbba753d0dd /shell-completion/zsh/_systemd-nspawn | |
| parent | 905c37e60ef653557d0354c2afa94546c31efe50 (diff) | |
rules: block: add support for pmem devices (#3683)
Persistent memory devices can be exposed as block devices as /dev/pmemN
and /dev/pmemNs. pmemN is the raw device and is byte-addressable from
within the kernel and when mmapped by applications from a DAX-mounted
file system. pmemNs has the block translation table (BTT) layered on top,
offering atomic sector/block access. Both pmemN and pmemNs are expected
to contain file systems.
blkid(8) and lsblk(8) seem to correctly report on pmemN and pmemNs.
systemd v219 will populate /dev/disk/by-uuid/ when, for example, mkfs is
used on pmem, but systemd v228 does not.
Add pmem to the whitelist.
Diffstat (limited to 'shell-completion/zsh/_systemd-nspawn')
0 files changed, 0 insertions, 0 deletions