> Follow-up question: Is my proposed strategy below correct:
> - Make a copy of all existing directories and files on the current disk using
> clonezilla.
> - Install the new M.2 SSDs.
> - Partitioning the new SSDs for RAID1 using an external tool.
> - Doing a minimal installation of C7 and
Hallo Simon,
> Anyway, the splitting of large disks has additional advantages. Think of
> what happens in case of a failure (power loss, kernel crash...). With the
> disk as one large chunk, the whole disk has to be resynced on restart
> while with smaller segments only those which are marked as
> On 01/11/2023 01:33 PM, H wrote:
>> On 01/11/2023 02:09 AM, Simon Matter wrote:
>>> What I usually do is this: "cut" the large disk into several pieces of
>>> equal size and create individual RAID1 arrays. Then add them as LVM PVs
>>> to
>>> one large VG. The advantage is that with one error on
> On 01/11/2023 02:09 AM, Simon Matter wrote:
>> What I usually do is this: "cut" the large disk into several pieces of
>> equal size and create individual RAID1 arrays. Then add them as LVM PVs
>> to
>> one large VG. The advantage is that with one error on one disk, you wont
>> lose redundancy on
On 01/11/2023 01:33 PM, H wrote:
> On 01/11/2023 02:09 AM, Simon Matter wrote:
>> What I usually do is this: "cut" the large disk into several pieces of
>> equal size and create individual RAID1 arrays. Then add them as LVM PVs to
>> one large VG. The advantage is that with one error on one disk,
On 01/11/2023 08:34 AM, Robert Moskowitz wrote:
>
> Perhaps you have not dealt with Firefox? :)
>
> On my Fedora 35 notebook, it slowly gobbles memory and I have to quit it
> after some number of days and restart.
>
> Now I only have 16GB of memory, 16GB physical swap, and 8GB zram swap.
>
>
On 01/11/2023 02:09 AM, Simon Matter wrote:
> What I usually do is this: "cut" the large disk into several pieces of
> equal size and create individual RAID1 arrays. Then add them as LVM PVs to
> one large VG. The advantage is that with one error on one disk, you wont
> lose redundancy on the
>
>
> On 1/11/23 02:09, Simon Matter wrote:
>>> I plan to upgrade an existing C7 computer which currently has one 256
>>> GB
>>> SSD to use mdadmin software RAID1 after adding two 4 TB M2. SSDs, the
>>> rest
>>> of the system remaining the same. The system also has one additional
>>> internal and
>
>
> On 1/10/23 20:20, Robert Moskowitz wrote:
>> Official drives should be here Friday, so trying to get reading.
>>
>>
>>
>> On 1/9/23 01:32, Simon Matter wrote:
>>> Hi
>>>
Continuing this thread, and focusing on RAID1.
I got an HPE Proliant gen10+ that has hardware RAID support.
On 1/11/23 02:09, Simon Matter wrote:
I plan to upgrade an existing C7 computer which currently has one 256 GB
SSD to use mdadmin software RAID1 after adding two 4 TB M2. SSDs, the rest
of the system remaining the same. The system also has one additional
internal and one external harddisk but
On 1/10/23 20:20, Robert Moskowitz wrote:
Official drives should be here Friday, so trying to get reading.
On 1/9/23 01:32, Simon Matter wrote:
Hi
Continuing this thread, and focusing on RAID1.
I got an HPE Proliant gen10+ that has hardware RAID support. (can turn
it off if I want).
This is an automated email from the git hooks/post-receive script.
arrfab pushed a commit to branch main
in repository centos/centos.org.
The following commit(s) were added to refs/heads/main by this push:
new 078b3ae Fixed hour/link for infra sig meeting
078b3ae is described below
commit
12 matches
Mail list logo
