All of lore.kernel.org
 help / color / mirror / Atom feed
From: antlists <antlists@youngman.org.uk>
To: Reindl Harald <h.reindl@thelounge.net>,
	David T-G <davidtg-robot@justpickone.org>,
	linux-raid@vger.kernel.org
Subject: Re: partitions & filesystems (was "Re: ???root account locked??? after removing one RAID1 hard disc")
Date: Mon, 30 Nov 2020 22:31:25 +0000	[thread overview]
Message-ID: <e2a9d347-0703-07a6-0128-adf86b35b6f3@youngman.org.uk> (raw)
In-Reply-To: <2d0fcd02-9e3a-d11a-a1cf-a47c1b6ce2c3@thelounge.net>

On 30/11/2020 21:49, Reindl Harald wrote:
> 
> 
> Am 30.11.20 um 21:51 schrieb antlists:
>> On 30/11/2020 20:05, David T-G wrote:
>>> You don't see any "filesystem" or, more correctly, partition in your
>>>
>>>    fdisk -l
>>>
>>> output because you have apparently created your filesystem on the entire
>>> device (hey, I didn't know one could do that!). 
>>
>> That, actually, is the norm. It is NOT normal to partition a raid array
> 
> it IS normal for several reasons
> 
> * you may end with a replacement disk which is subtle
>    smaller and hence you normally make the partition
>    a little smaller then the device

And what does that have to do with the price of tea in China? 
Partitioning your array doesn't have any effect on whether or not said 
array uses the whole disk or not.
> 
> * in case of SSD you reserve some space for
>    better wear-levelling

And putting a partition table in your array does exactly what to help that?
> 
> * in case you ever need to reinstall your OS you
>    want your data not in the same filesystem

Which is why I partition my disk. I use one raid for the OS, and another 
for my data.

Cheers,
Wol

  reply	other threads:[~2020-11-30 22:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  8:44 “root account locked” after removing one RAID1 hard disc c.buhtz
2020-11-30  9:27 ` antlists
2020-11-30 10:29   ` c.buhtz
2020-11-30 11:40     ` Wols Lists
2020-11-30 10:31   ` Reindl Harald
2020-11-30 11:10     ` Rudy Zijlstra
2020-11-30 11:18       ` Reindl Harald
2020-11-30 20:06         ` ???root account locked??? " David T-G
2020-11-30 21:57           ` Reindl Harald
2020-11-30 22:06             ` RAID repair script (was "Re: ???root account locked??? after removing one RAID1 hard disc" David T-G
2020-11-30 12:00     ` “root account locked” after removing one RAID1 hard disc Wols Lists
2020-11-30 12:13       ` Reindl Harald
2020-11-30 13:11         ` antlists
2020-11-30 13:16           ` Reindl Harald
2020-11-30 13:47             ` antlists
2020-11-30 13:53               ` Reindl Harald
2020-11-30 14:46                 ` Rudy Zijlstra
2020-11-30 20:05 ` partitions & filesystems (was "Re: ???root account locked??? after removing one RAID1 hard disc") David T-G
2020-11-30 20:51   ` antlists
2020-11-30 21:03     ` Rudy Zijlstra
2020-11-30 21:49     ` Reindl Harald
2020-11-30 22:31       ` antlists [this message]
2020-11-30 23:21         ` Reindl Harald
2020-11-30 23:59           ` antlists
2020-11-30 22:04     ` partitions & filesystems David T-G
2020-12-01  8:45     ` partitions & filesystems (was "Re: ???root account locked??? after removing one RAID1 hard disc") c.buhtz
2020-12-01  9:18       ` Rudy Zijlstra
2020-12-01 10:00       ` Wols Lists
2020-12-01  8:41   ` buhtz
2020-12-01  9:13     ` Reindl Harald
2020-12-01  8:42   ` c.buhtz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e2a9d347-0703-07a6-0128-adf86b35b6f3@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=davidtg-robot@justpickone.org \
    --cc=h.reindl@thelounge.net \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.