On January 12, 2023 1:56:36 AM EST, Simon Matter wrote:
>> 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
On January 12, 2023 2:43:26 AM EST, Michael Schumacher
wrote:
>
>> 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
On 01/12/2023 03:00 AM, Simon Matter wrote:
>> 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
Il 2023-01-12 09:00 Simon Matter ha scritto:
That's a huge improvement especially on very large disks.
Hi, not-ancient versions of Linux MD RAID cope with these issues via two
different means:
- a write bitmap to track dirty disk regions;
- an embedded bad list sector to remap such sectors
> 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
> 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/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
> 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 these should not be touched. The
>
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 these should not be touched. The system
16 matches
Mail list logo