On 29/07/20 4:13 am, Ian Pilcher wrote:
> On 7/28/20 11:07 AM, Mantas Mikulėnas wrote:
>> I'd create a single raidcheck.service that runs daily and calls a
>> script that itself determines which device to check, e.g.
>> /dev/md$[dayofyear % 16].
>
> That is the approach that I'm taking, although
On 7/28/20 11:07 AM, Mantas Mikulėnas wrote:
I'd create a single raidcheck.service that runs daily and calls a script
that itself determines which device to check, e.g. /dev/md$[dayofyear % 16].
That is the approach that I'm taking, although it means a fair bit of
work. I need to parse a
I'd create a single raidcheck.service that runs daily and calls a script
that itself determines which device to check, e.g. /dev/md$[dayofyear % 16].
On Sun, Jul 26, 2020, 22:56 Ian Pilcher wrote:
> My NAS has 16 MD RAID devices. I've created a simple service
> (raidcheck@.service) that will
On So, 26.07.20 14:56, Ian Pilcher (arequip...@gmail.com) wrote:
> My NAS has 16 MD RAID devices. I've created a simple service
> (raidcheck@.service) that will trigger a check of the RAID device
> identified by the argument. E.g., 'systemctl start raidcheck@md1' will
> trigger the check of md1
26.07.2020 22:56, Ian Pilcher пишет:
> My NAS has 16 MD RAID devices. I've created a simple service
> (raidcheck@.service) that will trigger a check of the RAID device
> identified by the argument. E.g., 'systemctl start raidcheck@md1' will
> trigger the check of md1 (after checking that no
