On 2020-05-24 21:37, Patrick O'Callaghan wrote:
Still getting the hang of md. I had it working for several days (2
disks in RAID1 config) but after a system update and reboot, it
A system update or a system upgrade?
suddenly shows no data:
]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
[...]
sdd 8:48 0 931.5G 0 disk
└─md127 9:127 0 931.4G 0 raid1
└─md127p1 259:0 0 931.4G 0 part
sde 8:64 0 931.5G 0 disk
└─md127 9:127 0 931.4G 0 raid1
└─md127p1 259:0 0 931.4G 0 part
# mdadm --detail /dev/md127p1
/dev/md127p1:
Version : 1.2
Creation Time : Wed May 20 16:34:58 2020
Raid Level : raid1
Array Size : 976628736 (931.39 GiB 1000.07 GB)
Used Dev Size : 976630464 (931.39 GiB 1000.07 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Sun May 24 12:29:54 2020
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Consistency Policy : bitmap
Name : Bree:0 (local to host Bree)
UUID : ba979f01:7f1dbe79:24f19f68:7ba6000c
Events : 22436
Number Major Minor RaidDevice State
0 8 48 0 active sync /dev/sdd
1 8 64 1 active sync /dev/sde
# mount /dev/md127p1 /raid
# ls /raid
How is this possible? The only thing that touches the array is a borg
backup run from crontab, which I have verified is working correctly,
including just before the update and reboot this morning. It looks as
if the mount is mounting the wrong thing.
Or am I missing something very obvious?
poc
I would suggest that md is happy and the array is runnig (cat /proc/mdstat).
But I would check the logs to see if the 'mount' had anything to say.
--
Eyal at Home (fedora(a)eyal.emu.id.au)